Expand the allowed versions of the required requests package? #26
Comments
philgyford
added a commit
to philgyford/django-wm
that referenced
this issue
Mar 26, 2022
Trying out changing `requests` from only `2.20.*` to `>= 2.20.0, < 3.0.0` And `beautifulsoup4` from only `4.6.*` to `>= 4.6.3, < 4.12.0` (latest unreleased version is 4.11, which doesn't look like it has any breaking changes beyond those in 4.10) I'll try it out and see if anything breaks! For beatonma#26
Merged
|
2.2.0 is now available. It should now accept No problem! Likewise - I hadn't touched this project in a long time and wasn't aware of anyone using it. Having some users who are interested in making it better is a good problem to have :) |
|
Thank you so much, very speedy! I've successfully added it locally, and look forward to trying to get it all working again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've just tried to install django-wm but hit an issue where its specified version of
requestsis older than that allowed by other packages I'm already using.setup.cfgspecifiesrequests ~= 2.20.0, so anything like2.20.*. But requests is now up to 2.27.1.Other things I'm using in this project, as examples, have
>=2.2.1(flickrapi),>=2.1.0(twython),>=2.0,<3.0(responses).Any chance it could be given a more lenient requirement?
(Sorry, after coming here ages ago to ask about a non-celery version of django-wm, I disappeared and only now have I found time to get to grips with it again... and here I am causing trouble once more! These kinds of interrelated dependencies can be such a pain and I only assume I haven't hit a similar problem with my own packages because nobody uses them :) Thanks for your time.)
The text was updated successfully, but these errors were encountered: