Hi.
On 25.11.2013. 14:42, Jurko Gospodnetić wrote:
So far all tests seem to indicate that things work out fine if we
install to some dummy target folder, copy the target folder to some
version specific location & uninstall. That leaves us with a working
Python folder sans the start menu and registry items, both of which we
do not need for this. Everything I've played around with so far seems to
use the correct Python data depending on the interpreter executable
invoked, whether or not there is a regular Windows installation
somewhere on the same machine.
We can use the script suggested by Ned Batchelder to temporarily
change the 'current installation' if needed for some external installer
package to correctly recognize where to install its content.
I'm still playing around with this, and will let you know how it goes.
Just wanted to let you know that the usage I described above seems to
work in all the cases I tried out.
I added some batch scripts for running a specific Python interpreter
as a convenience and everything works 'naturally' in our development
environment.
Packages can be easily installed to a specific targeted environment
using for example:
py243 -m easy_install pip
py332 -m pip install pytest
[not mentioning tweaks needed for specific ancient Python versions]
Thank you all for all the suggestions.
Best regards,
Jurko Gospodnetić
--
https://mail.python.org/mailman/listinfo/python-list
