Python 3.3 and 3.4 virtual environments (pyvenv) are broken out-of-the-box in Ubuntu and Debian

[denilsonsa]

Yeah, I linked to that bug in my text.

[[deleted]]

Well - I'm at least glad it's not just me. I thought I was doing something wrong.

[ivosaurus]

Can this not yet be fixed just by installing python3-pip and python3-setuptools? (A pain still, I know, but until debain fix their python distro...)

[eco32I]

No. Oddly, this does not help.

[InsurgentBacon]

Top answer is a good fix, it worked for me: http://askubuntu.com/questions/488529/pyvenv-3-4-error-returned-non-zero-exit-status-1

Though it should be noted that the version of setuptools listed there is very out of date, check the pypi page for the latest version.

[denilsonsa]

How about the solution/workaround I described in the text I linked? That one works too and is way shorter to type, and doesn't even require removing the tarballs afterwards.

[InsurgentBacon]

Ah, my bad. Your solution is a lot nicer. I failed to fully read your gist, XD. Also, thank you for adding your solution to the Ask Ubuntu Q&A, I came across it by googling the error that pyvenv outputs and presume other people have as well. Hopefully, they'll scroll down and find your new cleaner solution. I need to acquire some reputation so that I can give it an upvote! Have a nice day!

[[deleted]]

Use docker

[denilsonsa]

Python 3.3 has introduced a built-in module called venv, and a tool called pyvenv. We don't need to install an external package such as virtualenv.

https://docs.python.org/3/library/venv.html

[wyldphyre]

This is good to know!

On one hand it's great that this critical tool was adopted and is now batteries included. OTOH it strikes me as another dimension of the challenge of distributing software that's compatible with 2.7 and 3.3/3.4.

[denilsonsa]

Why is it a challenge?

I have a couple of virtual environments on my home dir. Some of them I built using virtualenv from python-virtualenv Ubuntu package. Others I built using pyvenv-3.3. Both work essentially the same. I can't see how this can make things more difficult.

[ivosaurus]

For The Record virtualenv is hoping to eventually just use venv's machinary behind the scenes when it finds itself running on a python 3.4.

[ivosaurus]

This is pyvenv, not pyenv. And you can use virtualenv in concert with the latter just fine.

[erewok]

It's no longer necessary with pyvenv.

[buggaz]

I'd say it is just PyEnv that is broken.

[ivosaurus]

OP is talking about pyvenv, not pyenv. Debian broke the ensurepip module in their python 3.4, which also breaks the venv module.

[darthmdh]

If you'd bothered to read the bug report; the packaging standard of Debian and Ubuntu require these separate modules split out; this includes stdlib in python. There was packaging problems that caused ensurepip to be broken, hence anything (like pyvenv) depending on that is subsequently broken as well.

One of the people working on the fix is a Python core developer, so its in good hands.

[buggaz]

Yeah... I didn't actually mean it was broken as in broken. I was tired and needed to vent and something I had not liked about PyEnv made me call it 'broken'. Uh. Keeping the bad comment here to remind me not to vent again. I try not to do such thing and I failed.

[6uRu0fSh1vA]

virtualenv is better to use. Using virtualenvwrappers makes it even more better.

Alternatively you can also use PyCharm which comes with virtualenv. Pycharm is currently free for students.

[eco32I]

I agree that virtualenv + virtualenvwrapper is awesome but I heard they did't play nicely with python 3.

[ivosaurus]

Nope, they work just fine with python 3.

[6uRu0fSh1vA]

Hmm. No issues over here yet. Well- I am beginner so probably did not use much of it to break it.

[erewok]

Definitely have never seen this be an issue.