| |
@@ -408,7 +408,7 @@
|
| |
Each Python package *MUST* include _Package Distribution Metadata_
|
| |
conforming to https://packaging.python.org/specifications/[PyPA specifications]
|
| |
(specifically,
|
| |
- https://packaging.python.org/specifications/recording-installed-packages/[Recording installed distributons]).
|
| |
+ https://packaging.python.org/specifications/recording-installed-packages/[Recording installed projects]).
|
| |
|
| |
The metadata *SHOULD* be included
|
| |
in the same subpackage as the main importable module,
|
| |
@@ -1129,7 +1129,7 @@
|
| |
where the linter is not pinned to an exact version.
|
| |
Furthermore, some of these tools take a long time
|
| |
to adapt to new Python versions,
|
| |
- preventing early testing with Aplha and Beta releases of Python.
|
| |
+ preventing early testing with Alpha and Beta releases of Python.
|
| |
And they are just not needed: wrongly formatted code is not important enough
|
| |
for the Fedora packager to bug the upstream about it.
|
| |
Making such an issue break a package build is entirely unreasonable.
|
| |
oturpe
commented 2 years ago
Assortment of fixes from reading the guidelines while trying to create my first Python package.