[Zope-Checkins] SVN: Zope/branches/2.11/doc/CHANGES.txt Cleanup changes a bit

2009-04-26 Thread Hanno Schlichting
Log message for revision 99505: Cleanup changes a bit Changed: U Zope/branches/2.11/doc/CHANGES.txt -=- Modified: Zope/branches/2.11/doc/CHANGES.txt === --- Zope/branches/2.11/doc/CHANGES.txt 2009-04-26 09:02:56 UTC (rev

[Zope-Checkins] SVN: Zope/branches/2.11/ Updated to include all new versions from the final Zope 3.4.0 release

2009-04-26 Thread Hanno Schlichting
Log message for revision 99507: Updated to include all new versions from the final Zope 3.4.0 release Changed: U Zope/branches/2.11/doc/CHANGES.txt _U Zope/branches/2.11/lib/python/zope/ _U Zope/branches/2.11/lib/python/zope/app/ -=- Modified: Zope/branches/2.11/doc/CHANGES.txt

[Zope-Checkins] SVN: Zope/trunk/ Caught up with the latest and greatest from the Zope Toolkit again

2009-04-26 Thread Hanno Schlichting
Log message for revision 99525: Caught up with the latest and greatest from the Zope Toolkit again Changed: U Zope/trunk/alltests.cfg A Zope/trunk/dependencies.cfg U Zope/trunk/src/Products/Five/browser/configure.zcml U

[Zope-Checkins] SVN: Zope/trunk/ Removed the dependency on `zope.app.testing` in favor of providing a more minimal placeless setup as part of ZopeTestCase for our own tests.

2009-04-26 Thread Hanno Schlichting
Log message for revision 99527: Removed the dependency on `zope.app.testing` in favor of providing a more minimal placeless setup as part of ZopeTestCase for our own tests. Changed: U Zope/trunk/alltests.cfg U Zope/trunk/doc/CHANGES.rst U Zope/trunk/setup.py U

[Zope-Checkins] SVN: Zope/trunk/setup.py We do depend on the zope-functional-testing extra of zope.testbrowser it seems

2009-04-26 Thread Hanno Schlichting
Log message for revision 99528: We do depend on the zope-functional-testing extra of zope.testbrowser it seems Changed: U Zope/trunk/setup.py -=- Modified: Zope/trunk/setup.py === --- Zope/trunk/setup.py 2009-04-26 16:33:20

[Zope-Checkins] SVN: Zope/trunk/ No longer depend on `zope.app.locales`. Zope2 uses almost none of the translations provided in the package and is not required for most projects. The decision to inclu

2009-04-26 Thread Hanno Schlichting
Log message for revision 99529: No longer depend on `zope.app.locales`. Zope2 uses almost none of the translations provided in the package and is not required for most projects. The decision to include locales is left to the application developer now. Changed: U

[Zope-dev] Zope Tests: 8 OK

2009-04-26 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Sat Apr 25 12:00:00 2009 UTC to Sun Apr 26 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Apr 25 20:42:50 EDT 2009 URL:

Re: [Zope-dev] gocept.bsquare

2009-04-26 Thread Christian Theune
On Sat, 2009-04-25 at 19:54 +0200, Adam GROSZER wrote: Hallo Christian, Any objection against merging svn://svn.zope.org/repos/main/gocept.bsquare/branches/pcardune-setup to the trunk? Feel free to go ahead. I haven't used that in a while and if you do I'm happy to have Pauls or your

[Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS

2009-04-26 Thread Martin Aspeli
Hi, First - a quick question: can we treat __name__ and id/getId()/_setId() as the same, always? OFS.SimpleItem has some support for letting id and name be the same, but the link is lost once both __name__ and id are set. Why isn't __name__ just a property that reflects self.id ? Then, the

Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS

2009-04-26 Thread Matthew Wilkes
On 26 Apr 2009, at 16:53, Martin Aspeli wrote: We can fix this by introducing some code in OFS (and BTreeFolder2) that mimics what zope.container does. Is there any risk involved in this? It looks ok in theory, just that we're at a4 of Zope 2.12, we should be getting wary of features.

Re: [Zope-dev] Proposal: set __parent__ and __name__ in Zope 2.12 OFS

2009-04-26 Thread Andreas Jung
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 26.04.2009 um 18:16 schrieb Matthew Wilkes: On 26 Apr 2009, at 16:53, Martin Aspeli wrote: We can fix this by introducing some code in OFS (and BTreeFolder2) that mimics what zope.container does. Is there any risk involved in this? It

Re: [Zope-dev] zc.buildout template recipes: concerns with [z3c|collective].recipe.template and other issues

2009-04-26 Thread Uli Fouquet
Hi there, Gary Poster wrote: I'm concerned about the state of the zc.buildout template recipes. I want one. I want some one-off files, specific to a certain project, for which writing a standalone recipe feels very heavy. Here are the template recipes I found:

Re: [Zope] Building a fast, scalable yet small Zope application

2009-04-26 Thread Lennart Regebro
On Sat, Apr 25, 2009 at 13:24, Morten W. Petersen mor...@nidelven-it.no wrote: So far, I've been contemplating disabling undo (if that's possible), I doubt that it would make a difference. The Undo functionality comes out of the database being logging, and changing that would mean pretty much a

Re: [Zope] Fwd: Building a fast, scalable yet small Zope application

2009-04-26 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Gerken wrote: Argl, why does this mailing list not use the reply-to: field? That would be a religious question, and one which is not helpful to debate here.. E.g., see: http://www.unicom.com/pw/reply-to-harmful.html The Zope mailing

Re: [Zope] Fwd: Building a fast, scalable yet small Zope application

2009-04-26 Thread Garito
jajajajajajajajajajajajaja Amazing! I don't know how the other list doesn't collapse using reply-to field jajajajajajajajajajajajaja What wonders me more is how belligerent some in this list are with this question You cause the problem, at least try to don't threaten us with ban us if we send

Re: [Zope] Fwd: Building a fast, scalable yet small Zope application

2009-04-26 Thread Patrick Gerken
On Sun, Apr 26, 2009 at 19:45, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patrick Gerken wrote: Argl, why does this mailing list not use the reply-to: field? That would be a religious question, and one which is not helpful to debate here..