From: Mark H. <ski...@gm...> - 2009-08-05 08:02:41
|
On 5/08/2009 1:29 PM, Zwicky, William R ERDC-CERL-IL Contractor wrote: > Sorry, I don't mean to spam the group. I'm trying to work through these > problems myself, and hoping someone might have pointers. > > Numpy 1.3.0 is the latest release, and is giving me a ton of trouble. In > particular, they're playing games with the imports, much like I did with > an earlier version of our software. While I was able to mend my ways and > my software to make py2exe happy, I'm not about to mend Numpy. Here's > the beginning of the error I get: > > The following modules appear to be missing > ['_umfpack', 'core.abs', 'core.max', …] > > _umfpack is a test probe (the import is in a try/except that handles > when _umfpack is missing). > > The core.* errors are relative imports. There are "import core" lines in > modules under numpy, and Python searches up the directories for that module. > > There are a ton more of these, but they're all test probes or relative > imports. > > What's the best way to handle this? I can add all these to the excludes > list, but I worry py2exe will be leaving out important pieces. I'd recommend listing those missing modules in either 'includes' or 'packages' - whatever works. You may need to use the 'fully qualified' name (eg, the correct module name may be numpy.core.abs, which is why py2exe isn't auto-including it.) As to why this is happening in the first place is a mystery to me too (I regularly need to list packages or modules I technically shouldn't need to) Cheers, Mark |