Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-17 Thread Christian Theune
Hi, On 09/16/2009 09:19 AM, Martijn Faassen wrote: > Hey, > > Stephan Richter wrote: > [snip] >> -1 from me too. Having the previous version avoids having to look it up in >> CHANGES.txt or the tags, which is really lame if you do lots of releasing. > > From private conversations here at the G

Re: [Zope-dev] zc.zope3recipes:instance: zdaemon/eventlog rotatation

2009-09-17 Thread Christian Zagrodnick
On 2009-09-16 13:03:44 +0200, Jim Fulton said: > On Wed, Sep 16, 2009 at 5:28 AM, Christian Zagrodnick wrote: >> The zc.zope3recipes:instance recipe creates a zdaemon.conf which writes >> the transcript_log and zdaemon's eventlog to the same file. That's >> actually fine. >> >> ZDaemon's reopen

[Zope-dev] Redesign suggestion for IReRaiseException

2009-09-17 Thread Christian Theune
Hi, I'd like to suggest a redesign of the IReRaiseException. I found this when reviewing revision 103682 and stumbled over the naming of the interfaces and that the interface only mentions a __call__ to retrieve a fact. IMHO this pattern smells like we should design an interface like this: clas

Re: [Zope-dev] Redesign suggestion for IReRaiseException

2009-09-17 Thread Martijn Faassen
Hey, Christian Theune wrote: > I'd like to suggest a redesign of the IReRaiseException. > > I found this when reviewing revision 103682 and stumbled over the naming > of the interfaces and that the interface only mentions a __call__ to > retrieve a fact. > > IMHO this pattern smells like we shou

[Zope-dev] Zope Tests: 8 OK

2009-09-17 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Wed Sep 16 12:00:00 2009 UTC to Thu Sep 17 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: Wed Sep 16 22:22:33 EDT 2009 URL: http://

Re: [Zope-dev] zope.location.pickling.PathPersistent and BBB

2009-09-17 Thread Thomas Lotze
Martijn Faassen wrote: > Sounds like you did the research. I've considered all packages mentioned in the current ztk.cfg that come from the zope.* namespace. The BBB stuff from zope.location.pickling is neither used by any of them, nor do compat-tests involving the pinned versions of those packag

Re: [Zope-dev] Redesign suggestion for IReRaiseException

2009-09-17 Thread Christian Theune
On 09/17/2009 01:48 PM, Martijn Faassen wrote: > Hey, > > Christian Theune wrote: >> I'd like to suggest a redesign of the IReRaiseException. >> >> I found this when reviewing revision 103682 and stumbled over the naming >> of the interfaces and that the interface only mentions a __call__ to >> re

Re: [Zope-dev] Redesign suggestion for IReRaiseException

2009-09-17 Thread Martijn Faassen
Hey, Christian Theune wrote: >> This would be an interface on exceptions, right? Would it try to adapt >> exceptions raised to IPublisherExceptionInfo and if successful look at >> this attribute? So an exception can either implement this interface >> directly, or you could register an adapter

Re: [Zope-dev] Redesign suggestion for IReRaiseException

2009-09-17 Thread Christian Theune
On 09/17/2009 10:49 PM, Martijn Faassen wrote: > Hey, > > Christian Theune wrote: > >>> This would be an interface on exceptions, right? Would it try to adapt >>> exceptions raised to IPublisherExceptionInfo and if successful look at >>> this attribute? So an exception can either implement this

[Zope-dev] Visibility of policy changes: Was: [Checkins] SVN: zope.app.security/trunk/ keep trunk version at 0. Update changes

2009-09-17 Thread Christian Theune
On 09/11/2009 05:58 PM, Martijn Faassen wrote: > Fred Drake wrote: >> On Fri, Sep 11, 2009 at 8:53 AM, Martijn Faassen >> 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 somewhere