Thanks to Mark, Tim, and Thomas for the valuable hints. Unfortunately, Leo seems to require something else. I guess I'm gonna download a regular installation now :(. "Mark Hammond" <mhammond@skippinet.com.au> writes: > I generally setup the registry, by adding an "InstallPath" key. Most > extensions then work correctly, including distutils. Now that we have the > "_winreg" module, we should include a simple script you can run to setup > everything you need. > > FYI, all you should need is: > > HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.3\InstallPath: > pydir > > HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.3\PythonPath: > pydir\lib;pydir\pcbuild > > where: > * "pydir" is the path to main Python directory - ie, parent of "PCBuild", > "Modules" etc > * The "2.3" is actually available in sys.winver > * The "PythonPath" entry is generally not needed, except in embedding > situations where the Python DLL isn't in the main Python build directory. > "Tim Peters" <tim.one@comcast.net> writes: > Another possibility is to use the native Windows facilities for fiddling the > registry. For example, edit the attached .reg file to taste, then > right-click on it in Explorer and select Merge from the context menu. Or > you can just double-click its icon. > Thomas Heller <theller@python.net> writes: > Does this help? > > http://effbot.org/zone/python-register.htm > > Thomas > -- Dave Abrahams Boost Consulting www.boost-consulting.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4