From: Russell E. O. <ro...@ce...> - 2006-03-08 01:17:31
|
In article <A7B5C22F20EE3C4E95744E2F03F1887F456198@MAYOR.retzlaff.com>, "Jimmy Retzlaff" <ji...@re...> wrote: > In case anyone hasn't noticed, I broke a bunch of things in py2exe > 0.6.4....I believe I've rectified these problems in a new version of py2exe.mf. > There have been a number of cases where I've recommended replacing > "import modulefinder" with "import py2exe.mf as modulefinder" since > 0.6.4 was released... this fix should allow you to go back to the former > (although the latter will continue to work as well).... I tried your modified mf.py (thanks much for the direct link) and it worked for me. I imported modulefinder instead of using py2exe.mf (the old way that worked before 0.6.4) and win32com.shell was found just fine. Thanks for the fix! At risk of sounding ungrateful, I'm curious if there is a long-term likelihood that py2exe will be able to find win32com and other such packages by itself (i.e. the packages that currently need playing with modulefinder or py2exe.mf to be found)? -- Russell |