On 8 May 2013 01:03, "Roy Smith" <r...@panix.com> wrote: > > In article <72f93710-9812-441e-8d3d-f221d5698...@googlegroups.com>, > sokovic.anamar...@gmail.com wrote: > > > Hi, > > > > what is the generally recommended structure when we have into play this type > > of problem: > > multiple versions of python (both in the sense of main versions and sub > > versions, e.g., > > 2.7 : > > 2.7.1 > > 2.7.3 > > 3: > > 3.3 > > 3.3.1 > > Different versions of gcc > > different compilation strategies (-vanilla and non-vanilla) > > different modules (numpy,scipy) together with the different versions of all > > the rest. > > > > any help is appreciated > > > > Ana > > Virtualenv is your friend. > -- > http://mail.python.org/mailman/listinfo/python-list
Have you looked at tox? It manages a folder full of virtualenvs for you, including your dependencies, and allows you to run your tests against every version.
-- http://mail.python.org/mailman/listinfo/python-list
