Better error message on failing to create a venv due to failing ensurepip

[JulienPalard]

BPO	45667
Nosy	@JulienPalard

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2021-10-29.10:00:06.597>
labels = []
title = 'Better error message on failing to create a venv due to failing ensurepip'
updated_at = <Date 2021-10-29.10:00:06.597>
user = 'https://github.com/JulienPalard'

bugs.python.org fields:

activity = <Date 2021-10-29.10:00:06.597>
actor = 'mdk'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-10-29.10:00:06.597>
creator = 'mdk'
dependencies = []
files = []
hgrepos = []
issue_num = 45667
keywords = []
message_count = 1.0
messages = ['405297']
nosy_count = 1.0
nosy_names = ['mdk']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45667'
versions = []

[JulienPalard]

Currently if ensurepip fails for a reason or another, for example if a wrong module gets imported:

$ touch http.py
$ python3.10 -m venv .venv
Error: Command '['/tmp/.venv/bin/python3.10', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.

the error is not helpfull. Maybe venv should just dump the stderr from ensurepip so we can learn a bit more about it (it's « understandable » in ensurepip traceback that it's in relation with http.py, in the given example.)