This is about version 4.3.1.
Line 55 and 56:
if not bootstrap:
self._ClearBaseModuleCode(initialExcludedModules)
bootstrap is always false, and these two lines therefore always cause most
"builtin" packages like "os" to not be included in the library.zip file.
(it sets the "file" and "code" attributes of all modules thus far included
to None!) This of course made my package not work since these are vital.
Commenting out these two lines fixes this but there were further modules
that were missing (like "re"). I discovered more weirdness:
Line 63 to 68:
self.ExcludeModule("cStringIO")
self.ExcludeModule("doctest")
self.ExcludeModule("getopt")
self.ExcludeModule("logging")
self.ExcludeModule("re")
self.ExcludeModule("subprocess")
What's this about? By commenting out these lines I was finally able to
build packages that worked. I was using build_exe, and copying the result
to a fresh pythonless XP VM to test that everything needed was bundled.
(The build result worked on the build machine, as it apparently used the
installed python modules)
Does anybody know why these things are like they are in this newest release?
- Robin
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
cx-freeze-users mailing list
cx-freeze-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
