Open bladeoflight16 opened 4 years ago
Hi, bladeoflight16.
I bumped the requests
version to 2.21 because of this vulnerability with version <=1.20.
You can rest assured that it causes no problems as I have tested pokepy with these requirements and it works as intended. I know it looks bad on the install to have an error like that, but I can't do anything for now...
I'll keep this open as I will probably do something about beckett one of these days.
By bumping Beckett's requests
would the issue be resolved?
Yes.
I haven't tested beckett
with a different requests
version though.
We could send a PR there and check if the tests are passing
Yes, we could.
I just don't think @phalt is interested in maintaining beckett
anymore, as I've left some unanswered issues and a PR's there over the years.
So I don't think it's worth it if the PR is going to be left unanswered.
If it's just to check whether beckett
would work with requests
2.21 for the sake of pokepy
's functionality, I don't think it's necessary, as the pokepy
tests cover that.
I am no longer actively working on Beckett :)
@phalt Be that as it may, requests uses semantic versioning. This means that Beckett should be able to depend on any higher 2.x version of it without worrying about breaking compatibility. Would you consider a small update to loosen the versioning requirement? Assuming your testing is automated, that should be an extremely small change.
@bladeoflight16 when I get some free time I will try and make a release.
Alternatively, feel free to make a pull request!
Using a clean venv, I get a dependency conflict between beckett and pokepy for the requests package:
It still installs, and I don't know whether it actually causes any problems. But still should be addressed.