#1226 Explain how Python canonical names are created
Merged 2 years ago by churchyard. Opened 2 years ago by churchyard.
churchyard/packaging-committee python-packaging-canonical  into  master

@@ -248,6 +248,9 @@ 

  https://www.python.org/dev/peps/pep-0503/#normalized-names[PEP 503],

  and <<py_dist_name,the `+%{py_dist_name}+` macro>> implements it

  for Fedora packaging.

+ The canonical name is obtained by switching the project name to lower case

+ and converting all runs of non-alphanumeric characters to single “-” characters.

+ Example: “The $$$ Tree” becomes “the-tree”.

  

  Elsewhere in this text,

  the metavariable `+DISTNAME+` refers to the canonical form of the project name.
@@ -285,6 +288,7 @@ 

  the <<Canonical project name>>.

  If possible, the project name *SHOULD* be the same

  as the name of the main importable module,

+ in lowercase,

  with underscores (`+_+`) replaced by dashes (`+-+`).

  

  If the importable module name and the project name do not match,

no initial comment

rebased onto 14b621e

2 years ago

Pull-Request has been merged by churchyard

2 years ago
Metadata