Giorgio Salluzzo

It's again something happening when the URL scheme is HTTPS.

I've just opened an [issue](https://github.com/aio-libs/aiohttp/issues/9510) on their side, let's see if and what they answer.

A temporary fix would be moving `import aiohttp` to a portion of code running while Mocket is already in control of the `ssl` module (see https://github.com/mindflayer/python-mocket/blob/main/tests/test_asyncio.py#L48).

Mocket `3.12.3` introduces a `connector` plugin for when things go wrong while testing HTTPS calls with `aiohttp`. See https://github.com/mindflayer/python-mocket/blob/main/tests/test_asyncio.py#L49.

I don't believe that having a socket that is left open for a while would be an issue, but I may be wrong. I haven't spent time on trying to...

Hi @piranna, are you considering helping with this, or it was just a feature request? I am asking this because I believe I won't be able to help with that...

I honestly don't think we need a fork of HTTPretty. I am the author of Mocket, project born in 2013, and there are already several known libraries relying on it...

Why not simply making them into `@property`? Something like: ``` class TCPConnector(BaseConnector): _SSL_CONTEXT_VERIFIED = None ... @property def ssl_context_verified(self): if not self._SSL_CONTEXT_VERIFIED: self._SSL_CONTEXT_VERIFIED = ... return self._SSL_CONTEXT_VERIFIED ... ``` In...

> I'm not overly clear what the issue is. Are you saying you don't mock aiohttp, but mock the ssl calls? So, in this case you're trying to mock the...

> If we simply revert the change, then I think the behaviour of your library would still be incorrect.. Before v .6 everything worked perfectly. Mocket is currently used for...