[python-win32] Multiple versions of Python on same machine with regsvr32.exe PYDs

[reckoner]

Mark:

Thanks for your reply. I'm using the Python extension described here:

    http://www.synapseadaptive.com/joel/index_old.html

Basically, the natlink.pyd file is called ( after being registered with 
  regsvr32 ) indirectly by the speech recognition engine. Thus, if the 
natlink.pyd file is built using, say, Python version 2.6, and I have 
another version of Python installed, say, Python version 2.7, then when 
the functions inside of natlink.pyd are called, they need to somehow be 
able to figure out the correct Python path and other linked libraries. 
So, I'm not sure how this works in terms of the registry and how Python 
figures out which Python version it should use and where the 
corresponding libraries are.

Any ideas here? I would like to have multiple Python installations on 
the same machine so I can migrate between two versions, but I admit all 
of this registry stuff is confusing to me and I don't imagine it will be 
so simple as simply changing the Python path.

Thanks in advance and for all your great work bringing Python to us 
Windows users.




On 7/14/2011 9:24 PM, Mark Hammond wrote:
> On 14/07/2011 4:39 AM, reckoner wrote:
>> Hi,
>>
>> I have been researching this for a couple of days now, and although
>> virtualenv seems like the answer, I have been reading about problems
>> with applications that require specific versions of Python in the
>> registry so it can find corresponding PYD and DLL files. This means that
>> it is more complicated than just setting the path differently for each
>> Python installation.
>
> I'm not with you there. What problems specifically?
>
>> In other words, if you need
>>
>> c:> regsrv32.exe Some_python.pyd
>
> regsvr32.exe doesn't work with .pyd files - what were you hoping to
> achieve?
>
>> then they're going to be problems if you try to change your default
>> Python installation by just manipulating the Path.
>>
>> Basically, my problem is I need to slowly migrate my entire software
>> stack from Python version 2.6 to Python version 2.7.
>
> What specific problems are you seeing?
>
> Mark