[issue19744] test_venv and installation fail if SSL/TLS is not available

Roundup Robot added the comment: New changeset cd39d4cab680 by Nick Coghlan in branch '3.4': Issue #19744: Handle missing SSL/TLS in ensurepip http://hg.python.org/cpython/rev/cd39d4cab680 -- ___ Python tracker ___

[issue19744] test_venv and installation fail if SSL/TLS is not available

Nick Coghlan added the comment: Issue 20685 created to cover inclusion in 3.4.0, already committed to default, so closing this one. -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker

[issue19744] test_venv and installation fail if SSL/TLS is not available

Nick Coghlan added the comment: Thanks Ned - I fixed that test to only run if SSL/TLS is available, and added a new one to test that the command "succeeds" (with a warning printed to stderr) if SSL/TLS is missing. Larry - over to you to decide whether or not to cherry pick this into the relea

[issue19744] test_venv and installation fail if SSL/TLS is not available

Roundup Robot added the comment: New changeset 9f76adbac8b7 by Nick Coghlan in branch 'default': Issue #19744: Handle missing SSL/TLS in ensurepip http://hg.python.org/cpython/rev/9f76adbac8b7 -- ___ Python tracker

[issue19744] test_venv and installation fail if SSL/TLS is not available

Ned Deily added the comment: issue19744_ensurepip_install_ok_without_ssl.diff looks good to me. Note, though, that with it and with ssl support missing, test_ensurepip fails somewhat obscurely: == FAIL: test_bootstrap_version

[issue19744] test_venv and installation fail if SSL/TLS is not available

Nick Coghlan added the comment: Note: I'm deliberately not worrying about ensurepip._uninstall here, since that only gets invoked implicitly in the Windows uninstaller, and that should always have a valid SSL to play with. Always, since I worked out how to disable ssl in my local build (just a

[issue19744] test_venv and installation fail if SSL/TLS is not available

Nick Coghlan added the comment: This patch is probably a better bet - it just prints a message to stderr to say that we're ignoring the ensurepip failure during installation. pip wouldn't work anyway in a Python without ssl built, but at least this way that Python can still be installed withou

[issue19744] test_venv and installation fail if SSL/TLS is not available

Nick Coghlan added the comment: Attached patch tweaks the ensurepip CLI to check immediately for ssl support, and avoid printing a traceback if it is missing. However, missing SSL support still fails the call, which fails installation. -- keywords: +patch resolution: fixed -> stage: c

[issue19744] test_venv and installation fail if SSL/TLS is not available

Changes by Nick Coghlan : -- title: test_venv fails if SSL/TLS is not available -> test_venv and installation fail if SSL/TLS is not available ___ Python tracker ___ ___