by SethMLarson on 1/30/24, 5:05 PM with 32 comments
by codingglass on 1/31/24, 1:53 AM
Then 'pyodide-http' got adopted into the Pyodide-included packages[2], so you didn't have to specify it for install, just import it and run patch_all().
And now a similar technique has been incorporated directly into urllib3. (Not a direct port - as far as I know Joe Marshall and others did a full reimplementation so that urllib3's API's would be maintained as much as possible). [2]
Very cool.
Edit: Looks like there's a note to this same effect on Seth Larson's post about urllib3's future. [3]
[1] https://github.com/koenvo/pyodide-http
[2] https://pyodide.org/en/stable/usage/packages-in-pyodide.html
[3] https://sethmlarson.dev/urllib3-is-fundraising-for-http2-sup...
by Austizzle on 1/30/24, 9:41 PM
by Extigy on 1/30/24, 6:52 PM
by canadiantim on 1/30/24, 5:12 PM
What does this practically mean?
Does this ever point to a future where we can use urlib3 instead of fetch?
by hoodchatham on 1/31/24, 3:43 AM
by hpeter on 1/30/24, 6:41 PM