-
Notifications
You must be signed in to change notification settings - Fork 15
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
pip / pip3 installs an outdated version #14
Comments
Thanks for bringing this to my attention. I'm not sure why PyPi is giving you an outdated version, but in the meantime you can install the package through Github directly:
|
Pip installs outdated version because |
Bump. This is still an issue. @braunly is correct, |
Time to do something then ! This is exactly why derpibooru-dl fails. |
I published my own patched version here which can be used as a substitute if installed as a zipball. I haven't published it to PyPi as I'm not sure of the "legal" implications of such. The project maintainer @joshua-stone appears to be inactive, so no PyPi update any time soon. |
@braunly @rautamiekka @BytewaveMLP I've been trying to fix the issue, but packaging has been difficult. There are multiple instances of version information across different files to keep track of, pip isn't providing meaningful error output, and PyPI doesn't seem to be clear about whether the PKG-INFO file I upload is even doing anything. After using Rust/Cargo, I'm finding that Python's tooling could definitely use an improvement in developer friendliness. As mentioned before, installing from Github directly seems to at least work while I look into fixing the PyPI package:
|
Oh huh, you're alive? That's good to know, at least. Hopefully you can get things worked out. Would be nice to be able to use the official PyPi package at some point. ❤️ |
Yeah I'm alive, although I admittedly haven't been keeping up with development. I think I've finally fixed the problem. Please check by running this:
|
After installing
|
And just to prove it's the correct version:
|
The problem is that we (pip) have to run Basically, you can't import your module inside your |
As pointed out in joshua-stone#14, the import in this is breaking pip because it tries to import requests before it's installed. As far as I can see, this import doesn't do anything, and it installed fine without it. So I request that this line gets removed so this package gets installed correctly through pip.
With the |
Still having this issue, without pre-installing requests manually, so I fixed it in a fork. |
Hi, maybe this is just me being ignorant about how things work, but no matter what I try, pip always installs version 0.6 for me, which doesn't work anymore with the changes to the API. I've reproduced this on multiple machines running different distros.
Anyone else experiencing this? Somebody know how to fix it?
The text was updated successfully, but these errors were encountered: