Case sensitivity of project names when publishing to PyPI

[robertmartin8]

• 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.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[justinmayer]

@robertmartin8: Could you try using the latest Poetry 1.0 beta (e.g., by passing --preview to the get-poetry.py install script) and confirm that the issue you reported persists?

[robertmartin8]

@justinmayer

I just pushed an update to my package. As far as I can see, the issue still persists.

> poetry --version
Poetry version 1.0.0b9

> poetry build

Building PyPortfolioOpt (0.5.0)
 - Building sdist
 - Built PyPortfolioOpt-0.5.0.tar.gz

 - Building wheel
 - Built PyPortfolioOpt-0.5.0-py3-none-any.whl

> poetry publish

Publishing PyPortfolioOpt (0.5.0) to PyPI
Username: ***********
Password: 
 - Uploading PyPortfolioOpt-0.5.0-py3-none-any.whl 100%
 - Uploading PyPortfolioOpt-0.5.0.tar.gz 100%

[justinmayer]

Poetry v1.0.0 was just released, so I'd try again with that version. I imagine the issue is unresolved, but it'd be better to know that for certain.

[robertmartin8]

@justinmayer I've just tried with v1.0.0 – it's still unresolved.

[neersighted]

@dimbleby will python-poetry/poetry-core#484 affect this?

[dimbleby]

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 pypi/warehouse#10030, it will remain impossible to do both of (i) publish with a pretty project name and (ii) normalize sdist and wheel names.

python-poetry/poetry-core#484 continues in the direction of favouring normalization.

[neersighted]

Ah, makes sense -- we're trading capitalized names versus not being able to upload an entire category of otherwise valid packages. Given the acceptance of PEP 625 and our move to canonicalize names, I'm going to close this as wontfix. It could eventually be addressed by amendments to the PEPs/changes in PyPI widening the list of acceptable names (e.g. pypi/warehouse#12316).

[dimbleby]

yeah - again reiterating what I said in the other one - if and when that pypi issue is fixed, it's trivial for poetry to start publishing with pretty names. But we shouldn't do that while it doesn't work!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.