Hi all,
I just noticed a problem (which forced me to a last-minute update of the windows
ipython installer). As far as I can tell, this should be considered a bug.[color=blue]
>From the Python docs, sys.executable is:[/color]
executable
A string giving the name of the executable binary for the Python
interpreter, on systems where this makes sense.
However, during the execution of a post-install script, this string actually
resolves to the name of the binary installer! This name should resolve, I
think to the name of the Python executable for which the installer is running
(a value selectable at the start of the installation, if more than one Python
is detected). Having this value available allows you to properly generate
shortcuts with the proper full path to the python executable.
I resorted to using sys.prefix+r'\p ython.exe', which will most likely work, but
I'd rather see sys.executable give me a more sensible answer.
Should this be filed as a distutils bug? I'd rather not clog the database if it
was the result of a deliberate decision, as strange as it may seem to me.
Cheers,
f
I just noticed a problem (which forced me to a last-minute update of the windows
ipython installer). As far as I can tell, this should be considered a bug.[color=blue]
>From the Python docs, sys.executable is:[/color]
executable
A string giving the name of the executable binary for the Python
interpreter, on systems where this makes sense.
However, during the execution of a post-install script, this string actually
resolves to the name of the binary installer! This name should resolve, I
think to the name of the Python executable for which the installer is running
(a value selectable at the start of the installation, if more than one Python
is detected). Having this value available allows you to properly generate
shortcuts with the proper full path to the python executable.
I resorted to using sys.prefix+r'\p ython.exe', which will most likely work, but
I'd rather see sys.executable give me a more sensible answer.
Should this be filed as a distutils bug? I'd rather not clog the database if it
was the result of a deliberate decision, as strange as it may seem to me.
Cheers,
f