buildout - using different python version

Question

i have set up buildout project (django to be specific) that has to run in old machine, it works fine in my local system with python 2.7.

In production server it runs python 2.5 and i want to configure buildout that it would download and use 2.6, but only this project not system wide.

So i assume it should use some sort of recipe, but witch and how? I cannot find one. I hope to achieve it only using buildout.cfg file..

Answer 1

Usually every buildout project contains a bootstrap.py script with is initially run using the Python interpreter that you need/want for this project. Running bootstrap.py will locally create/install a buildout and all the stuff you need. The typical usage pattern is:

svn checkout <some_url_of_a_buildout_project>
cd my_project
/path/to/my/python bootstrap.py
bin/buildout

Answer 2

Whichever python you use to do run the initial bootstrap.py is the one that will be used for your entire project. All paths will reference that specific python and the sitepackages for that specific python will be used.

This is one of the best things about buildout

This is a 32 bit python 2.6:

/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 boostrap.py

This is a 64 bit python 2.7:

/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python bootstrap.py

Now go look at the the bin/ it created.

Then do your actual bin/buildout -c dev.cfg and look at the scripts in the bin. For my 32 bit example:

For the first one I see in my django file:

#!/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python
...
'/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages',

The accepted answer says you need to compile a whole python. This is not needed nor advised, though it would mean you have a completely isolated sitepackages. But there are easier ways to tell buildout to not include the sitepackages.

The answer from esaelPsnoroMoN is actually correct, but s/he didn't describe the solution very well. (I ignored it myself before)

Answer 3

Answer of Martijn Pieters doesnt seem to help me. I need different versions of python inside buildout scripts. This is my example

[buildout]
parts = py2script
        py3script
index = https://pypi.python.org/simple

[python36]
executable = /usr/bin/python3.6
[python27]
executable = /usr/bin/python2.7

[py3script]
recipe = zc.recipe.egg:scripts
python = python36
eggs = bobo
interpreter = python3_interpreter

[py2script]
recipe = zc.recipe.egg:scripts
python = python27
eggs = bobo
interpreter = python2_interpreter

Every time inside python(2|3)_interpreter scripts will be written that python version which I used for bootstraping. So my buildout.cfg doesnt seem to work as expected.

Answer 4

Buildout specifically supports this scenario. Each part in a buildout can use it's own python interpreter, or you can set one python interpreter globally for all parts. This defaults to the python used to run buildout.

To set the python interpreter used, set the python option to the name of a part that contains an executable option. This can be a part that builds a whole new python interpreter. Here is an example:

[buildout]
python = python
parts =
    python

[python]
recipe = zc.recipe.cmmi
url = http://www.python.org/ftp/python/2.6.6/Python-2.6.6.tgz
executable = ${buildout:directory}/parts/python/bin/python2.6
extra_options=
    --enable-unicode=ucs4
    --with-threads
    --with-readline

Any other parts in this buildout now will use the python 2.6 executable.

You may want to symlink the python script into the buildout bin/ directory as well; the following part would do that for you:

[pythonbin]
recipe = plone.recipe.command
command = ln -s ${python:executable} ${buildout:bin-directory}/python