[pywin32-bugs] [ pywin32-Bugs-1053745 ] PythonPath no longer set by installer.

[SourceForge.net <no...@so...>]

Bugs item #1053745, was opened at 2004-10-26 00:03
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018

Category: installation
Group: None
>Status: Pending
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?

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2004-10-26 09:04

Message:
Logged In: YES 
user_id=14198

There should be a pywin32.pth file installed into your
site-packages directory.  Python loads this as it starts up
- unless you have told Python not to process site.py

You should be able to confirm this by running python.exe and
printing sys.path

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018