import eventlet still patches everything

[Glueon]

In the docs you write:

We’ve in the past considered doing this automatically upon importing Eventlet, but have decided against that course of action because it is un-Pythonic to change the behavior of module A simply by importing module B.

I was working on a project which uses eventlet in some parts of the system and thus imports eventlet. Also I use HTTPretty to test some functionallity. Just a simple import eventlet "greens" some standard libraries thefore breaking the httpretty functionallity. It does not always break. For example if I mock an 'http' request it works fine and breaks only on 'https'.

Here is an open issue on httpretty gabrielfalcao/HTTPretty#254

I think that it's HTTPretty fault it breaks when eventlet greens the world but that auto-monkeypatching upon simple import seems to be quite unpredictable.

[temoto]

Hello. Thanks for reproduction code, I've used it to bisect breaker commit.

I couldn't get FakeSSLSocket error since Eventlet v0.15, but OSError Socket is not connected is showing up since b2e5146

[Glueon]

@temoto I used the the latest eventlet version. My concrete example was invoked via pytest but as far as I remember repl gives the same result.

What is interesting that this all works fine with the responses library.

[davidszotten]

also hitting this. i was surprised to find eventlet applying monkey-patches at import time (simply import eventlet triggers the monkey-patch at the bottom of eventlet/green/ssl.py)

is this a "bug"?

[temoto]

It is a bug.

[temoto]

Sorry for leaving this issue open.