Various responses to the priorities/roadmap post mentioned that the urllib3/requests port was the library that missed the most in Trio.
I agree! That’s why I started working on it in January 2018, basically by trying to turn @njs’s ideas into code and then asking him for reviews (with help of a few other contributors). We’re now in February 2019. As it’s only my priority every few months, the progress is irregular: while we did improve things a lot, there is still a lot of work left!
The working repository is https://github.com/python-trio/urllib3. The current task is to ensure that all existing tests pass, so that we get back to 100% coverage. We’re at 93% right now. Here’s my elaborate process:
- pick a xfailing or skipped test
- try to make it pass
- send the modification for review
- rinse and repeat
As a result, I’m afraid there are no identified good first bugs: I can’t tell before working on a test how easy it will be! But I’d be happy to help if anyone want to try doing this.
Maybe a good first task would be to read https://github.com/python-trio/urllib3/issues/1, try running the tests using tox, and document/improve the process for the next contributors? Again, I’d be happy to help.
One big issue was that I could not merge urllib3 changes fast enough and was months behind the urllib3 main branch.