Live data from Hacker News

Migrating to HTTPX2

github.com

111–119 of 119 posts

Re: Migrating to HTTPX2

#112

Earlier quoted context omitted.

https://github.com/encode/httpx/discussions/3784 > I've closed off access to issues and discussions. > I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value. https://www.reddit.com/r/Python/comments/1rl5kuq/anyone_know...

What does gender has to do with software development?

[flagged]

Re: Migrating to HTTPX2

#113

Earlier quoted context omitted.

https://github.com/encode/httpx/discussions/3784 > I've closed off access to issues and discussions. > I don't want to continue allowing an online environment with such an absurdly skewed gender representation. I find it intensely unwelcoming, and it's not reflective of the type of working environments I value. https://www.reddit.com/r/Python/comments/1rl5kuq/anyone_know...

What does gender has to do with software development?

I don't know anything about the history/context here, but in general an example would be if a developer were to receive gender-based harassment.

Re: Migrating to HTTPX2

#114

Why would you want to use HTTPX2 over say requests?

Requests has been dead for over a decade. It doesn’t support HTTP/2, it doesn’t support HTTP/3, it doesn’t support async, and they ignore security vulnerabilities for months.

Nobody should use requests. If you are still using it, the quickest way to get off it is to switch to niquests, which is actively developed, supports all the things I mentioned above, and API-compatible with requests - you can just do `import niquests as requests` for an instant upgrade.

https://niquests.readthedocs.io/

Re: Migrating to HTTPX2

#115
post #94
post #70

we have recently switched from httpx for the same reason but instead went with the Rust-based pyqwest (runs on Hyper) it has also a drop-in httpx-compatible transport so migration was easy and also it supports http2 trailers https://pyqwest.dev

Why not pyreqwest?

because pyqwest is what official connect Python library uses and we wanted to follow that

Re: Migrating to HTTPX2

#116

Earlier quoted context omitted.

What does gender has to do with software development?

I don't know anything about the history/context here, but in general an example would be if a developer were to receive gender-based harassment.

You know you can delete emails and messages you don’t like, right?

And again, both genders can write good/bad software just the same.

Re: Migrating to HTTPX2

#117
post #106

Earlier quoted context omitted.

> how can a single person affect negatively FOSS so much? FOSS is not affected negatively. First because FOSS is not en entity in the first place. There is no "community" per se but a muriad of softwares choosing open source licences for various reasons. Second because the choices of one project maintainer is negligible. > This type of behavior should be moderated and banned from any FOSS activity Banned by who and w…

>FOSS is not affected negatively. First because FOSS is not en entity in the first place. There is no "community" per se but a muriad of softwares choosing open source licences for various reasons. Second because the choices of one project maintainer is negligible. Yes it is, this was a major component. >This type of behavior should be moderated and banned from any FOSS activity By moderators that are not existing bu…

> Nope, is just that a useful open source project for me has always public report and that's the basis to start collaborating.

> All of it, anybody using the open source, should be free to use, modify and collaborate on a project independently from the mental issues of the one that started it. closing repos just goes against all of this and should be a shame.

You are making a false assumption that open source software is about the author surrendering is rights and forced collaboration. It is not.

Open source software is about the use of a license that grants the end user rights to study, modify and publish modifications (basically giving rights to fork) under the same or compatible license, often with mandory author attribution. There is nothing in these licenses about original author duties on maintaining a project open to collaboration, it is only about user rights.

Re: Migrating to HTTPX2

#118
post #94

Earlier quoted context omitted.

Why not pyreqwest?

because pyqwest is what official connect Python library uses and we wanted to follow that

Understood (fyi I was genuinely asking as I only used pyreqwest, which I like, and was looking for comparison if any)

Re: Migrating to HTTPX2

#119

Why would you want to use HTTPX2 over say requests?

Requests has been dead for over a decade. It doesn’t support HTTP/2, it doesn’t support HTTP/3, it doesn’t support async, and they ignore security vulnerabilities for months. Nobody should use requests. If you are still using it, the quickest way to get off it is to switch to niquests, which is actively developed, supports all the things I mentioned above, and API-compatible with requests - you can just do `import ni…

Aha, this is the context I was missing

thanks!

Post reply on HN