That is correct. For awhile now Python has had an adhoc concept of
environment markers, but there wasn't standard for what they were and
what they supported so each implementation was slightly different (this
is a common theme with Python packaging). We attempted to standardize
this in PEP 508 whic
Public bug reported:
In the upstream version v20.2 setuptools switched implementations of
parser libraries. This is an internal implementation detail, however the
new parser library did not correctly handle several edge cases which
caused regressions preventing certain packages from installing or,
FWIW I think that ``python -m venv`` is the easiest (only?) way to
reliably say that you want to create a virtual environment for *this*
particular Python. This is especially important when multiple versions
of Python that have venv start to be able to be installed (either via
the system repos, or
hon-venv/bin/python3.4', '-Im',
> 'ensurepip',
> '--upgrade', '--default-pip']' returned non-zero exit status 1
>
> # works, but no pip
> python3.4 -m venv --clear --without-pip python-venv
>
> Thank you
>
> To manage noti
status 1
>
> # works, but no pip
> python3.4 -m venv --clear --without-pip python-venv
>
> Thank you
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions
>
>
---
Donald
You can work around this by doing:
python3 -m venv --without-pip /tmp/env
curl https://bootstrap.pypa.io/get-pip.py | /tmp/env/bin/pyython
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bu
Can we just add the Wheel files to ensurepip for Trusty? It's already
being done for virtualenv (which is why it works at all) and that should
be way less impact than having to do the full backport that the other
thing would require.
--
You received this bug notification because you are a member
Public bug reported:
[Impact]
* Anyone attempting to use the pyenv script from Python 3.4 will be met
with a fairly confusing error by default. This would have worked fine in
saucy and raring.
* While this can be worked around by adding a flag to the pyvenv
script, it also removes the ability
8 matches
Mail list logo
