On 12/21/2014 9:31 AM, Nick Coghlan wrote:
On 21 December 2014 at 20:33, Liam Marsh
mailto:liam.marsh.home@gmail.com> wrote: Hello again
a few days later, i wad a new idea: the user who wants the 2.X modules, the 3.2 and 3.4 modules to work will probably install the three versions. so, is it possible to have the <somepath>\Python\python34; <somepath>\Python\python32; and <somepath>\Python\python27 dirs, and the <somepath>\Python\PythonAutoVersion program, useing the comment "#py ver XX" to chose which version will take care of it? (same thing with the IDLE)
You're exploring a space which already has a large array of tools available to address it. In particular, selective application upgrades is one of the features provided by virtual environments. If someone so desires, *.pth files can be used to share modules between different virtual environments (although this isn't a common practice - virtual environments are generally aimed at providing near total isolation of an application's dependency stack from other virtual environments on the system).
I thought he was looking for something like the py launcher, implemented for Windows as PEP 397, and discussed for Linux here: https://mail.python.org/pipermail/python-ideas/2014-April/027633.html -- Eric.