Recognizing httpx.Client settings with custom Transports

[lu-pl]

Hello,

I have a question regarding the behavior of httpx.Client in the context of custom Transports (i.e. httpx.BaseTransport subclasses).

I am implementing a SPARQL Protocol client that, apart from targeting remote endpoints, also supports running queries against in-memory Graph objects. The Graph object feature is implemented using custom Transport classes that essentially delegate any SPARQL operation request to the given Graph object instead of a remote endpoint.

These are my current Transport definitions: https://github.com/lu-pl/sparqlx/blob/main/src/sparqlx/utils/transports.py

I just realized that for any httpx.Client initialized with those Transports, client settings like e.g. timeouts are not recognized. It seems like httpx-defined transports like e.g. httpx.WSGITransport do not recognize client settings either (as far as I can tell).

So I am wondering: Are client configs even meaningful with custom transports? If yes, how to best implement client config recognition with custom transports?

Any help is much appreciated! :)