From: Zwicky,
William R ERDC-CERL-IL C. <Wil...@us...> - 2009-08-05 03:29:20
|
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. -Bill |
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 |
From: Zwicky,
William R ERDC-CERL-IL C. <Wil...@us...> - 2009-08-05 22:53:39
|
OK, I think I've gotten most everything under control. One more strange error: *** binary dependencies *** Your executable(s) also depend on these dlls which are not included, you may or may not need to distribute them. Make sure you have the license if you distribute any of them, and make sure you don't distribute files belonging to the operating system. specfun.pyd - C:\Programs\Python25wrz\lib\site-packages\scipy\special\specfun.pyd This message is *false* - specfun.pyd was found and included in the executable automatically. Why would py2exe complain about something it found just fine? Strangely, adding both "specfun" and "scipy.special.specfun" to the excludes list eliminates the warning .. And yet py2exe continues to include the pyd file in the executable. How do I tell py2exe to exclude that file. (I don't really want to, but I don't like how py2exe ignores the excludes list.) -Bill |