#urllib3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #urllib3, aggregated by home.social.
-
APScheduler + requests 遇到 OSError: [Errno 24] Too many open files 的問題
#apscheduler #bug #code #collection #flask #gc #gunicorn #pypy #pypy3 #python #requests #source #urllib #urllib3 #workaround
-
APScheduler + requests 遇到 OSError: [Errno 24] Too many open files 的問題
#apscheduler #bug #code #collection #flask #gc #gunicorn #pypy #pypy3 #python #requests #source #urllib #urllib3 #workaround
-
I'm happy to announce that #urllib3 has a new lead maintainer: @illiav 👏 Illia has been contributing to urllib3 for over 3 years now and I'm confident will make a great lead of the project. I'll continue to maintain the project alongside my other co-maintainers @quentinpradet and @shazow
-
I'm happy to announce that #urllib3 has a new lead maintainer: @illiav 👏 Illia has been contributing to urllib3 for over 3 years now and I'm confident will make a great lead of the project. I'll continue to maintain the project alongside my other co-maintainers @quentinpradet and @shazow
-
I can't count how many times I've put
import requestsbehind a warnings filter after urllib3's developers decided they can dictate what libraries the end user has. -
It's here! The 2024 annual report for #urllib3, a relatively quiet year that included work on HTTP/2 and Web Assembly (WASM). We include our plans for Python 2 deprecation, please take a look. $3,300 worth of bounty issues exist today!
-
It's here! The 2024 annual report for #urllib3, a relatively quiet year that included work on HTTP/2 and Web Assembly (WASM). We include our plans for Python 2 deprecation, please take a look. $3,300 worth of bounty issues exist today!
-
Hot off the presses!!! 🔥 Find me at #AllThingsOpen tomorrow and tell me how you're supporting your open source middle-stack for a #urllib3 sticker!
-
Python's urllib3 has fixed a low severity vulnerability in version 2.2.2, which was released yesterday.
This vulnerability has been assigned CVE-2024-37891.
For those not familiar with urllib3, it describes it's self asa powerful, user-friendly HTTP client for Python
It is used by many projects and libraries, including the popular requests library.
https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf
-
Python's urllib3 has fixed a low severity vulnerability in version 2.2.2, which was released yesterday.
This vulnerability has been assigned CVE-2024-37891.
For those not familiar with urllib3, it describes it's self asa powerful, user-friendly HTTP client for Python
It is used by many projects and libraries, including the popular requests library.
https://github.com/urllib3/urllib3/security/advisories/GHSA-34jh-p97f-mpxf
-
Po prostu super. #urllib3 teraz wymaga inwazyjnego forka #HyperCorn do testów. Wzdych.
https://github.com/urllib3/urllib3/blob/2.2.0/dev-requirements.txt#L19
-
Just great. #urllib3 now requires an intrusive fork of #HyperCorn for testing. Sigh.
https://github.com/urllib3/urllib3/blob/2.2.0/dev-requirements.txt#L19
-
Just great. #urllib3 now requires an intrusive fork of #HyperCorn for testing. Sigh.
https://github.com/urllib3/urllib3/blob/2.2.0/dev-requirements.txt#L19
-
#urllib3 landed its first HTTP/2 PR, many more where that came from!
We're still fundraising to release HTTP/2 support, forward this URL to folks who have been wanting HTTP/2 support in #Python:
https://opencollective.com/urllib3/updates/urllib3-is-fundraising-for-http-2-support
-
#urllib3 landed its first HTTP/2 PR, many more where that came from!
We're still fundraising to release HTTP/2 support, forward this URL to folks who have been wanting HTTP/2 support in #Python:
https://opencollective.com/urllib3/updates/urllib3-is-fundraising-for-http-2-support
-
📦 We released #urllib3 v2.1.0 today! This release removes many of the features that have been deprecated for removal in v2. Security fixes will continue to be available in v1.26.x thanks to @[email protected]
-
New release of #urllib3, v1.26.16 backports a bugfix for PoolManager thread-safety when accessing a high number of distinct origins to not close responses before they complete: https://github.com/urllib3/urllib3/releases/tag/1.26.16
-
New release of #urllib3, v1.26.16 backports a bugfix for PoolManager thread-safety when accessing a high number of distinct origins to not close responses before they complete: https://github.com/urllib3/urllib3/releases/tag/1.26.16
-
#urllib3 2.0* is a true horror story. Whenever I fix one package not to downgrade my whole testing container to the previous version, I discover another broken package.
The most horrendous part is that they usually aren't broken by deliberate API changes — they rely on implementation details!
-
This whole #urllib3 / #OpenSSL situation is getting absurd.
I don't have sympathy for #OpenBSD or #LibreSSL. However, I can understand that they had good reasons to fork OpenSSL, and that switching back today would be hard.
I can understand projects refusing to officially declare support and rejecting workarounds. But pushing LibreSSL hate to the point of blocking #Python implementations that don't link to OpenSSL is just horrible. Users get in the crossfire, again.
-
This whole #urllib3 / #OpenSSL situation is getting absurd.
I don't have sympathy for #OpenBSD or #LibreSSL. However, I can understand that they had good reasons to fork OpenSSL, and that switching back today would be hard.
I can understand projects refusing to officially declare support and rejecting workarounds. But pushing LibreSSL hate to the point of blocking #Python implementations that don't link to OpenSSL is just horrible. Users get in the crossfire, again.
-
Oh, just great!
It turns out that #urllib3 added a totally bonkers OpenSSL version check, and they broke a lot of systems as a result. Ofc the immediate result is dozens of packages pinning urllib3 < 2, and if they continue their negligence it's going to go into hundreds.
Ofc, it is a mess that distro maintainers will have to clean up eventually. I mean, removing the pins when they do not apply to us.
https://github.com/urllib3/urllib3/issues/2168#issuecomment-1535053569
https://github.com/urllib3/urllib3/pull/2705/files#diff-793e73e680de400394dedf7d080fbcef6e74c065ffcc10b8c3dc11217a786e0b -
One thing that the #urllib3 team does that I wonder if other #opensource projects do is ensure someone is around to help in case of disasters. Very similar to on-call but ad-hoc and during fragile moments like releases of new default behaviors/major versions. Do any other projects do this?
-
One thing that the #urllib3 team does that I wonder if other #opensource projects do is ensure someone is around to help in case of disasters. Very similar to on-call but ad-hoc and during fragile moments like releases of new default behaviors/major versions. Do any other projects do this?
-
New #urllib3 JSON APIs making a cameo in @pamelafox's presentation slides! 🤩 #Python
-
#urllib3 v2.0.1 has been released with two small fixes:
– Fixed socket leak after failed cert hostname or fingerprint verification (thanks @graingert !)
– Fixed an issue when .read(0) was called on an empty response buffer (thanks @quentinpradet !) -
Over 1 million installs of a new major version in 24 hours (and single-digit number of integration issues 😏) #urllib3
https://pepy.tech/project/urllib3?versions=2.0.0
Next hurdle is being unpinned by Requests, then we'll *really* know if there are any big issues... 😬
-
Already over 250,000 installs of #urllib3 v2.0.0: https://pepy.tech/project/urllib3?versions=2.0.0
-
#urllib3 2.0.0 was released! FWICS most of the "breaking" changes are delayed until 2.1.0. However, I'm pretty sure I've seen some project importing vendored six from urllib3, and that's certainly going to break since it is gone ;-).
Ofc pinned <2 in random places is going to be a pain.
https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html
-
#urllib3 2.0.0 was released! FWICS most of the "breaking" changes are delayed until 2.1.0. However, I'm pretty sure I've seen some project importing vendored six from urllib3, and that's certainly going to break since it is gone ;-).
Ofc pinned <2 in random places is going to be a pain.
https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html
-
-
#urllib3 1.26.15 has been released! 📦 This is the first release that was kicked off by a community member.
https://github.com/urllib3/urllib3/releases/tag/1.26.15
This release contains a fix for socket timeout consistency on connection reuse and fixes for IDNA and URL encoding.
-
New article: "Working on #urllib3 full-time for one week"
👉 https://sethmlarson.dev/working-on-urllib3-full-time-for-one-week
@quentinpradet and I took one week off of our normal day jobs in early November to push urllib3 v2.0.0 over the finish line. We were successful and we've both written about our experiences.
-
I'm the guest of #Tidelift's webinar on #urllib3, #Python, and #OpenSource supply chain security happening later today, hope to see you there: https://tidelift.com/how-the-maintainers-of-urllib3-keep-the-project-secure-and-healthy
-
@brettcannon @simon @kenlai We're used to #Python 2.7 being at 50% and all 3.x releases being some portion of the remaining 50% (usually 10-15% each). Now with 2.7 mostly gone I think we're seeing more healthy upgrade behavior across 3.x versions. From #urllib3's stats across all downloads:
- 12% 3.6
- 30% 3.7
- 22% 3.8
- 12% 3.9
- 7% 3.10
- 2% 3.11Anecdotally from talking to others I believe multi-hop (eg 3.6->3.9) upgrades are being much more common, too!
-
Building the #urllib3 v2.0 changelog, almost 100 changes!! https://github.com/urllib3/urllib3/pull/2795
-
#Tidelift has published a three part series about #urllib3: the most downloaded #Python package with over 3billion/year downloads. 🤯
The series details how Quentin and I think about security, processes, tooling, and maintenance of critical #Python and #opensource infrastructure. Hope you give them a read and learn something new!
– https://blog.tidelift.com/urllib3-part-1
– https://blog.tidelift.com/urllib3-part-2
– https://blog.tidelift.com/urllib3-part-3
