Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"pycrc" != "PyCRC" but same url used in python package index #38

Closed
Ecordonnier opened this issue Jan 28, 2020 · 3 comments
Closed

"pycrc" != "PyCRC" but same url used in python package index #38

Ecordonnier opened this issue Jan 28, 2020 · 3 comments

Comments

@Ecordonnier
Copy link

Ecordonnier commented Jan 28, 2020

Hello,
I was using PyCRC in my project (https://libraries.io/pypi/PyCRC / https://github.com/alexbutirskiy/PyCRC, which is not maintained any more and has nothing to do with https://github.com/tpircher/pycrc) and my nightly builds started failing, because the python package index removed "PyCRC 1.21" and added "pycrc version 0.9.2" instead (https://pypi.org/project/pycrc/#history shows the release was done on January 24), therefore I started getting those error messages:

ERROR: Could not find a version that satisfies the requirement PyCRC==1.21 (from -r requirements.txt (line 3)) (from versions: 0.9.2)
ERROR: No matching distribution found for PyCRC==1.21 (from -r requirements.txt (line 3))

I just wanted to document the issue there in case it affects other people. It is quite confusing that the python package index just replaced one package with another even though they are not related, and kept the same package name with a different case, knowing that pip is case insensitive.

@cantzler
Copy link

We just encountered the same issue as well :(

@tpircher-zz
Copy link
Owner

I am sorry about the problems caused by this. The change on the Python Package Index was initiated by me and agreed with the maintainer of the (other) PyCRC package. It was triggered by the fact that I got contacted by multiple people attempting to install pycrc via pip and who were surprised that they got a different code they were expecting. The joys of a name clash. Sigh.

@Ecordonnier
Copy link
Author

Hi tpircher! No problem, as far as I understand this change conforms to https://www.python.org/dev/peps/pep-0541/

I don't know how cumbersome it is, but if it is easily doable I would suggest to clarify the situation in the project description at https://pypi.org/project/pycrc/#description

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants