> I don't think it was a mistake. First, even though Python had been > using autoconf for years, nobody came up with a complete patch to > autoconfiscate Modules/Setup, or define a different configuration > mechanism. So using setup.py was an improvement over the status quo, > even if not an improvement over some not-implemented technique - which > might have never been implemented. > > Furthermore, as Marc-André points out: there is nothing that stops > setup.py/distutils from using the same strategies as autoconf. > > Finally, in this specific case, I do think that the best strategy is > to check for the version of OpenSSL. This is against autoconf > philosophy (check for features, not for versions), but since the SSL > support is tied to a specific implementation, rather than an API with > competing implementations, checking the version does no harm and > simplifies the configuration machinery. So, is this a showstopper issue for the release candidate? I believe Neil went on vacation today. I'd like to have a release out in 6 hours. Should I try to get this fixed??? --Guido van Rossum (home page: http://www.python.org/~guido/)
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