[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Fri Jun 20 11:00:00 2008 UTC to Sat Jun 21 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Jun 20 21:00:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009735.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:02:00 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009736.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:03:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009737.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:05:01 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009738.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 20 21:06:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009739.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildout on Windows
Philipp von Weitershausen wrote: This isn't a matter of a binary zope.proxy egg. If you look at the 'zope2' part of your buildout.cfg, you'll see it's actually trying to compile Zope 2 itself (which happens to contain the zope.proxy package as part of the Zope 3 libraries that it ships with). Right, this doesn't seem sane. Is this the fault of the recipe or of buildout? What you want to do on Windows is install Zope 2 manually using the installers, then edit buildout.cfg to NOT build Zope 2, but to refer to the installation location, e.g.: Well, I really don't ;-) I want buildout to get binary eggs on windows or (and I know I'm asking a lot here) to get a binary Zope 2 if it needs one. I'm still hazy on what the problem is... Will buildout use binary eggs if they're available? (given that it's Windows where this is particularly important...) cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildout on Windows
Hey Sidnei, Sidnei da Silva wrote: Depending on how 'plone-ish' your buildout is, you can start from the newly-created, experimental buildout-based Plone Installer for Windows: https://launchpad.net/plone/3.1/3.1.2/ So how does this work? Where's the buildout.cfg that gets used and what recipes have you created/tweaked to make this happen? Also, related, would you be up for building binary windows eggs for the zope 3 components for both python 2.4 and python 2.5? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: buildout on Windows
Martin Aspeli wrote: - if you really are installing zope2, then I wonder why it's trying to download zope.proxy. This is possibly a case of egg dependencies gone wrong, and you may want to look at plone.recipe.zope2install and its fake eggs optoin Hmmm :-S Can you explain this more? - you probably want to do what the error message says and install mingw32. look at http://plone.org/documentation/tutorial/buildout for some instructions on how to prepare for building zope in wintendo. No, I really don't. I don't what to do any C compilation on the windows boxes. I'm much more interested in fixing problems so other people on windows don't have to worry about VC++ or mingw32... cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: created z3c.saconfig
On Fri, Jun 20, 2008 at 02:01:52PM +0200, Martijn Faassen wrote: Hi there, Brian Sutherland wrote: [snip] Also for this problem: # XXX what happens if EngineFactory were to be evicted from the ZODB # cache? def getCached(self): return getattr(self, '_v_engine', None) I think you could use the same mechanism found in zope.app.cache.ram. I.e. store the engines in a module level global dictionary. Then use some clever way (with a counter and time) to figure out a unique key for your local utility (and persistently store the key). Ah, thanks for that tip. Does zope.app.cache.ram deal with threading issues? Ah, yes, I see it uses a lock. Anyway, a patch would be welcome. :) Committed, please feel free to revert or modify as you feel:) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- Brian Sutherland ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
