Better migrate to https://zapros.dev from httpx maintainer
Migrating to HTTPX2
71–80 of 119 posts
Re: Migrating to HTTPX2
#72Re: Migrating to HTTPX2
#73A network error occurred. Please check your connection and try again. If this issue persists please contact us through our help center at help.openai.com.
yeah nice engineering clowns
Re: Migrating to HTTPX2
#74Earlier quoted context omitted.
this made me laugh even though i dont think i even get it. can you explain this please lol
people think other people are 'toxic' for the silliest of things most times; and this person is saying some maintainer is toxic to put it out there but provides no information as to why.. so i figured my context is as good as theirs
> people think other people are 'toxic' for the silliest of things most times
Do they?
Re: Migrating to HTTPX2
#75Earlier quoted context omitted.
> Unfortunately that 1.0 work is happening in a private repository. That’s even more reason to consider it non-viable. There is no reason to encourage or support this type of behavior in a project. It is their right to do with it as they please, but I’m not interested in a project that functions like this. The forks are continuing to operate like true community projects.
Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.
That is a legitimate feeling, but to spite the trillion dollars company he also hurts thousands of regular developers.
He doesn't owe those developers anything, of course, but likewise they do not owe him loyalty and thus since an open fork exists, his project will die.
Killing the project is also his right, but people also have a right to be upset by his passive aggressive behavior. Just announce that you're shutting down the project and move on, don't waste our time.
Re: Migrating to HTTPX2
#76[flagged]
HTTPX2 isn't about the protocol version, it's the name of a python library to make http requests.
But yes, it doesn't support HTTP3. Here's the related issue: https://github.com/pydantic/httpx2/issues/92
Re: Migrating to HTTPX2
#77Earlier quoted context omitted.
> Unfortunately that 1.0 work is happening in a private repository. That’s even more reason to consider it non-viable. There is no reason to encourage or support this type of behavior in a project. It is their right to do with it as they please, but I’m not interested in a project that functions like this. The forks are continuing to operate like true community projects.
Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.
[deleted]
Re: Migrating to HTTPX2
#78Better migrate to https://zapros.dev from httpx maintainer
Seems like the point is that the httpx maintainer is a bad maintainer.
Re: Migrating to HTTPX2
#79Earlier quoted context omitted.
> Unfortunately that 1.0 work is happening in a private repository. That’s even more reason to consider it non-viable. There is no reason to encourage or support this type of behavior in a project. It is their right to do with it as they please, but I’m not interested in a project that functions like this. The forks are continuing to operate like true community projects.
Maybe they don't feel like sharing their work with the AI bot scrapers until the work is complete.
For the users of the project, the reasons don’t matter. They’re free to do as they want for any reason they choose.
Users of the project can (and have been) moving to forks that are operated as open, community projects in the continued spirit of the project’s original intention.
For what it’s worth, the maintainer has stated their reasons and they are not related to AI or scraper bots.
Re: Migrating to HTTPX2
#80Why this is in the frontpage?
I'd second this question. And I really mean that in a sincere way. Why is the choice of a random HTTP library in an SDK such an engaging topic of discussion here? Is there some context I'm missing?
When I first read the title, I assumed this was some fancy new protocol that extends HTTP or something. But it's just about an SDK switching one transitive dependency with a fork? And arguably one that should just have its functionality be part of stdlib?