On Wed, Feb 24, 2010 at 10:31 AM, Craig Swank <[email protected]> wrote:
> Ok, now the repoze and zope packages appear to all be going into the
> build. When I add my custom namespace packages they don't go in. Can
> you try it out with the two 'rubbish' packages I made? I tried these
> and they also didn't work. My library directory of the build has a
> 'rubbish' folder, but it only has an __init__.py file. If you can get
> them to work, could you please show me your setup.py?
Sure. They do indeed work.
This is my setup.py
from cx_Freeze import setup, Executable
buildOptions = dict(
namespace_packages = ["rubbish"])
setup(
name = "test_freeze",
version = "0.1",
description = "Sample cx_Freeze script",
options = dict(build_exe = buildOptions),
executables = [Executable("test_freeze.py")])
And this is my test_freeze.py
import rubbish.example
import rubbish.anotherexample
print "Rubbish.example", rubbish.example
print "Rubbish.anotherexample", rubbish.anotherexample
Note the use of the top-level package which has been broken up. I
assume you had specified "rubbish.example" and
"rubbish.anotherexample" in your namespace package list, right? I
suspect that will be a common "error" so what I have just checked in
is code to ensure that if a subsidiary package is marked as a
namespace package so are all of its parents, which must by definition
be true. Let me know how that goes, now. Thanks!
Anthony
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
cx-freeze-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
