Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • A network error occurred. Please check your connection and try again. If this issue persists please contact us through our help center at help.openai.com.

    yeah nice engineering clowns

    by i574n
  • nb: operating system TLS trust store is used now (instead of certifi)
    by tosh
  • All this for an SDK you might not need.

    SDK is just a wrapper around POST https://api.openai.com/v1/responses

    Just REST + JSON.

    streaming (sse parsing) + tool calling + structured outputs + pagination are easy to do.

    by tulio_ribeiro
  • There seems to be a bunch of downsides mentioned...

    But what are the upsides of this change?

    by londons_explore
  • we have recently switched from httpx for the same reason but instead went with the Rust-based pyqwest (runs on Hyper) it has also a drop-in httpx-compatible transport so migration was easy and also it supports http2 trailers

    https://pyqwest.dev

    by ushakov
  • Wonder if they evaluated httpx2 vs niquests: https://github.com/jawah/niquests
    by jklehm
  • Anthropic made the same change a few weeks after OpenAI did: https://github.com/anthropics/anthropic-sdk-python/releases/...

    The problem with httpx as a dependency is that it's currently working towards a 1.0 release which will be full of breaking changes.

    The httpx2 project is essentially a fork that promises not to break the existing API, which makes it a more stable dependency to build against.

    I wrote a pretty long comment about my concerns for the breaking 1.0 version last year - https://github.com/encode/httpx/discussions/3344#discussionc... - in that comment I recommended the HTTPX project release their 1.0 as a package called httpx2 instead, but a year later we now have an httpx2 (released by a different maintainer) that keeps the old API.

    by simonw

Explore Birbla archives