Wow, that's a serious thread! I hope you're coming to PyCon Quentin. I'll be there and hard to miss (I carry a 6ft "Python Staff")
I happened to bump into both Cory Benfield and Kenneth and picked their brains on some of the thinking for requests 3.0. The design in my email is going to take a year to develop and stabilise. I think we can still work on points 1 and 3, but 2 will just be an architectural principle. The actual implementation of it will take time and most likely change considering what you point out and even how much changed in the last 12 months. With respect to the comment on reviewers, point 3 will help. I've merged 10's of pull-requests to simply add AWS AZ's and EC2 instance sizes. This just seems completely unnecessary when Amazon maintain that list inside boto. On Fri, Mar 9, 2018 at 4:41 PM, Quentin Pradet <quentin.pra...@gmail.com> wrote: > Thanks Anthony! We do need this kind of discussion. > > So libcloud right now is an healthy project that continues to improve, > mostly with external contributions. Which is nice! However it's difficult > for me to keep up with those pull requests, so for any other developments > we would need more reviewers. > > I think we should be careful about asyncio. It's likely to become the next > urllib or httplib: useful, but much worse than existing third-party > projects. Indeed, it was set in stone when added to the standard library, > but the async/await keywords changed all the best practices. So it's not > clear that asyncio is the future of Python async, > http://trio.readthedocs.io/en/latest/ seems more promising and more > natural to use for example. > > I'm actually contributing to an async urllib3 port to asyncio, twisted and > trio, while keeping sync support for Python 2 and Python 3, using a > "bleaching" approach : see https://github.com/shazow/urllib3/issues/1323. > Hopefully this will be ready for requests 3.0, and at that point the > community will have learned how to make useful async + sync libraries. > Until then, I don't believe we should work on making libcloud async or even > async-only. > > Hope that helps, > Quentin >
