10 ms·
The domain for the Python Requests library is expired
- jsmeaton 4y agoThis was recently an issue with the celery docs site too. When the primary authors step away from the code the infra isn’t always handed over.
- abbaselmas 4y agoi had some problem with celery a few days ago, this cant be coincidence. Thanks for the info.
- matsemann 4y agoYeah, celery docs were down for weeks earlier this year and now has a new domain.
- tony 4y agoBackstory on the above: https://github.com/celery/celeryproject/issues/52 https://github.com/celery/celeryproject/issues/52, https://twitter.com/auvipy/status/1506560289117933568 https://twitter.com/auvipy/status/1506560289117933568, https://twitter.com/auvipy/status/1507254618954207235 https://twitter.com/auvipy/status/1507254618954207235
- jammycrisp 4y agoGitHub issue: https://github.com/psf/requests/issues/6140 https://github.com/psf/requests/issues/6140
- Jamie9912 4y agoIm curious how this is a valid issue for that repository, the repository seems to make no reference to that domain
- raunak 4y agoThe requests repository isn’t connected to Python-requests? Maybe take another look, haha.
- Jamie9912 4y agoI would argue that the repository should only pertain to things regarding the repository, not the project as a whole
- pseudalopex 4y agoWhere should things regarding the project go? The maintainers said to ask a question on Stack Overflow, file an issue on GitHub, or send a message on Twitter.[1] [1] https://requests.readthedocs.io/en/latest/community/support/ https://requests.readthedocs.io/en/latest/community/support/
- forgotpwd16 4y agoThe only official connection is that site holding translations to the docs hosted on RTD.
- di 4y agoFrom https://github.com/psf/requests/issues/6140 https://github.com/psf/requests/issues/6140: > The domain is still owned by Kenneth and the maintainers haven't had access to it in quite some time. and: > For those looking for alternatives, https://requests.readthedocs.io/en/latest/ https://requests.readthedocs.io/en/latest/ should be returning docs correctly again. This has been the "official" location for some time as we lack controls on the python-requests domains. I'll update again once we receive a response from Kenneth.
- pyuser583 4y agoAccording to Kenneth’s Twitter feed, be became a dad about about 50 days ago. I imagine he’s busy.
- OJFord 4y agoHe sort of 'rage quit' well before that, handed everything off to the first to request it. Not great, but his prerogative, something to bare in mind relying on OSS from random individuals I suppose, even if it is something as major as requests (and someone as major as Reitz) et al.
- ksaj 4y agoIt's the same as our recent FOSS library security gaffe. Entirely maintained by one guy, yet relied upon by way too many people not willing to throw in some funds for its upkeep.
- pyuser583 4y agoJudging by his now-deleted tweets, he’s had a hectic life. I hope he’s enjoying spending time with his spawn.
- boopmaster 4y agohopefully it’s more enjoyment than you’ve derived by frolicking around in his creative outputs before tossing out hot takes about his personal life.
- wodenokoto 4y agoWhat does it mean that the domain has expired? I tried to look it up on a domain purchasing website and it isn't available for purchase, and according to namecheap it is still owned by the same owner since 2011.
- nateprewitt 4y agoTo clarify, it's not expired, the registrar is asking Kenneth to verify his identity. We're currently pending that before it's available again.
- simonw 4y agoWeirdly, when I'm evaluating open source libraries having their own domain name rather than a site on GitHub pages or ReadTheDocs is a very slight mark against them in my book - because of exactly this. If a project has its own domain name, it has better be VERY confident that it will be renewing that domain for decades to come. If it's a relatively concise library I would much rather it use a trustworthy service to host its documentation as opposed to some custom domain that's likely to expire and break links in the future. (My own open source projects now mostly hang off my https://datasette.io/ https://datasette.io/ domain, but I was a few years into that project before I committed to a domain name that I plan to renew for the rest of my life.)
- matsemann 4y agoI almost feel like it's a python specific issue. No other eco system have I've had to scour so many random almost identical looking websites to learn the libraries I use. Almost like spending lots of time making a documentation page is a rite of passage for python devs. Of course, some of it may be that I didn't need it as much for when I did java dev. Typing+docstrings help much more in the IDE than for python code. Also, it's good that most python devs want to document their code. I'd just wish they'd do a better job, and not be so inspired by the crappy official docs.
- number6 4y agoThere is this tool: sphinx. Helps you making documentation + website. Can read you code and document it with your docstrings. Generates some okish documentation and is kind of boilerplate if you create a library. There do all these websites come from.
- vladvasiliu 4y agoSure, for example Rust has rustdoc that does the same thing, but there's a common repository for documentation, kind of like pip is a common repository for libs in Python. There are connectors for ReadTheDocs to generate the Sphinx docs from GitHub, and probably from elsewhere, too. Yet many projects prefer to host the docs on some random domain.
- marban 4y agoRecommended alternative: https://www.python-httpx.org https://www.python-httpx.org
- mikkelam 4y agoYep! I've been using httpx for all my projects and several are in production. It's a great replacement
- marban 4y agoToo bad you'll still end up with requests as part of some other package's dependency most of the time.
- raverbashing 4y agoThis is a bit ridiculous (not the library, the situation) Why do we have to reinvent the wheel every couple of years? As much as this lib looks fine, I'd be sticking with requests if it still keeps getting fixes And of course the beauty of open source is that I can fork the project and add a fix if I need. It's great that HttpX uses the same API apparently, but you know, there's always some rough corner somewhere and of course your project hits it. Of course. Software maintenance is already annoying without having to update libraries every now and then. Now having to replace a library is even more problematic
- julianwachholz 4y agorequests has laid all the groundwork for httpx to be able to even exist. the new library is a natural evolution that for example features full async support, which I don't think will ever be added to requests.
- wheelerof4te 4y agoDepending on your needs, urllib might be good enough.
- declnz 4y ago
- _andrei_ 4y agorequests.dev is on sale for $174
- sideproject 4y agoI've recently launched a project (https://domainy.io https://domainy.io) which lets you monitor for domain names's availability, expiration, purchased etc etc. It's been interesting to see the type of domains that do get expired, though I haven't had a chance to snap up some of them.
- deleted 4y ago[deleted]
- wheelerof4te 4y agoToo bad, requests is a very popular and useful library. Yet, this is just one more example against reliying on third-party libraries for production purposes. Sometimes, urllib is enough.
- robertlagrant 4y agoAt least it's open source. You can still install the library, read (and even vendor) the source code, and build the docs from that code. You just can't visit the website.
- gonzo41 4y agoThis happened to the Celery project a while back. I was surprised most opensource projects arn't using something like gitlab or hub pages for cheap hosting for docs.
- lysecret 4y agoRequests not being async is a pretty big remark against it in my book. I am still using it for testing and sync requests but moved to aiohttp mostly.