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?

Craig


On Feb 24, 2010, at 10:02 AM, Anthony Tuininga wrote:

> On Wed, Feb 24, 2010 at 9:34 AM, Craig Swank <[email protected]>  
> wrote:
>> The new namespace_packages option seems to work for the zope  
>> packages in my
>
> The zope package is already built in to the hooks so you don't have to
> include them yourself manually.
>
>> project, but is having trouble with repoze.lru for some reason.  My  
>> setup.py
>> looks like this:
>> from cx_Freeze import setup, Executable
>> version = '1.0'
>> includes=['lxml', 'lxml._elementpath', 'lxml.etree', 'gzip',  
>> 'gfmodel',
>> 'gfserver', 'chameleon', 'paste', 'webob',  'paste']
>> namespaces = ['zope.interface', 'zope.component', 'repoze.bfg']
>> setup(name='gearfacts',
>>       version=version,
>>       options = {
>>         "build_exe" : {
>>             "namespace_packages": namespaces,
>>             "includes": includes,
>>             },
>>         },
>>       executables=[Executable('run.py')],
>>       )
>
> Right. This is due to the fact that you need to specify the top-level
> package as the namespace package. The others fill in that namespace.
> So you should say instead:
>
> namespaces = ["zope", "repoze"]
>
> I suppose I could say that if you said "repoze.bfg" that I would do
> that one as well as the top-level package associated with it. If that
> makes sense to you, let me know and I'll make the appropriate changes;
> otherwise, simply modify the namespaces variable as specified and all
> should work well for you. Let me know!
>
> Anthony
>
> ------------------------------------------------------------------------------
> Download Intel&#174; 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


------------------------------------------------------------------------------
Download Intel&#174; 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

Reply via email to