|
From: SourceForge.net <no...@so...> - 2005-03-31 00:21:31
|
Bugs item #1064265, was opened at 2004-11-11 13:30 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1064265&group_id=78018 Category: win32 Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tony Meyer (anadelonbrin) Assigned to: Nobody/Anonymous (nobody) Summary: Having system32 in sys.path causes problems for services Initial Comment: If system32 is on sys.path and a script is run as a Windows service, then it may die when it finds a zlib.dll in system32 before it tries to find one in PythonXX\DLLs. In Mark's own words: "I think that for a service (or for any Python program for that matter), we don't want system32 on sys.path" ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2005-03-31 10:21 Message: Logged In: YES user_id=14198 Checking in PythonService.cpp; new revision: 1.17; previous revision: 1.16 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1064265&group_id=78018 |
