From: Robin Dunn [mailto:robin@alldunn.com]
The installer expects to find a key in the registry that
specifies the path where Python is installed.
Sorry to butt in, but why does it do this? This presumably breaks
installation on home-built setups without registry keys? How will it be
affected by Python 2.2's implementation of PEP 250, which makes the default
installation location on Windows os.path.join(sys.prefix, 'Lib',
'site-packages'), rather than just sys.prefix?
[Please don't tell me that wxPython will still install in sys.prefix on
Python 2.2 :-(]
> From: Robin Dunn [mailto:robin@alldunn.com]
> The installer expects to find a key in the registry that
> specifies the path where Python is installed.
Sorry to butt in, but why does it do this?
It's the only way to find sys.prefix for the version of Python that wxPython
was built for, without actually executing Python. If anybody has a better
solution that will work with InnoSetup, please let me know. One thing I
have done is if the reg key isn't found then it will not fail but prompt the
user to enter a path on the PYTHONPATH.
This presumably breaks
installation on home-built setups without registry keys? How will it be
affected by Python 2.2's implementation of PEP 250, which makes the
default
installation location on Windows os.path.join(sys.prefix, 'Lib',
'site-packages'), rather than just sys.prefix?
[Please don't tell me that wxPython will still install in sys.prefix on
Python 2.2 :-(]
Nope.
ยทยทยท
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!