Would it be too much to ask for this bug to not be marked as "fix
released", given that it's not fixed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title
Matthias, that command clearly only works if you have sudo access. This
makes it a bad idea for *most* of the scripts that would need to use the
pyvenv command.
Like I said, you should not need elevated privileges to use the Python
standard library. Especially something whose purpose is to make it
As an example of why this matters, you do not typically need root access
to use the Python standard library.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1290847
> This should work after you apt-get install python3-venv
> (python3.4-venv).
venv is a module in the Python 3 standard library. I don't understand
why it would need a separate package on Ubuntu.
Someone who's installing additional packages could just as well install
the better-understood python3
This seems to be broken in Vivid beta:
$ python3 -m venv testenv
Error: Command '['/home/rspeer/testenv/bin/python3', '-Im', 'ensurepip',
'--upgrade', '--default-pip']' returned non-zero exit status 1
I know that virtualenv can be installed separately, but it's a big wart
that Python 3 i
5 matches
Mail list logo
