Amending PEP 427 (and PEP 625) on package normalization rules

[dstufft (Donald Stufft)]

@pf_moore

What I want now, though, is to make PyPI show my project name as pkg_metadata. And I don’t have any means of doing that, which I can locate (short of deleting and re-creating the project, which I can do right now, but I don’t want to, and which I won’t be able to do when deletions are prohibited).

@dstufft

PyPI looks the project up by normalized name during upload and will rename the project if the “display” name is different.

That doesn’t seem to be happening for me. All of my metadata uses the normalised name, but PyPI still has the hyphenated version.

Sounds like either one of the tools in the process of getting that data to PyPI normalized the name prior to sending that data to PyPI or Warehouse has a bug. I don’t have time at the moment to dig into which of those things are causing it.

If you wanted to dig into it, you could see what (it looks like you uploaded with twine?) twine is sending on the wire, since Warehouse doesn’t introspect the package currently, it’s trusting data that is sent in a HTML form alongside the file by twine. I believe that happens here, if you wanted to drop some debugging code in there to see what is being sent.

If your uploader is sending a form field with the name name and the value pkg_resources and Warehouse isn’t updating the display name to pkg_resources then that’s a bug in Warehouse.