Incompatible with httpcore 0.12.0

[Simon-Le]

The version 0.12.0 of httpcore is not compatible. When this version is installed, all the tests using httpx.Client() will fail with the following error

AttributeError: 'Client' object has no attribute '_transport'

[florimondmanca]

Hey 👋

Indeed, I'm also getting an error about retries which was only added in 0.12.1:

$ pipinstallhttpxhttpcore==0.12.0
$ python>>>importhttpx>>>client=httpx.Client()
Traceback (mostrecentcalllast):
File"<stdin>", line1, in<module>File"/Users/florimond.manca/.pyenv/versions/3.8.5/lib/python3.8/site-packages/httpx/_client.py", line605, in__init__self._transport=self._init_transport(
File"/Users/florimond.manca/.pyenv/versions/3.8.5/lib/python3.8/site-packages/httpx/_client.py", line652, in_init_transportreturnHTTPTransport(
File"/Users/florimond.manca/.pyenv/versions/3.8.5/lib/python3.8/site-packages/httpx/_transports/default.py", line58, in__init__self._pool=httpcore.SyncConnectionPool(
TypeError: __init__() gotanunexpectedkeywordargument'retries'

And then exiting the interpreter shows the exception you're mentioning that comes from Client.__del__:

Exceptionignoredin: <functionClient.__del__at0x1013363a0>Traceback (mostrecentcalllast):
File"/Users/florimond.manca/.pyenv/versions/3.8.5/lib/python3.8/site-packages/httpx/_client.py", line1134, in__del__self.close()
File"/Users/florimond.manca/.pyenv/versions/3.8.5/lib/python3.8/site-packages/httpx/_client.py", line1106, incloseself._transport.close()
AttributeError: 'Client'objecthasnoattribute'_transport'

The reason is that self._transport = ... was aborted mid-way, so the Client object that's still in memory doesn't have a _transport attribute yet, but __del__ assumes so.

Upgrading to httpcore==0.12.1 fixes it, yes. :-)

[florimondmanca]

Thanks!

[johtso]

Argh, awkward. Is there any reasonable way to catch this kind of thing in tests? Testing with every combination of dependency versions specified in setup.py probably isn't viable. Maybe there's something simple we could do that would catch the majority of slip ups though? Maybe just test with the oldest and the newest version of httpcore allowed?

[florimondmanca]

Testing against the oldest HTTPCore version as per the HTTPX requirement sounds sensible.

I'm not sure about running this as part of every CI run, but maybe we could start with that. Only putting it as a task in the release job would mean we only catch these issues once the release is ready, ideally that would be before.

Another option is to actually work locally with the lowest HTTPCore possible. That would mean pinning HTTPCore strictly in our requirements.txt, such that any API changes done separately are caught because we'd need to bump that version to continue working on HTTPX. Then we could have a simple test in the test suite to verify that this number is effectively the lowest possible number for the range specified in setup.py. I think I'd prefer this approach. Thoughts?