News for hackers. Stuff that matters.
Re:Announcing Pipenv by helb on Monday January 23, 2017 @08:35AM (#13462037)
> --three / --two Use Python 3/2 when creating virtualenv.

I use Python 2.7, 3.4, and 3.5 on various projects. Is there a way to choose between 3.4 and 3.5 using Pipenv? I'm using something like this with virtualenv:

  $ virtualenv -p `which python3.5` .venv
Re:Announcing Pipenv by iheredia on Monday January 23, 2017 @09:48AM (#13462490)
Just a comment. Your command is equivalent to

  $ virtualenv -p python3.5 .venv
Re:Announcing Pipenv by emeraldd on Monday January 23, 2017 @11:29AM (#13463334)
Is that true? His command would evaluate the path at the time which is run, but yours seems to evaluate the path at the time python3.5 is run. Subtle, but very different results.
Re:Announcing Pipenv by kyrias on Monday January 23, 2017 @01:05PM (#13464265)
virtualenv resolves the interpreter when you run virtualenv, and if you specify a different interpreter with `-p` it will resolve the path to the interpreter and then run virtualenv again using it.
Re:Announcing Pipenv by jjawssd on Monday January 23, 2017 @11:05AM (#13463097)
No, but you could be using pyenv instead of the system package manager because it is far cleaner