Windows Stackless Python 2.5.2 does not copy across to virtualenv folder

[Python Nutter]

Windows XP
Python.org Python 2.5.2
Stackless Python 2.5.2 installed on top of Python.org Python 2.5.2
virtualenv 1.3
setuptools 0.69c

command used:
virtualenv TEST
TEST\Scripts\activate.bat

result:
during creation the python.exe is copied into TEST\Scripts directory
during activation the %PATH% variable has TEST\Scripts at the beginning so it executes first in the search

any python execution results in Python 2.5.2 executing and *NOT* Stackless Python 2.5.2 executing.

The fix (not sure if this is all that is required):
VirtualEnv needs to *also* copy the file C:\PYTHON25\python25.dll into the TEST\Scripts directory.

As soon as I did this my python or ipython executions resulted in Stackless Python 2.5.2 loading instead of the standard Python 2.5.2

[Ian Bicking (ianb)]

Is there a way to detect that it is a stackless interpreter? I'd rather only copy the dll if it is stackless, as it shouldn't be much of an issue for normal interpreters.

[Python Nutter (pythonnutter)]

Stackless replaces python25.dll I believe as its how it gets inside
the interpreter to convert it to Stackless operation.

Now if there is an easy way to detect this beyond known file
signatures I'm not sure. I have not gone deep into the file(s) that
Stackless writes over standard Python.

I can look into it some more but right now Im a bit shattered so I'll
have to go to bed and get some sleep. (minds not wantng to do anything
analytic thinking wise.)

2008/12/18 Ian Bicking <email address hidden>:
> Is there a way to detect that it is a stackless interpreter? I'd rather
> only copy the dll if it is stackless, as it shouldn't be much of an
> issue for normal interpreters.
>
> --
> Windows Stackless Python 2.5.2 does not copy across to virtualenv folder
> https://bugs.launchpad.net/bugs/290565
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Virtualenv: library isolated for Python: New
>
> Bug description:
> Windows XP
> Python.org Python 2.5.2
> Stackless Python 2.5.2 installed on top of Python.org Python 2.5.2
> virtualenv 1.3
> setuptools 0.69c
>
>
> command used:
> virtualenv TEST
> TEST\Scripts\activate.bat
>
> result:
> during creation the python.exe is copied into TEST\Scripts directory
> during activation the %PATH% variable has TEST\Scripts at the beginning so it executes first in the search
>
> any python execution results in Python 2.5.2 executing and *NOT* Stackless Python 2.5.2 executing.
>
> The fix (not sure if this is all that is required):
> VirtualEnv needs to *also* copy the file C:\PYTHON25\python25.dll into the TEST\Scripts directory.
>
> As soon as I did this my python or ipython executions resulted in Stackless Python 2.5.2 loading instead of the standard Python 2.5.2
>

[Carl Meyer (carljm)]

Not migrating to new tracker at https://github.com/pypa/virtualenv/issues due to lack of followup from initial reporter.