[pywin32-bugs] [ pywin32-Bugs-1053745 ] PythonPath no longer set by installer.
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
From: SourceForge.net <no...@so...> - 2004-10-25 14:03:16
|
Bugs item #1053745, was opened at 2004-10-25 16:03 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018 Category: installation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Oliver Giesen (ogiesen) Assigned to: Nobody/Anonymous (nobody) Summary: PythonPath no longer set by installer. Initial Comment: I have meant to report this ever since the first 20x release but somehow never got around to it: Before the 20x releases the installer used to add the extensions to the PythonPath as sub-entries win32 and win32com respectively. This no longer is the case and as a result my WinCvs macros that make use of the extensions no longer work unless I add the extensions to the PythonPath manually. Is there something I have missed? Is there some other way to make the extensions "publicly importable" nowadays? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018 |