Re:Issue: find a new home for repos including Requests
by fibers on Wednesday July 17, 2019 @03:43PM
(#20463231)
what will this mean for an async version of requests?
[ Parent
| on HN ]
Re:Issue: find a new home for repos including Requests
by florimondmanca on Wednesday July 17, 2019 @06:39PM
(#20464753)
On a side note, there has been work on an async HTTP client in a separate project conducted by the Encode organization here: https://github.com/encode/http3
Re:Issue: find a new home for repos including Requests
by kamyarg on Wednesday July 17, 2019 @03:44PM
(#20463243)
Someone more responsible can actually make it happen.
Re:Issue: find a new home for repos including Requests
by hartator on Wednesday July 17, 2019 @03:53PM
(#20463313)
kennethreitz has not been responsible? `requests` is my favorite http library in all languages so far.
Re:Issue: find a new home for repos including Requests
by jrimbault on Wednesday July 17, 2019 @03:59PM
(#20463363)
He has shown patterns of bad behaviors. One recent example of the top of my head :
- https://vorpus.org/blog/why-im-not-collaborating-with-kennet...
- and HN's thread https://news.ycombinator.com/item?id=19826680
Request has not been maintained by Reitz for some time now (meaning he hasn't contributed).
Re:Issue: find a new home for repos including Requests
by kamyarg on Wednesday July 17, 2019 @03:58PM
(#20463354)
Take a look into pipenv issues and how he handles legitimate broken features such as --keep-outdated and you will know[1].
Requests I agree has been very stable.
Also as an extra reading regarding async support for requests take a look at this article by a Python core Developer(Nathaniel J. Smith):
"Why I'm not collaborating with Kenneth Reitz" https://vorpus.org/blog/why-im-not-collaborating-with-kennet...