Is the PIP requirement too strict?
I don't happen to have OpenSSL configured on my OSX dev box right now. This usually leads to some warnings during the build stage and obviously various ssl-based tests don't work, but I can still get other stuff done. But with the latest repo, "make install" refuses to complete -- it ends fatally as follows: if test "xupgrade" != "xno" ; then \ case upgrade in \ upgrade) ensurepip="--upgrade" ;; \ install|*) ensurepip="" ;; \ esac; \ ./python.exe -E -m ensurepip \ $ensurepip --root=/ ; \ fi Traceback (most recent call last): File "/Users/guido/cpython/Lib/runpy.py", line 171, in _run_module_as_main "__main__", mod_spec) File "/Users/guido/cpython/Lib/runpy.py", line 86, in _run_code exec(code, run_globals) File "/Users/guido/cpython/Lib/ensurepip/__main__.py", line 4, in <module> ensurepip._main() File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 203, in _main default_pip=args.default_pip, File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 74, in bootstrap _require_ssl_for_pip() File "/Users/guido/cpython/Lib/ensurepip/__init__.py", line 23, in _require_ssl_for_pip raise RuntimeError(_MISSING_SSL_MESSAGE) RuntimeError: pip 1.5.2 requires SSL/TLS make: *** [install] Error 1 Can this failure be suppressed in the Makefile (given that I know what I'm doing)? -- --Guido van Rossum (python.org/~guido)
On Feb 11, 2014, at 12:30 PM, Guido van Rossum <guido@python.org> wrote:
So right now pip doesn’t work without TLS, we’re working on that and our 1.6 release should have that. I *thought* that Nick (I think?) had made it so that you just didn’t get pip if you didn’t have TLS enabled, but apparently not. You can suppress this by doing ``ENSUREPIP=no make install``, but probably this should just print a warning instead of dying when TLS isn’t available. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Right, I think this is a genuine bug in the ensurepip CLI mode. http://bugs.python.org/issue19744 was still pending with Tim (to see if it solved the original problem), but we need to more gracefully handle the error at the CLI level as well.
In article <CAP7+vJ+3sxE6LNt8QeHdni3-E4RwNTpqLVqNsGKLppCMWGA=yw@mail.gmail.com>, Guido van Rossum <guido@python.org> wrote:
As a side note, you shouldn't have to configure OpenSSL to build any of the current branches of Python on OS X systems. It should build gracefully with the Apple-supplied headers and libssl/libcrypto, modulo possible deprecation warnings in the recent releases of OS X. -- Ned Deily, nad@acm.org
To follow up, Ned diagnosed this for me off-list. The cause was my recent upgrade to Mavericks, which causes the Xcode 5 command line tools to be installed differently. In case others have the same issue, the solution was to run: xcode-select --install (and accept the dialog box it pops up). This is a common issue with Mavericks and open-source projects (not just Python); Ned will add something to the README. --Guido On Tue, Feb 11, 2014 at 2:22 PM, Ned Deily <nad@acm.org> wrote:
-- --Guido van Rossum (python.org/~guido)
On Feb 11, 2014, at 12:30 PM, Guido van Rossum <guido@python.org> wrote:
So right now pip doesn’t work without TLS, we’re working on that and our 1.6 release should have that. I *thought* that Nick (I think?) had made it so that you just didn’t get pip if you didn’t have TLS enabled, but apparently not. You can suppress this by doing ``ENSUREPIP=no make install``, but probably this should just print a warning instead of dying when TLS isn’t available. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
Right, I think this is a genuine bug in the ensurepip CLI mode. http://bugs.python.org/issue19744 was still pending with Tim (to see if it solved the original problem), but we need to more gracefully handle the error at the CLI level as well.
In article <CAP7+vJ+3sxE6LNt8QeHdni3-E4RwNTpqLVqNsGKLppCMWGA=yw@mail.gmail.com>, Guido van Rossum <guido@python.org> wrote:
As a side note, you shouldn't have to configure OpenSSL to build any of the current branches of Python on OS X systems. It should build gracefully with the Apple-supplied headers and libssl/libcrypto, modulo possible deprecation warnings in the recent releases of OS X. -- Ned Deily, nad@acm.org
To follow up, Ned diagnosed this for me off-list. The cause was my recent upgrade to Mavericks, which causes the Xcode 5 command line tools to be installed differently. In case others have the same issue, the solution was to run: xcode-select --install (and accept the dialog box it pops up). This is a common issue with Mavericks and open-source projects (not just Python); Ned will add something to the README. --Guido On Tue, Feb 11, 2014 at 2:22 PM, Ned Deily <nad@acm.org> wrote:
-- --Guido van Rossum (python.org/~guido)
participants (4)
-
Donald Stufft -
Guido van Rossum -
Ned Deily -
Nick Coghlan