What's the problem this feature will solve?
Conform to accepted standards, make it possible to reliably determine a project's (canonical form) name and version from the source distribution filename.
Describe the solution you'd like
See https://peps.python.org/pep-0625/
When creating sdist files, normalise the project name and version parts according to the specification, documented here.
Alternative Solutions
Continue as at present, which will leave sdist consumers with no reliable way of knowing the filename and version of a sdist short of either extracting the metadata from the sdist (if the sdist conforms to PEP 643) or actually building the distribution.
Additional context
Code that wants the project's formal name will still need to read the distribution metadata - that is understood and this specification doesn't affect that.
Code of Conduct
What's the problem this feature will solve?
Conform to accepted standards, make it possible to reliably determine a project's (canonical form) name and version from the source distribution filename.
Describe the solution you'd like
See https://peps.python.org/pep-0625/
When creating sdist files, normalise the project name and version parts according to the specification, documented here.
Alternative Solutions
Continue as at present, which will leave sdist consumers with no reliable way of knowing the filename and version of a sdist short of either extracting the metadata from the sdist (if the sdist conforms to PEP 643) or actually building the distribution.
Additional context
Code that wants the project's formal name will still need to read the distribution metadata - that is understood and this specification doesn't affect that.
Code of Conduct