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

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

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

Httpx:platzierungen được khoanh sát là kliện HTTP hiện đại cho các lập trình viên. Với hỗ trợ nguyên thủy cho async và sync, nó cung cấpישית tiện khả năng gia tăng hiệu suất và dễ dàng trong việc quản lý các yếu cầu HTTP. Hưởng thuện sử dụng nhu soi nhất ở ganado khác nhau, nâng cấp trải nghiệm phát triển python. #Httpx #KliệnHTTP #LậpTrình #Python #TechNews

https://www.reddit.com/r/programming/comments/1p4pshk/beyond_requests_why_httpx_is_the_modern_http/

Восемь высокопроизводительных Python-библиотек в копилку разработчикам

Когда в 1991 году Гвидо ван Россум представил миру Python, никто не мог предсказать, какое место через несколько десятилетий этот язык займет в веб-разработке, Data Science и Machine Learning. Сейчас Python продолжает развиваться: с новым поколением инструментов в прошлое уходят традиционные ограничения — производительность, GIL и сложность параллельных вычислений. Привет, Хабр! С вами Леша Жиряков, я руковожу бэкенд-направлением витрины KION, возглавляю гильдию по Python и пишу для блога MWS на Хабре. Я каждый день сталкиваюсь с вызовами высоконагруженных систем и сформировался пул инструментов, которые помогают решать критические проблемы современной разработки — от обработки данных с Polars до управления зависимостями с UV. В этом материале я сделаю обзор Python-библиотек, с которыми можно создавать системы, сравнимые по производительности с Go и Rust.

https://habr.com/ru/companies/ru_mts/articles/968776/

#библиотеки #python #fastapi #litestar #polars #httpx #dask #Pydantic_V2 #ruff #Pithon_UV