Case sensitivity of project names when publishing to PyPI
See original GitHub issue- I am on the latest Poetry version.
- I have searched the issues of this repo and believe that this is not a duplicate.
- Poetry version: 0.12.16
Issue
I’m trying to migrate my project from setup.py
etc to poetry
, and it has mostly been very straightforward.
My (very minor) issue is that the name
field does not appear to preserve its case when publishing.
[tool.poetry]
name = "PyPortfolioOpt"
version = "0.3.2"
...
Becomes:
With setup.py
, the case sensitivity is preserved on PyPI.
I know that there is no real difference which is why this is a minor issue, but stylistically it’s a tiny thing that I prefer about setup.py
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
PyPi Package Registry is case sensitive (#244412) - GitLab
PEP 426 states: All comparisons of distribution names MUST be case insensitive, and MUST consider hyphens and underscores to be equivalent.
Read more >Is PIP/PyPI Case Sensitive? - Finxter
“PyPI places strict restrictions on names – they must match a case insensitive regex or they won't be accepted.”.
Read more >Pip case sensitivity - python - Stack Overflow
No, pip is not case sensitive. All comparisons of distribution names must be case insensitive, and must consider hyphens ...
Read more >How to configure, build, and publish your Python projects to PyPI
In practice, when you want to publish your real project, you would need to give it a meaningful and descriptive name, preferably catchy...
Read more >How to upload programs to PyPI - Packt Subscription
name : The name of the project, as it will be listed on PyPI. Only ASCII alphanumeric characters, underscores, hyphens, and periods are...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, as I said there, that MR leaves poetry continuing to normalize project names at upload.
Unless and until pypa decide what the standards should actually be, and pypi do something about https://github.com/pypi/warehouse/issues/10030, it will remain impossible to do both of (i) publish with a pretty project name and (ii) normalize sdist and wheel names.
https://github.com/python-poetry/poetry-core/pull/484 continues in the direction of favouring normalization.
@justinmayer I’ve just tried with v1.0.0 – it’s still unresolved.