Closed crsnchng closed 1 year ago
@crsnchng This is plenty good enough for a bug report. You have all the right information.
For what it's worth zeep
seems to not require urllib3
directly (in setup.py). What that tells me is that something else you're relying on isn't capping urllib3
and so you're ending up with 2.0. If you have it in your dependencies or can track that dependency down, you can probably cap urllib3
for the time being to get out of the immediate pain.
We should probably make sure that whatever is relying on this support is killed in a major release. Until then, if your other dependency(ies?) requiring urllib3 aren't requiring 2.0 I think this can keep you out of this particular problem
If you'd like to send a PR to rip out the appengine
/gae
code, that would be greatly appreciated and I would happily review it.
@pquentin alternatively, do you have time to get to this now that 2.0 is out?
@sigmavirus24 Thank you for the reply.
Before I wrote the initial issue up, I forced the Urllib3 version back to the previous one and everything worked again, so I'm good for now.
I would absolutely be interested in helping with that however I don't know that I have the ability to do this accurately. I wouldn't know where to begin aside from searching for appengine in the code and removing it and the surrounding context from everywhere I see it.
It's likely the import in the middle you got the trade back from and wherever we import those values to (likely the whole file) if I remember correctly. I expect it to be relatively straight forward
Thanks!
@sigmavirus24 To be clear you would be OK with removing App Engine support and generally make sure that toolbelt is compatible with urllib3 2.0 and all its removals/deprecations and then release that as a new version?
I can help with that.
Yes that's what I'm in favor of. I don't think the app engine support has been used/needed for years
requests-toolbelt is out with urllib3 2.0 support: https://pypi.org/project/requests-toolbelt/1.0.0/
Thanks for the report, closing.
Apologies if this is structured poorly, I don't open issues often. I use Zeep to access a SOAP API via Python and they import MultipartDecoder to use here. Since the release of Urllib3 v2.0.0 yesterday, I've been getting errors and I was finally able to figure out what happened (I feel dumb, I should have just looked at the call stack more closely).
Release for reference: https://github.com/urllib3/urllib3/releases/tag/2.0.0
Where I was able to locate the reference to AppEngine in toolbelt:
https://github.com/requests/toolbelt/blob/9d47ccf1a2e0f033f9b7d9c269e455c7f505f0fd/requests_toolbelt/_compat.py#L44-L50
The error call stack from my code that led me here: