-
Notifications
You must be signed in to change notification settings - Fork 53
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
Port to using urllib3 or requests #16
Comments
I'm a bit reluctant about this. |
@jayvdb , python3-compatible release is out, would you like to submit a patch for urllib3 or requests? We could have a look. |
I think it'd be great to use |
Sorry, I am not working in this area at the moment, and have a full plate on other OSS projects right now. |
My vote: get the current small stuff merged in and released, and keep this issue open as something that could be tried out later (ie. for next major release, if there ever needs to be one). If @jascoul says he'd accept a PR that refactors to use |
IDK if my vote counts, but unless the code gets way shorter and way more readable, I would refrain from relying on another 3rd party library, even as widespread as |
Definitely a valid perspective (and it's not like I suddenly own this repo, so I guess it's for the others to decide)! Anyway, there's a list of things to do before this one, so it can get tabled for now. But in my experience you'd be surprised how nice requests can make some old urllib code :) Plus it's all academic unless those who can merge say they'd accept the PR anyway, no point writing anything till confirmation of that exists. So yeah, low low prio right now if nothing's broken with urllib. And requests is really only 'technically' a third party module at this point 😃 |
Would it be beneficial to port pyoai to use urllib3 or requests? (After #15 is merged)
It would remove a lot of complex http urllib/urllib2 code, and less future problems due to oddball http server configurations.
The text was updated successfully, but these errors were encountered: