search

ovh / python-ovh

Thin wrapper around OVH's APIs. Handles all the hard work including credential creation and requests signing.
https://pypi.org/project/ovh/
Other
296 stars 81 forks source link

[Proposal] Migrate to HTTP Niquests #128

Closed Ousret closed 10 months ago

Ousret commented 10 months ago

Hello OVH,

I am proposing to migrate the project from Requests to the compatible Niquests. Here a few reasons why:

This new client ship with an advanced TLS certification validation mechanism that rely on the OCSP protocol, With this, add the capability to leverage an encrypted DNS resolver on the protocol of your choosing, like but not limited to: "DNS over HTTPS, DNS over QUIC, ...". The TLS negotiation has been revised to be stricter, for example, denying unsafe tls renegotiation.

Also, this client no longer relies on Certifi but rather on the trusted operating system store.

It is significantly faster and propose up to date protocols, mentioning it even if OVH api does seems to propose HTTP/2 or 3. In addition to that, you can find async interfaces if needed. Also, if you decide, to offer HTTP/2+, Niquests is natively capable to leverage a multiplexed connection.

You don't have to worry one bit about the compatibility, it is backward compatible, in fact, this project strictly extend its solid bases (requests).

There's a ton of improvement that you can discover at https://github.com/jawah/niquests Also, Niquests is made in :fr:

deathiop commented 10 months ago

Hello @Ousret,

First of all, thank you for this proposal. However, we are declining it: we aim at relying on wildly known and used dependencies with this SDK, so the community does not have to wonder what we are importing in their project, whether OVHcloud SDKs can be trusted, etc. We wish all the best to the Niquest project, but one cannot yet say it reached a satisfying adoption level for us to consider this change.