🌕 我為何要分叉(fork)HTTPX
➤ 當開源專案維護失靈:從 HTTPX 到 httpxyz 的生存選擇
https://tildeweb.nl/~michiel/httpxyz.html
由於知名的 Python HTTP 客戶端套件 HTTPX 長期缺乏更新與版本發布,且開發者封閉了 GitHub 上的問題追蹤與討論區,導致許多仰賴該套件的專案陷入困境。作者 Michiel 在貢獻修正代碼卻遲遲未獲合併後,決定分叉出名為 `httpxyz` 的專案。他強調此舉並非為了推翻既有架構,而是為了提供一個穩定、持續維護的替代方案,並呼籲開源社羣減少對單一平臺(如 GitHub)的過度依賴。
+ 這就是開源軟體依賴單一核心維護者的風險。當維護者開始「封閉」開發過程,分叉確實是維持軟體生命力的唯一路徑。
+ 雖然理解維護者的壓力,但如果一個高流量的套件既不更新又不開放權限,對生態系的傷害確實太大。支持這個穩定導向的分叉。
##Python #開源生態 #HTTPX #軟體維護
Why I forked httpx | Blog

I forked the python library httpx to httpxyz after over a year without a release of this popular package

Why I forked httpx | Blog

🔥 Check out this must-read post from Hacker News 📖 📂 **Category**: 💡 **What You’ll Learn**: Why I forked httpx published on 2026-03-25 · tagged with #httpx, #httpxyz and #python Yesterday I forked httpx. The new fork is called httpxyz. Reasons for the fork HTTPX is a very popular HTTP client for Python. There is lots of code depending on it.

https://viralpique.com/why-i-forked-httpx-blog/

Why I forked httpx | Blog - viralpique.com

🔥 Check out this must-read post from Hacker News 📖 📂 **Category**: 💡 **What You’ll Learn**: Why I forked httpx published on 2026-03-25 · tagged with #httpx, #httpxyz and #python Yesterday I forked httpx. The new fork is called httpxyz. Reasons for the fork HTTPX is a very popular HTTP client for Python. There is

viralpique.com - Where Curiosity Goes Viral
Why I forked httpx | Blog

I forked the python library httpx to httpxyz after over a year without a release of this popular package

Why I forked httpx - the popular python package:

https://tildeweb.nl/~michiel/httpxyz.html

#python #httpx #httpxyz

Why I forked httpx | Blog

I forked the python library httpx to httpxyz after over a year without a release of this popular package

There's a new piece explaining "The Slow Collapse of #MkDocs": "How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects."

https://fpgmaas.com/blog/collapse-of-mkdocs/

Well, that says a lot. But what's really interesting is that MkDocs 2.x is being developed as part of the "encode" organization. That's great, right? The people who gave us such great libraries as #httpx?

Well, turns out no, not at all. It looks like encode has already crumbled and became immensely toxic.

httpx is not allowing bug reports anymore, apparently because of "absurdly skewed gender representation", whatever that means.

https://web.archive.org/web/20260228113715/https://github.com/encode/httpx/discussions/3784

That also explained why starlette moved out of the organization a while back:

https://web.archive.org/web/20260323042730/https://github.com/Kludex/starlette/issues/3180

There's a great rot in #OpenSource.

#FreeSoftware #Python

The Slow Collapse of MkDocs

How personality clashes, an absent founder, and a controversial redesign fractured one of Python's most popular projects.

Hey, in light of https://github.com/encode/httpx/discussions/3784 , does anyone know of how to get in touch or give feedback?

I guess there's a stackoverflow tag

#Python #HTTPX

Closing off access. · encode httpx · Discussion #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...

GitHub

Does the concept behind #python #httpx.Auth make sense?

Auth instances are responsible for setting up an Authorization header (or equivalent) but in some cases they might need to refresh their tokens or make other HTTP requests. httpx facilitates this by making Auth instances generators, and treating all but last yielded values as auth-related requests, and only the last one is the authorized user request.

Except I haven’t seen a library using this mechanism - all of them have their own inner httpx.Client instances

#programming

Ok, I got a #Python #HTTPX problem.

I have a few custom httpx.Auth implementations, but I want them to pull from some common flows--namely GitHub Actions get-an-OIDC.

In the standard form, you can just use `yield from`, and then requests and responses get shuffled around correctly, and you can just be like `token = yield from do_github()`

but then I need to do non-http async things, and it all gets messy.

because async generator can't use `yield from`, and all i've got is manual pumping.

HTTPX is a nice Python HTTP client. Here is a comparison of HTTPX synchronous and asynchronous clients.

https://gavinw.me/notes/python/httpx-sync-async.html

#python #httpx #async

Gavin Wiggins

Sync and Async HTTPX Comparison

How to modernise your requests-based API consumption code in #Python as if it were 2025. https://dev.to/dentedlogic/what-modern-python-uses-for-async-api-calls-httpx-taskgroups-3e4e #httpx #asyncio #requests
What Modern Python Uses for Async API Calls: HTTPX & TaskGroups

Multiple API calls in Python are usually written in a way that makes them slow You’ve...

DEV Community