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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To
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
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
Bugs, which is subscribed to Ubuntu.
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
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,
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.
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
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
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
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
Bugs, which is subscribed
This is it: https://bugs.python.org/issue24875
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about this bug go
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
@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
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 the
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To
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.
--
I call it directly also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about this bug go to:
FTR,
python3 -m venv env
Doesn't work either for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about
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
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 bug
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
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
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
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 'pyvenv'
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
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
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 separated
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
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 if
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
Bugs, which is
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising
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
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
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
Bugs, which is
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 should work
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage
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
Bugs, which is subscribed
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails
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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
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).
#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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
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
Bugs, which is subscribed to Ubuntu.
Any progress on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about this bug go to:
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
Bugs, which is subscribed to
debdiff sent to Doko
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about this bug go to:
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
infinity 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
Bugs, which is subscribed to Ubuntu.
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip
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
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
Why this is marked as Fix Released? This is still broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about
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
Bugs,
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip
Ah sorry, the previous comment is incorrect. My mistake, please ignore
it. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
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
Bugs, which is subscribed to Ubuntu.
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
On 2014-06-10, Barry Warsaw wrote:
It's a bit of a long, complicated process, but rest assured we are on it.
It's been three weeks since the status of this bug was changed to Fix
Released, but it is apparently still not available in Ubuntu 14.04. In
what time frame can we expect to see it land
** Changed in: python3.4 (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: python3-defaults (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does anyone know when the fix will be available in the ubuntu repos?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage
On Jun 10, 2014, at 01:18 PM, jose wrote:
Does anyone know when the fix will be available in the ubuntu repos?
It's a bit of a long, complicated process, but rest assured we are on
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks I appreciate the update and the the effort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about this bug
Apologies for the noise but also: Thanks for working on a thoughtfully-
derived correct fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
** Changed in: python3.4 (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications
Thank you for releasing fix. I for one am genuinely grateful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To manage notifications about
Am 04.06.2014 15:51, schrieb btreecat:
Matthias Klose, coming from a distro who does a lot less mucking about
with upstream packages, having deafult language behavior broken infavor
of idealistic guidlines is just plain bad for UX.
there is nothing broken in default language behaviour. There
On Jun 05, 2014, at 04:10 PM, Matthias Klose wrote:
shipping virtualenv in such a way is a mistake, which only was discovered
after the release.
I'm working on an update to virtualenv which will use the same technique as
pyvenv, so now that we know the problem, we'll be able to solve it there
I just had a brush with this issue. Thank you kind folks for working on
fixing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290847
Title:
pyvenv fails due to mising ensurepip module
To
Matthias Klose, coming from a distro who does a lot less mucking about
with upstream packages, having deafult language behavior broken infavor
of idealistic guidlines is just plain bad for UX.
Spin it how you want to but shiping broken packages means some one just
means someone spent the time
Can we get a status update? This is still broken and it's sad that such
a critical and good-for-the-comunity feature is needlessly broken by
default.
Forturnately this doesn't completely break docker as I can just do
everything system wide and isolate the image. However it would be lovely
to use
On Jun 03, 2014, at 08:33 PM, Stephen Tanner wrote:
Can we get a status update?
Matthias and I are actively working on this stack in Debian. I've had to wait
until several packages clear Debian NEW, including one NMU. I've also had to
update several other packages, and provide an update to the
Stephen Tanner: There is a second way to easily deploy a virtual
environment: You can also use `virtualenv`. In Ubuntu I belive the
package is named python-virtualenv (might need a 3!). Installing that
with apt-get will give you (as far as I can tell) the same tools for
python 3.4 as venv-3.4.
--
virtualenv relies on some dirty hacks (right now at least, in the future
it'll reuse venv where available) so using venv is preferable. However
the python-virtualenv package was allowed to (at least for now, I
believe barry is planning to update it to the venv solution once it's
done) violate the
Am 03.06.2014 22:33, schrieb Stephen Tanner:
Can we get a status update? This is still broken and it's sad that such
a critical and good-for-the-comunity feature is needlessly broken by
^^
default.
If you don't understand Ubuntu's
What makes the situation with these wheels so much more drastic than
what happens with python-virtualenv already?
https://packages.debian.org/sid/all/python-virtualenv/filelist
I don't understand why there needs to be an entire effort de-bundling
and de-(re-?)-vendoring files and why this hasn't
On May 22, 2014, at 09:32 PM, Ivo wrote:
I don't understand why there needs to be an entire effort de-bundling
and de-(re-?)-vendoring files and why this hasn't been applied to
virtualenv as well?
python-virtualenv violates policy too. It just wasn't noticed before.
Ideally the same set of
As a stop-gap solution for n00bs like me, download the lib/ensurepip
directory from the Python 3.4 source code, and place it in
/usr/lib/python3.4 with the proper permissions.
Hoping this gets resolved soon...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Apr 24, 2014, at 07:38 PM, Matthias Klose wrote:
So why not build the wheel files from the Debian python-pip source
package, build-depending on python-six, python-requests, etc, then
revert the de-vendorize patch. The binary package should have Built-
Using information about these build
1) Treat the .whl files in ensurepip as data files, or alternatively bundled
copies
of code that are intended to be bundled (as per the Debian manual in
4.13),
and continue to do your normal modifications to python-pip.
chapter 4 talks about source packages, not binary packages.
Let's look at use cases.
1) User wants to pip install something into their ~/.local directory.
Having python3-* packages installed does not give them pip3. They have
to apt-get install python3-pip. If they try to `pip3 install foo` it
will try to install it into the system dist-packages and
Your use cases are correct. Ideally in the future 1) won't require
--user but that's a different discussion :)
The wheels in ensurepip are taken from PyPI and are built with ``python
setup.py bdist_wheel --no-script`` (I may have the command parameter
wrong for excluding scripts, and the latest
If I'm reading the rewheel code correctly, I think we are going to have
to do something like the following:
* Package up wheel for Debian (python-wheel, and python3-wheel). This
gives us the setuptools bdist_wheel command.
* At Python build-time we need *.dist-info/RECORD files for setuptools,
So I think that the debundling of requests, html5lib, etc that python-
pip does and rewheel are mutually incompatible and are going to lead to
a lot of end user pain.
Specifically the reason we bundle those things in pip is because if pip
depends on requests, and someone does ``pip install
1 - 100 of 111 matches
Mail list logo
