home.social

#niquests — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #niquests, aggregated by home.social.

fetched live
  1. Zło To 🏴‍☠️ @[email protected] ·

    State of client side HTTP in #python

    - stdlib http.client - HTTP/1.1 only, docs recommend to use requests instead.
    - requests - poorly maintained, in 2020 stopped working when servers deprecated older TLS versions. HTTP/1.1 only, sync only
    - #httpx - comparatively slow and API design is driven by compatibility with browsers. Some users plug-in aiohttp for better performance. Supports HTTP/2 but it's discouraged as not optimized.
    - #aiohttp - good API, both client and server but seems more focused on the server side; HTTP/1.1 only.
    - #niquests - async fork of requests with HTTP/2, but uses forked urllib3 with the same package name as the original, which messes up deployment.
    - #aioquic - client & server, HTTP/3 only

    🤦

    #pythonRequests #programming

    #python #httpx #aiohttp #programming #niquests #aioquic
  2. Zło To 🏴‍☠️ @[email protected] ·

    State of client side HTTP in #python

    - stdlib http.client - HTTP/1.1 only, docs recommend to use requests instead.
    - requests - poorly maintained, in 2020 stopped working when servers deprecated older TLS versions. HTTP/1.1 only, sync only
    - #httpx - comparatively slow and API design is driven by compatibility with browsers. Some users plug-in aiohttp for better performance. Supports HTTP/2 but it's discouraged as not optimized.
    - #aiohttp - good API, both client and server but seems more focused on the server side; HTTP/1.1 only.
    - #niquests - async fork of requests with HTTP/2, but uses forked urllib3 with the same package name as the original, which messes up deployment.
    - #aioquic - client & server, HTTP/3 only

    🤦

    #pythonRequests #programming

    #python #httpx #aiohttp #programming #niquests #aioquic
  3. Zło To 🏴‍☠️ @[email protected] ·

    State of client side HTTP in #python

    - stdlib http.client - HTTP/1.1 only, docs recommend to use requests instead.
    - requests - poorly maintained, in 2020 stopped working when servers deprecated older TLS versions. HTTP/1.1 only, sync only
    - #httpx - comparatively slow and API design is driven by compatibility with browsers. Some users plug-in aiohttp for better performance. Supports HTTP/2 but it's discouraged as not optimized.
    - #aiohttp - good API, both client and server but seems more focused on the server side; HTTP/1.1 only.
    - #niquests - async fork of requests with HTTP/2, but uses forked urllib3 with the same package name as the original, which messes up deployment.
    - #aioquic - client & server, HTTP/3 only

    🤦

    #pythonRequests #programming

    #python #httpx #aiohttp #programming #niquests #aioquic
  4. Zło To 🏴‍☠️ @[email protected] ·

    State of client side HTTP in #python

    - stdlib http.client - HTTP/1.1 only, docs recommend to use requests instead.
    - requests - poorly maintained, in 2020 stopped working when servers deprecated older TLS versions. HTTP/1.1 only, sync only
    - #httpx - comparatively slow and API design is driven by compatibility with browsers. Some users plug-in aiohttp for better performance. Supports HTTP/2 but it's discouraged as not optimized.
    - #aiohttp - good API, both client and server but seems more focused on the server side; HTTP/1.1 only.
    - #niquests - async fork of requests with HTTP/2, but uses forked urllib3 with the same package name as the original, which messes up deployment.
    - #aioquic - client & server, HTTP/3 only

    🤦

    #pythonRequests #programming

    #pythonrequests #aioquic #niquests #programming #aiohttp #httpx
  5. Zło To 🏴‍☠️ @[email protected] ·

    State of client side HTTP in #python

    - stdlib http.client - HTTP/1.1 only, docs recommend to use requests instead.
    - requests - poorly maintained, in 2020 stopped working when servers deprecated older TLS versions. HTTP/1.1 only, sync only
    - #httpx - comparatively slow and API design is driven by compatibility with browsers. Some users plug-in aiohttp for better performance. Supports HTTP/2 but it's discouraged as not optimized.
    - #aiohttp - good API, both client and server but seems more focused on the server side; HTTP/1.1 only.
    - #niquests - async fork of requests with HTTP/2, but uses forked urllib3 with the same package name as the original, which messes up deployment.
    - #aioquic - client & server, HTTP/3 only

    🤦

    #pythonRequests #programming

    #python #httpx #aiohttp #programming #niquests #aioquic
  6. xiffy (but some call me appie) @[email protected] ·

    Niquests een drop-in replacement voor requests (of httpx) voor python (met http2.0 en meer): hackernoon.com/the-promise-tha
    #python #requests #niquests

    #niquests #requests #python
  7. xiffy (but some call me appie) @[email protected] ·

    Niquests een drop-in replacement voor requests (of httpx) voor python (met http2.0 en meer): hackernoon.com/the-promise-tha
    #python #requests #niquests

    #niquests #requests #python
  8. xiffy (but some call me appie) @[email protected] ·

    Niquests een drop-in replacement voor requests (of httpx) voor python (met http2.0 en meer): hackernoon.com/the-promise-tha
    #python #requests #niquests

    #niquests #requests #python
  9. xiffy (but some call me appie) @[email protected] ·

    Niquests een drop-in replacement voor requests (of httpx) voor python (met http2.0 en meer): hackernoon.com/the-promise-tha
    #python #requests #niquests

    #python #requests #niquests