added support for selecting per-project Python interpreter used to create the virtual environment. #311
Conversation
… project virtual environment.
…er used to create the project virtual environment. The import project form is modified and the PYTHON_CHOICES constant corrected.
|
This looks like a great start. I think we'll call it python2 and python3, where python->python2. This is more explicit. I'll go ahead and give this a test locally and see if it works. I'm curious if Sphinx and everything else will install properly. |
|
Hitting this bug when trying to test this functionality: pypa/pip#650 It seems pip can't install distribute on py3k :/ This is likely to hold up using it on RTD as it breaks the virtualenv option. Looking at possible ways to work around it. |
|
Looks like we get basic support if we don't enable the upgrade flag with pip and distribute. |
|
I have a question. Where this feature will be available on readthedocs? best regards |
|
sorry to ask before test. i see that there is available righ now. again, sorry |
|
I testit and don't work. the reason is that you have to install virtualenv in all the interpreters for this to work because the virtualenv command is run with the -m schitch on the interpreter. |
This is a solution for Issue 132. Maybe you recall I comment on the issue thread that i will try to solve the issue, well this is my solution. The only problem is that my machine OS is Debian and the environment is not created once a new project is added, may be you can test that part. Is very simple. The project model is updated to store the name of the interpreter used to create the virutal environment. The interpreter name is one of the choices set on constants for that application. The project import form has been modified too to make the Python interpreter selectable and the import project task has been modified to spell explicitly the name of the interpreter on the environment creation command. Additionally a migration has been added to make easy the database schema update.