Start supporting pyvenv

[berdario]

Supporting pyvenv (the stdlib venv module) might mean that in a remote future, where Python <3.4 will have disappeared, the virtualenv dependency will be redundant.

Due to this bug, to use venv on Ubuntu/Debian it'd require a preemptive check if ensurepip is available with python -c 'import ensurepip' (python -m ensurepip won't work due to a debian patch)

Still, before implementing it, it's better to wait until some bugs will have been ironed out

[AlJohri]

hi @berdario, any update on potentially using python3 -m venv in pew? thanks!

[FranklinYu]

The Ubuntu bug has been fixed in Ubuntu/Debian, but the Python bug is included only in next minor release (3.7).

[berdario]

Hi everyone, thanks for checking on the other issues and updating here.

Yeah, I think it's a good time to start looking into it. Unfortunately I don't have time for it in the next month, I think (people are welcome to send a PR for it)

I'm also thinking, that this change should coexist with the normal virtualenv-dependency implementation. Probably toggled with an environment variable (not sure yet if it should be opt-out or opt-in... I'd prefer the former, since otherwise not many people might test it).

Only after a few months without complains, I'd then consider removing the virtualenv dependency for Python > 3.4 (or 3.7)

[uranusjr]

I looked into this a bit, and currently the most significant difference might be virtualenv-clone. I haven’t seen anything like this for venv—Does it “just work”, or is there an equivalent? I think I have solutions for all other parts.