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
Version available on PyPI is more recent than the one here #20
Comments
Hi @tlc28! As you can see from this comment, this repo is not particularly maintained anymore. I'm not sure why the PyPI version is |
Thanks @jcmorrow for your answer!
Yeah, I had figured this out from the commit history. But a lot of other good libraries don't change anymore.
I do not want to look like the guy who puts the responsibility on you, but I would appreciate to have this sorted out. Now, I'm not event sure that the code available on PyPI is the same as the one in the repo!? … actually, it's not and the diff is quite long, but it should be easy to merge it back to the repo. If it helps, I can contact the author listed on PyPI or/and I can submit a PR to merge the changes from the version on PyPI.
Thanks for the alternatives! I've tried expects, expects, assertpy… but somehow, I find robber's syntax to be more readable. And it does the job! |
@tlc28 yeah, it looks to me like the PyPI version is probably https://github.com/EastAgile/robber.py. Maybe you should open a PR over there (or just message the maintainers) to ask that they change the homepage on PyPI to their repo? Also, it looks like the |
Hi @jcmorrow !
Thanks for pointing me to the repo!
Sounds like a plan! I'll do that asap. Thanks again for your help. |
Hi,
I'm packaging robber.py for Guix (https://guix.gnu.org) and could not help but notice that the version available on PyPI (1.1.5) is more recent than the one (0.1.0) in this repo (the one PyPI is pointing to as a homepage).
I would rather use the git repo as a source of truth as it contains some tests. Should I use a different repo? If so, would it be possible to update the PyPI page for robber. Thanks!
The text was updated successfully, but these errors were encountered: