On 09/11/2009 05:58 PM, Martijn Faassen wrote:
Fred Drake wrote:
On Fri, Sep 11, 2009 at 8:53 AM, Martijn Faassen faas...@startifact.com
wrote:
So, could you please follow this policy for ZTK packages in SVN?
I suspect it would help if packages that are part of the ZTK have that
indicated
Hi there,
Christian Theune wrote:
I'm happy with that change, except that it might be worthwhile to
announce policy changes in a separate thread.
Good point. I'll do that in the future; please remind again if it
doesn't happen.
Regards,
Martijn
Summary of messages to the zope-tests list.
Period Thu Sep 17 12:00:00 2009 UTC to Fri Sep 18 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: Thu Sep 17 20:44:25 EDT 2009
URL:
On Friday 18 September 2009, Christian Theune wrote:
I've also taken the liberty to update the ZTK policy to say that this
should be done. (other steering group members can call me back if they
don't like this policy change :)
I'm happy with that change, except that it might be worthwhile
On 09/18/2009 02:04 PM, Stephan Richter wrote:
On Friday 18 September 2009, Christian Theune wrote:
I've also taken the liberty to update the ZTK policy to say that this
should be done. (other steering group members can call me back if they
don't like this policy change :)
I'm happy with
On 09/18/2009 09:21 AM, Martijn Faassen wrote:
Hi there,
Christian Theune wrote:
I'm happy with that change, except that it might be worthwhile to
announce policy changes in a separate thread.
Good point. I'll do that in the future; please remind again if it
doesn't happen.
I'll try
Christian Theune wrote:
On 09/18/2009 02:04 PM, Stephan Richter wrote:
On Friday 18 September 2009, Christian Theune wrote:
I've also taken the liberty to update the ZTK policy to say that this
should be done. (other steering group members can call me back if they
don't like this policy
Hi,
We're trying to make an integration of z3c.hashedresource into Grok.
While working on it we wondered how and where people using
z3c.hashedresource set the caching headers for the resources referenced
by the URLs generated by z3c.hashedresource.
A few random thoughts about this:
*
On Friday 18 September 2009, Jan-Wijbrand Kolman wrote:
While working on it we wondered how and where people using
z3c.hashedresource set the caching headers for the resources referenced
by the URLs generated by z3c.hashedresource.
I think I solved that in z3c.versionedresource.
Regards,
Hi Stephan,
Stephan Richter wrote:
On Friday 18 September 2009, Jan-Wijbrand Kolman wrote:
While working on it we wondered how and where people using
z3c.hashedresource set the caching headers for the resources referenced
by the URLs generated by z3c.hashedresource.
I think I solved that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is from a note I sent yesterday to the ZTK steering group (Martijn,
Christian, Jim, Stephan), proposing criteria for removing packages from
the ZTK. Martijn has already updated the docs to reflect some of the
criteria: I figured I would throw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Two modules do a really complicated and ugly conditional import dance to
try and make twisted availabe as an alternative to ZServer. I propose
we nuke that dance on the Zope trunk: at this point, we should prefer
to do WSGI well, and leave
On Sep 18, 2009, at 11:53 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is from a note I sent yesterday to the ZTK steering group
(Martijn,
Christian, Jim, Stephan), proposing criteria for removing packages
from
the ZTK. Martijn has already updated the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Most of the remaining zope.app dependencies in the Zope2 trunk are
related to Products.five.form. I propose moving all that code out to a
new package, e.g. 'five.forms', which can be included by anybody who
uses that code.
Tres.
- --
On Fri, Sep 18, 2009 at 11:53 AM, Tres Seaver tsea...@palladion.com wrote:
- - Any package which depends on a zope.* package which is *not* part
of the ZTK should itself be removed from the ZTK.
+1
- - As a corollary, any package which depends on any other probationary
package is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yuppie:
I don't know what the purpose of the following checkin was:
http://svn.zope.org/Zope/trunk/?rev=85827view=rev
but the tests all pass if I rip out the import, and Zope starts. I
don't know what code in Zope2 expects the
On 18.09.09 17:56, Tres Seaver wrote:
Two modules do a really complicated and ugly conditional import dance to
try and make twisted availabe as an alternative to ZServer.
Can you explain a bit more?
I propose
we nuke that dance on the Zope trunk: at this point, we should prefer
to do WSGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
On 18.09.09 17:56, Tres Seaver wrote:
Two modules do a really complicated and ugly conditional import dance to
try and make twisted availabe as an alternative to ZServer.
Can you explain a bit more?
I propose
we nuke that
On 18.09.09 18:18, Tres Seaver wrote:
Andreas Jung wrote:
On 18.09.09 17:56, Tres Seaver wrote:
Two modules do a really complicated and ugly conditional import
dance to
try and make twisted availabe as an alternative to ZServer.
Can you explain a bit more?
I propose
we nuke that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
Sounds interesting.
Do you happen to have a list of packages that would be affected by
these rules?
Sure: all the zope.app packages. They have effectively been in
probationary status for a while now; I'm proposing to
On Fri, Sep 18, 2009 at 1:23 PM, Andreas Jung li...@zopyx.com wrote:
IIRC, the twisted integration code was added because Jim wanted us to
get out of the server business. At this point, I think that folks
wanting an alternative to ZServer should focus on using WSGI to
integrate with the
On Fri, Sep 18, 2009 at 5:59 PM, Tres Seaver tsea...@palladion.com wrote:
Most of the remaining zope.app dependencies in the Zope2 trunk are
related to Products.five.form. I propose moving all that code out to a
new package, e.g. 'five.forms', which can be included by anybody who
uses that
On Friday 18 September 2009, Jan-Wijbrand Kolman wrote:
Would it be a good idea to remove setting the cache headers from the
zope.app.publisher.browser resource implementations and make that more
pluggable? z3c.versionedresource could then probably get rid of the
resource subclasses, right?
On Fri, Sep 18, 2009 at 6:20 PM, Tres Seaver tsea...@palladion.com wrote:
Sure: all the zope.app packages. They have effectively been in
probationary status for a while now; I'm proposing to remove them
completely from the ZTK.
I'd like to leave any zope.app.* package in the under-review
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
On 18.09.09 18:18, Tres Seaver wrote:
Andreas Jung wrote:
On 18.09.09 17:56, Tres Seaver wrote:
Two modules do a really complicated and ugly conditional import
dance to
try and make twisted availabe as an alternative to
Hi Tres!
Tres Seaver wrote:
I don't know what the purpose of the following checkin was:
http://svn.zope.org/Zope/trunk/?rev=85827view=rev
See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html
but the tests all pass if I rip out the import, and Zope starts. I
don't know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi Tres!
Tres Seaver wrote:
I don't know what the purpose of the following checkin was:
http://svn.zope.org/Zope/trunk/?rev=85827view=rev
See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html
but the tests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
Wouldn't it make sense to move the VocabularyRegistry class into
zope.schema instead of forking it?
Nope -- the implementation uses zope.component, which would create a
cycle. The fork is really fine here: it is truly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
yuppie wrote:
Hi Tres!
Tres Seaver wrote:
I don't know what the purpose of the following checkin was:
http://svn.zope.org/Zope/trunk/?rev=85827view=rev
See https://mail.zope.org/pipermail/zope-dev/2008-April/031691.html
29 matches
Mail list logo
