Re: [Zope-dev] pinning, nailing and kgs'ing

2008-02-04 Thread Kevin Teague
On Feb 3, 2008, at 10:50 AM, Tim Terlegård wrote: On Feb 3, 2008, at 3:35 AM, Kevin Teague wrote: I wanted to try using the snowsprint-viewlets2 branch of grok in my project the other day. It took me a little time to figure out how to do this, so I thought it'd be nice if there was a bit

[Zope-dev] Re: [Checkins] SVN: zope.app.twisted/trunk/src/zope/app/twisted/ftp/utils.py fix of 599 error on conflict error in request

2008-02-04 Thread Christian Theune
Adam Groszer schrieb: Log message for revision 83376: fix of 599 error on conflict error in request see: http://mail.zope.org/pipermail/zope-dev/2008-January/030844.html I'm missing a test case here. Also the annotation style of the comment should go into a bug report and not into the

Re: [Zope-dev] more on stacked component registries

2008-02-04 Thread Stephan Richter
On Tuesday 15 January 2008, Chris Withers wrote: For what I'm after, I need to have a more dynamic buildup of registrations based on which objects have been traversed through. Right. I think the component architecture is not really made for this. I think it would be easier to turn on/off

Re: [Zope-dev] 2 failures on the KGS (z3c.rml zope.app.publication)

2008-02-04 Thread Stephan Richter
On Friday 11 January 2008, Christophe Combelles wrote: I was trying to read and understand zope.release and zope.kgs (to be able to add zope.app.locales 3.4.1 into the upcoming zope 3.4). Cool, did you get it to work? BTW, I have added this version to the KGS and it is life now. So I've

Re: [Zope-dev] Session concurrency problem

2008-02-04 Thread Stephan Richter
On Wednesday 30 January 2008, Dieter Maurer wrote: 2. Sometimes, the session package data does not have the data in it and fails with a key error. This happens maybe 1 in 50 times and I have not reliably reproduced this problem. What is session package data? A very simple object: class

[Zope-dev] Re: [Checkins] SVN: zope.server/trunk/s fix of 599 error on conflict error in request

2008-02-04 Thread Christian Theune
Hi, Adam Groszer schrieb: Log message for revision 83382: fix of 599 error on conflict error in request see: http://mail.zope.org/pipermail/zope-dev/2008-January/030844.html Changed: U zope.server/trunk/setup.py U zope.server/trunk/src/zope/server/ftp/publisher.py -=- Modified:

[Zope-dev] Zope Tests: 6 OK

2008-02-04 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Sun Feb 3 12:00:00 2008 UTC to Mon Feb 4 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Feb 3 21:02:22 EST 2008

[Zope-dev] Re[2]: [Checkins] SVN: zope.server/trunk/s fix of 599 error on conflict error in request

2008-02-04 Thread Adam Groszer
Hello Christian, I'm sorry Christian. Points taken, I'll try to do better next time. Actually the issue was an edge case. See my mail: http://mail.zope.org/pipermail/zope-dev/2008-January/030844.html Solution is to change: response = request.response publish(request) #do

[Zope-dev] How individual package versions are used in a release?

2008-02-04 Thread Dmitry Vasiliev
Hi All! I've just updated Russian translation at zope.app.locales and notice tags for all previous releases of the package. The question is should I create new tag (and update setup.py or something) for the package to be included into the next Zope 3 release? Links to a release politics for

Re: [Zope-dev] 2 failures on the KGS (z3c.rml zope.app.publication)

2008-02-04 Thread Christophe Combelles
Stephan Richter a écrit : On Friday 11 January 2008, Christophe Combelles wrote: I was trying to read and understand zope.release and zope.kgs (to be able to add zope.app.locales 3.4.1 into the upcoming zope 3.4). Cool, did you get it to work? BTW, I have added this version to the KGS and it

Re: [Zope-dev] How individual package versions are used in a release?

2008-02-04 Thread Christophe Combelles
Dmitry Vasiliev a écrit : Hi All! I've just updated Russian translation at zope.app.locales and notice tags for all previous releases of the package. The question is should I create new tag (and update setup.py or something) for the package to be included into the next Zope 3 release? Links