Paul Moore

> This also means recognizing that the overview is not PyPI best-practice specific. Why do you feel that's the case? Certainly there are many workflows involving deploying Python code, but...

> the main thing the document is trying to highlight is that you can depend only on stdlib to do sdists I'm not sure how that's even relevant. We very...

> the goal is to educate the user on something they might justifiably do to distribute Python software, building on examples they've likely encountered recently I have to say, when...

> And I think your list is pretty good! However, it doesn't focus on what's necessary on the target/deployment environment. I'd dispute or at least extend some of your points....

> Many popular libraries can and often are simply included by directly copying them into a project. Can you provide examples? I'm not aware of any such. > I can...

From a quick look, there's a lot of features of `scripttest` that we use which are not in Aurornis, so that won't be happening any time soon...

I'm not aware of anything in any spec that suggests that stripping trailing zero components is necessary when normalising versions. Yes, when *comparing* versions, extra trailing zeroes are ignored, but...

In your example, as ling as the *project name* is known to be normalised (so it doesn't contain a hyphen character) there is no ambiguity. I agree that I would...

Python has *two* concepts of a project name. The "display name" (which is the project's choice, and which is what is stored in the project metadata and should be used...

I assume things like https://pypi.org/project/pykg-config/ - [PEP 503](https://peps.python.org/pep-0503/) defines normalisation to use hyphens. The wheel and sdist [specs](https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode) are different, but they basically come down to "normalise like PEP 503...