"M.-A. Lemburg" <mal@lemburg.com> writes: > What can we do about this ? The standard solution is to modify Modules/Setup at installation time, to suit your local needs. > Perhaps we should simply let setup.py build two extensions: _socket > (without SSL) and _socketssl (with SSL) ?! If the _socketssl build > or import fails for some reason, Python could still pick up the > _socket extension in socket.py. -1: Instead of avoiding to use an existing OpenSSL installation, it would be much better if the socket module was fixed to work with all existing versions. Of course, without a precise bug report, we cannot know whether this was possible. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4