|
From: SourceForge.net <no...@so...> - 2004-10-16 11:28:27
|
Feature Requests item #1048282, was opened at 2004-10-16 13:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=1048282&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert Kiendl (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: win32comext makes many problems (py2exe, zip-packages, etc) Initial Comment: Each time I install a new release of pywin, I first copy the win32comext folder contents to win32com. Otherwise I have a lot of trouble with that module-fake code in win32com/__init__.py Is there a true reason for win32comext? If anybody makes an own extenstion (as I used some) they don't need to live in win32comext.? If modules come with pywin they can anyway stay in win32com and load clean, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=1048282&group_id=78018 |
