RetroSearch Browse

Tue Feb 11 19:15:30 CET 2014 · https://mail.python.org/pipermail/python-dev/2014-February/132308.html

On Feb 11, 2014, at 12:30 PM, Guido van Rossum <guido at python.org> wrote:

> 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)
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/donald%40stufft.io

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140211/04437827/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/python-dev/attachments/20140211/04437827/attachment.sig>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-February/132308.html below:

[Python-Dev] Is the PIP requirement too strict?