Not a fix but a workaround: I use the virtualenv package instead, rather
than -m venv.
--
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:
pyvenv fails
Yes, 5 years later this is still broken. What can we do to install a
venv, please?
--
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:
pyvenv fails due
I'm sorry to post to this ancient bug, but I just did a fresh install of
Ubuntu 18.04, and I just want to create a virtual env with python 3.7,
including pip (or some way to install modules). Doing this does not
work:
% sudo apt install python3.7 python3.7-venv
% python3.7 -m venv py37-venv
It gi
On Oct 16, 2015, at 03:17 PM, Harry P wrote:
>I'm now testing Ubuntu 15.10, which seems *even more* broken, since it
>seems to have a mixed mode of Python3.4 and 3.5. there's no
>python3.4-pip package, which means there is essentially no way of
>getting a working pip for python 3.4.
Tools like p
I'm now testing Ubuntu 15.10, which seems *even more* broken, since it
seems to have a mixed mode of Python3.4 and 3.5. there's no
python3.4-pip package, which means there is essentially no way of
getting a working pip for python 3.4.
I know I'm not a contributor, so I don't *deserve* answers, bu
I can confirm what Mali says. No python3[*]-venv in the repositories.
And the python3 -m venv gives the error that kickstarted this lengthy
fix process.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubun
Hi Matthias et al,
Did this used to be on trusty? We added it to a deployment script about
a week and a half ago and it worked on an 14.04 ec2 image, but then as
of today doing a deploy with a fresh image it doesn't seem to be finding
python3.4-venv or python3-venv, and we're back to square one. :
Thanks that seems to work
Jose
On 09/24/2015 08:57 PM, Matthias Klose wrote:
> On 25.09.2015 02:40, jose wrote:
>> There is no python3-venv package in 14.04 how do I get it? or where do I
>> find it?
> this is work in progress, for now please install the python3.4-venv
> package.
>
--
You receiv
On 25.09.2015 02:40, jose wrote:
> There is no python3-venv package in 14.04 how do I get it? or where do I
> find it?
this is work in progress, for now please install the python3.4-venv
package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
There is no python3-venv package in 14.04 how do I get it? or where do I
find it?
Jose
On 09/14/2015 10:18 AM, Dario Bertini wrote:
> @rspeer @wolfgang-richter
>
> The bug is "sort of fixed"
>
> You have to install python3-venv, this will make the ensurepip module
> available, and the creation of
There have been some discussions about this via other channels (e.g.
IRC). We're probably at least going to patch Python so that if you try
to do `python3 -m venv` and ensurepip (i.e. via python3-venv binary
package) isn't installed, you'll get a more helpful message that
instructs you to `sudo ap
PS: the bug I found is not truly a bug, just a difference in behaviour
between venv and virtualenv:
the former won't allow you to locally install packages when created with
--system-site-packages (making that flag effectively useless, imho),
while virtualenv will allow you to layer local packages
This is it: https://bugs.python.org/issue24875
--
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:
pyvenv fails due to mising ensurepip module
Status i
@rspeer @wolfgang-richter
The bug is "sort of fixed"
You have to install python3-venv, this will make the ensurepip module
available, and the creation of a virtualenv will succeed
Imho this is an horrible naming choice: the error you'll get when trying
to run `python3 -m venv` mentions ensurepip
i dont know what happens in distro land, but the rest of the world
expects to be able to follow the docs at python.org without any more
fuss than "install python3"
in the future, if you really need a broken up python package for
whatever reason, could you make a python3-tiny like vim-tiny, that th
I just encountered this bug. I do not see the aforementioned pyvenv
packages anymore, and this renders programmatically creating virtual
envs (a la EnvBuilder style) completely broken.
Is there any roadmap to fixing this in 14.04 ?
--
You received this bug notification because you are a member
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
On Jun 25, 2015, at 04:31 PM, Donald Stufft wrote:
>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.
Even though I don't generally use it, I agree with the above.
--
You received this bu
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
FTR,
python3 -m venv env
Doesn't work either for me.
--
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:
pyvenv fails due to mising ensurepip modu
I call it directly also.
--
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:
pyvenv fails due to mising ensurepip module
Status in python3-defaults pac
On Jun 25, 2015, at 11:13 AM, Jonas Thiem wrote:
>Who calls pyvenv directly?
I do.
--
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:
pyvenv fails du
Regarding a different matter: above python3-venv was mentioned for
Ubuntu 14.04 (Trusty), but I can't find such a package (neither
python3-virtualenv). Maybe a listing for which ubuntu releases and which
python versions this is supposed to be fixed would be helpful to stop
people from asking.
--
Who calls pyvenv directly? People just use python3 -m venv which, as
people pointed out above, is expected by everyone to be fully working
and available with any python3 install _without_ separately installed
packages. Sure distributions have different conventions, but python was
always packaged wi
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
On 06/17/2015 06:27 PM, Harry P wrote:
> I do a fair bit of work with beginner Python tutorials. It's not often
> that we have to say "on linux, this is harder", but this is one area
> where ubuntu/debian are failing pretty hard compared to the mac +
> windows experience.
$ pyvenv
The program 'py
On 06/17/2015 06:33 PM, Donald Stufft wrote:
> I think it should be installed by default because it is a documented part
> of the Python language. I think the Debian/Ubuntu Python is fundamentally
> broken by default as it is currently.
No, a distribution has it's own conventions and policies. We
> if they address a different issue, the venv package doesn't need to be
> installed by default.
But again, pyvenv isn't a separated thing from Python. Everywhere except in
Debian/Ubuntu, It's shipped with Python itself, since it's part of the standard
library.
If you need to install extra packa
I think it should be installed by default because it is a documented part
of the Python language. I think the Debian/Ubuntu Python is fundamentally
broken by default as it is currently.
On June 17, 2015 at 12:30:58 PM, Matthias Klose (d...@ubuntu.com) wrote:
> On 06/17/2015 06:12 PM, Donald Stufft
I do a fair bit of work with beginner Python tutorials. It's not often
that we have to say "on linux, this is harder", but this is one area
where ubuntu/debian are failing pretty hard compared to the mac +
windows experience.
--
You received this bug notification because you are a member of Ubun
On 06/17/2015 06:12 PM, Donald Stufft wrote:
> virtual environments and distro packages solve entirely different problems
> though. They aren’t two solutions to the same problem.
if they address a different issue, the venv package doesn't need to be installed
by default.
--
You received this bug
> I don't think the installation by default would be a good idea.
> This is distro land, and I think we should promote using the distro packages.
> People wanting to install venv and pip know how to do this.
But pyvenv is, since release 3.4, part of the Python standard library. It's not
a separate
virtual environments and distro packages solve entirely different problems
though. They aren’t two solutions to the same problem.
On June 17, 2015 at 12:11:28 PM, Matthias Klose (d...@ubuntu.com) wrote:
> I don't think the installation by default would be a good idea. This is
> distro land, and I
I don't think the installation by default would be a good idea. This is
distro land, and I think we should promote using the distro packages.
People wanting to install venv and pip know how to do this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
On Jun 16, 2015, at 11:37 AM, Jonas Thiem wrote:
>Is there any chance this will be made available without a separate
>python3-venv package? Since python 3.3 or 3.4 venv is considered as a
>core package, so the requirement to install python3-venv is somewhat
>non-intuitive.
Would it be good enough
Is there any chance this will be made available without a separate
python3-venv package? Since python 3.3 or 3.4 venv is considered as a
core package, so the requirement to install python3-venv is somewhat
non-intuitive.
Python developers in any sort of support chat will also always tell you
that
If this is fixed, why is pyvenv-3.4 not working for me without
"--without-pip"?
--
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:
pyvenv fails due to
I have to agree Rob. Having python3-venv as a new and separate package
makes it only confusing for developers. I could live with this, if the
package would be a dependency of python3, so it gets installed
automatically.
--
You received this bug notification because you are a member of Ubuntu
Touc
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
On Mar 31, 2015, at 12:49 PM, jose wrote:
>Now that it looks like the package is fixed for Vivid, are there plans
>to backport to Trusty? and do we know when that may be?
LP: #1433324 and LP: #1348954
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Now that it looks like the package is fixed for Vivid, are there plans
to backport to Trusty? and do we know when that may be?
Thanks
Jose
On 03/02/2015 09:25 AM, Barry Warsaw wrote:
> We still need to work on backporting to Trusty and doing the SRU. I
> don't know when I will have time to do t
This seems to do the trick, if somewhat clumsily.
** Attachment added: "lp1290847.txt"
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847/+attachment/4361252/+files/lp1290847.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Yes, and actually I thought we did! I'll attach a patch after some
testing.
--
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:
pyvenv fails due to mis
On Monday, March 30, 2015 05:07:44 AM you wrote:
> On Mar 30, 2015, at 02:04 AM, Rob Speer wrote:
> >$ python3 -m venv testenv
> >Error: Command '['/home/rspeer/testenv/bin/python3', '-Im',
> >'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit
> >status 1
> This shou
On Mar 30, 2015, at 02:04 AM, Rob Speer wrote:
>$ python3 -m venv testenv
>Error: Command '['/home/rspeer/testenv/bin/python3', '-Im', 'ensurepip',
> '--upgrade', '--default-pip']' returned non-zero exit status 1
This should work after you apt-get install python3-venv
(python3.4-venv).
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
We still need to work on backporting to Trusty and doing the SRU. I
don't know when I will have time to do that though. :(
--
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
Python 3.4.3 is out. I did a apt-get upgrade, but am still getting this
error. I see my python is 3.4, not 3.4.2 or 3.4.3. Do I need to add a
repo to get this? Am I missing something?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
On Jan 20, 2015, at 05:07 PM, Kapil Thangavelu wrote:
>bug says fixed released, but this is still an issue on trusty. i don't
>see the value of virtualenvs without pip so that's not a viable
>workaround.
It's only pyvenv which currently doesn't work in Trusty. virtualenv still
works (always has)
bug says fixed released, but this is still an issue on trusty. i don't
see the value of virtualenvs without pip so that's not a viable
workaround.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
htt
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
#17 works ...
The source code for ensurepip can be found in the python.org tarball
https://www.python.org/ftp/python/3.4.2/Python-3.4.2.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://
Please, fix this. Ubuntu is the one of the most popular linux distros,
and python3 is currently supported by almost every alive package. And
it's very sad, to have such problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Any progress on this?
--
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:
pyvenv fails due to mising ensurepip module
Status in “python3-defaults” pack
debdiff sent to Doko
--
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:
pyvenv fails due to mising ensurepip module
Status in “python3-defaults” packa
The PPA version doesn't fix this problem. I have a workaround for this
bug, and a fix for LP: #1367907 that would both be appropriate to SRU.
I'll get together with Doko to get him my patches.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
this is all prepared in the ubuntu-toolchain-r/ppa PPA. you might want to test
it. I won't work on this before the 14.10 release.
--
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.launch
On Sep 22, 2014, at 07:44 PM, Donald Stufft wrote:
>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.
I'm not
barry: Kay, if they wouldn't be 100% compatible, I agree it's a bad
idea, so just printing the "yo, this is broken, try the other
thing" would be fine, IMO.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
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
I apologize for going back and forth on this bug so often. It may
simply be not feasible to SRU a fix for this. The fix is not just in
the python3.4 package. I think at a minimum this means:
* Backporting wheel to trusty. It was first available in utopic, so i'm
not even sure if it's appropri
another work around is to do:
sudo apt-get install python-virtualenv
virtualenv myvenv -p python3
--
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:
I've gotten tired of waiting. I create the environment without pip and then
install pip manually from the website. Not sure what issues that will cause
down the road but it seems to work for now
Jose
Original Message
Subject: [Bug 1290847] Re: pyvenv fails due to mising ensur
On Tuesday, September 09, 2014 05:24:32 you wrote:
> Will this get a stable release update? If yes, how do I track when the
> bug is fixed in Trusty?
It's my understanding that this is planned, but I'm not the one doing the
work. For trusty status, you'd see bug status changes that specifically
Will this get a stable release update? If yes, how do I track when the
bug is fixed in Trusty?
--
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:
pyven
On Monday, September 08, 2014 14:40:53 you wrote:
> Why this is marked as "Fix Released? This is still broken.
Fixed released means fixed in the development series, not necessarily in
released versions of Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch see
Why this is marked as "Fix Released? This is still broken.
--
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:
pyvenv fails due to mising ensurepip modu
Ah sorry, the previous comment is incorrect. My mistake, please ignore
it. :(
--
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:
pyvenv fails due to mi
This is already released to trusty; just run apt-get upgrade and you
will get it.
--
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:
pyvenv fails due t
Anyone know if and when this fix is planned to be backported to trusty
(i.e. the current Ubuntu release)? There doesn't seem to be any
information in this bug report to indicate one way or the other. I
actually don't even know which version of the python3.4 package fixes
it. (Isn't that something b
How can I keep track of the update process or download pre-release
versions? Fixes have yet to hit the testing (pre-release) repository.
--
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.
Pierre, this seemed to work for me:
$ sudo apt-get install python-virtualenv
$ virtualenv /desired/path/to/env
$ which pip
/desired/path/to/env/bin/pip
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubunt
Hi everyone,
I came across this issue this morning when trying to enable a virtualenv
with Python 3.4.
First of all, thanks to everyone who worked on that to make a fix
available in Debian!
Same question as Adrien Beau: Any update on when a fix will be
available? In the meantime, what is the bes
74 matches
Mail list logo