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

Duplicate/confusing entry in pypi #817

Closed
gugu91 opened this issue Jun 7, 2018 · 8 comments
Closed

Duplicate/confusing entry in pypi #817

gugu91 opened this issue Jun 7, 2018 · 8 comments
Labels
documentation no-changelog If set, the issue won't show up in the Changelog
Milestone

Comments

@gugu91
Copy link

gugu91 commented Jun 7, 2018

Description of issue / feature request

Is there any difference between: https://pypi.org/project/locust/ and https://pypi.org/project/locustio/ ?

Also, there is a this conda package: https://anaconda.org/conda-forge/locust and this: https://anaconda.org/auto/locustio

@cgoldberg
Copy link
Member

https://pypi.org/project/locustio/ is the official

@cgoldberg
Copy link
Member

cgoldberg commented Jun 8, 2018

hmm.. this is super confusing considering pip install locust (instead of pip install locustio) will get you an outdated version right now.

@heyman do you have the access to the locust namespace on PyPI? If so, I think we should publish the next release there as well as locustio. Could you add me as a maintainer to locust on PyPI?

@cyberw
Copy link
Collaborator

cyberw commented Oct 26, 2019

@heyman We should try to fix this. Ideally I think we should switch to using locust instead of locustio (but that would be a major change). IMO, the unused one should be removed or replaced with some sort of a deprecation notice.

@heyman
Copy link
Member

heyman commented Oct 26, 2019

@cgoldberg Yes, I have access to the locust namespace. Currently what's uploaded there is just a setup.py with a install_requires=["locustio"] so one should get the latest locustio version when running pip install locust(though I guess you won't get the latest version when running pip install locust --upgrade if you already have an older version of the locustio package installed).

@cyberw I think that ideally we would switch to locust, keep all the already uploaded locustio packages so that we wouldn't break projects that have a version pinned, and then make so that the newest version of locustio was some kind of dummy package that would issue a warning telling people to user locust instead. I'm not sure if that is possible though?

@heyman
Copy link
Member

heyman commented Oct 26, 2019

I guess that we could switch to locust and then keep uploading a new setup.py (to locustio) with install_requires=["locust==x.y"] for every version we release. That would be a maintenance burden though (but maybe we could automate it?).

@cyberw
Copy link
Collaborator

cyberw commented Oct 28, 2019

There seems to be a way to output log messages (and maybe even throw an error) after package installation, maybe that could be useful.

https://stackoverflow.com/questions/20288711/post-install-script-with-python-setuptools

@heyman
Copy link
Member

heyman commented Oct 28, 2019

I believe pip swallows all output, at least when the installation is successful (maybe it's possible to output a message while rasing an error).

@cyberw
Copy link
Collaborator

cyberw commented May 22, 2020

Fixed! Release is now on locust, and trying to install locustio gives a helpful error message:

**** Locust package has moved from 'locustio' to 'locust'. Please update your reference (or pin your version to 0.14.6 if you dont want to update to 1.0) ****

@cyberw cyberw closed this as completed May 22, 2020
@cyberw cyberw added the no-changelog If set, the issue won't show up in the Changelog label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation no-changelog If set, the issue won't show up in the Changelog
Projects
None yet
Development

No branches or pull requests

5 participants