On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said:
The ``constraints`` module in zope.app.container seem to be usable
outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not
have to pull in ZODB just to
On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable
outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not
have to pull in ZODB just to get these frameworky
Hi Christian
Betreff: [Zope-dev] Re: Splitting up zope.app.container
On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said:
The ``constraints`` module in zope.app.container seem to be usable
outside a ZODB-application---ditto most of the interfaces.
If we want to
Hi.
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
Scope:
For those unfamiliar with the branch, it makes Acquisition aware of
__parent__ pointers. This makes it unnecessary to use Acquisition
mixin's for Zope 3 code to use them in Zope 2 code. The
Philipp von Weitershausen wrote:
Wichert Akkerman wrote:
Previously Philipp von Weitershausen wrote:
In my opinion, the fact that it accidentally worked as an instance
variable isn't a very strong argument for continuing to support it. To
me, this is a prime example of misusing a Five
On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote:
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back problems.
Merging
Christian Theune wrote:
On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote:
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back
Previously Martijn Pieters wrote:
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back problems.
Merging it into Zope trunk will get it
Summary of messages to the zope-tests list.
Period Wed Apr 16 11:00:00 2008 UTC to Thu Apr 17 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: Wed Apr 16 21:00:32 EDT 2008
URL:
On Apr 17, 2008, at 12:27 , Hanno Schlichting wrote:
Opinions, votes?
+1
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back problems.
Merging it into Zope trunk will get it into the Zope 2.12 release which is
at
--On 17. April 2008 12:27:42 +0200 Hanno Schlichting [EMAIL PROTECTED]
wrote:
Hi.
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
Go ahead.
Andreas
pgphIV5gzoW65.pgp
Description: PGP signature
___
Zope-Dev
Hanno Schlichting wrote:
Timeline:
I would like to do the merge as soon as possible, so people can easily
test it against all their applications and report back problems.
Merging it into Zope trunk will get it into the Zope 2.12 release which
is at this point not scheduled yet, but is
Hanno Schlichting wrote:
Martijn Faassen wrote:
Alexander Limi wrote:
On Mon, 14 Apr 2008 10:11:11 -0700, Philipp von Weitershausen
[EMAIL PROTECTED] wrote:
*IF* you'd like to be pragmatic, I'd suggest we clean up those
failing Plone tests, merge the branch and be on our way.
This gets
Bernd Dorn wrote:
On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable
outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not
have to pull in ZODB just to get
Hey,
Hanno, this is a major step forward! +1 from me as well.
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 -
On 17.04.2008, at 12:27, Hanno Schlichting wrote:
Opinions, votes?
+1
--
Stefan H. Holek
[EMAIL PROTECTED]
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
Previously Philipp von Weitershausen wrote:
This sounds good. Here's another idea, though: In accordance with
release early and often, how about scheduling the 2.12 release shortly
after the 2.11 one? So the only new thing in 2.12 would be the
philikon-aq branch (it would still ship with
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This sounds good. Here's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Hi.
I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.
Scope:
For those unfamiliar with the branch, it makes Acquisition aware of
__parent__ pointers. This makes it unnecessary to
Hanno Schlichting wrote:
Philipp von Weitershausen wrote:
Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release
which is at this point not scheduled yet, but is unlikely to get a
release before early 2009. This should give us plenty of time to test.
This
21 matches
Mail list logo
