- Zope-Dev - Zope lists

Zope Tests: 2 OK, 3 Failed
by Zope Tests Summarizer 22 Sep '08

22 Sep '08

Summary of messages to the zope-tests list. Period Sun Sep 21 11:00:00 2008 UTC to Mon Sep 22 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Sep 21 20:55:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010202.html Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Sep 21 20:56:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010203.html Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Sep 21 20:58:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010204.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sun Sep 21 20:52:06 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010200.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Sep 21 20:53:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010201.html

1 0

Zope 3 wiki frontpage busted
by Christian Theune 22 Sep '08

22 Sep '08

Hi, the restructured Text layout is busted. I just reverted some spam, but that wasn't the issue. Could someone enlightened have a look, please? Christian -- Christian Theune · ct(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development

2 1

Zope Tests: 2 OK, 3 Failed
by Zope Tests Summarizer 21 Sep '08

21 Sep '08

Summary of messages to the zope-tests list. Period Sat Sep 20 11:00:00 2008 UTC to Sun Sep 21 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Sep 20 20:53:25 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010197.html Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Sep 20 20:54:55 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010198.html Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Sep 20 20:56:25 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010199.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Sep 20 20:50:25 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010195.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Sep 20 20:51:55 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010196.html

1 0

Zope Tests: 2 OK, 3 Failed
by Zope Tests Summarizer 20 Sep '08

20 Sep '08

Summary of messages to the zope-tests list. Period Fri Sep 19 11:00:00 2008 UTC to Sat Sep 20 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Sep 19 20:54:54 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010192.html Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Sep 19 20:56:24 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010193.html Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Sep 19 20:57:54 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010194.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Sep 19 20:51:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010190.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Sep 19 20:53:24 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010191.html

1 0

Re: [Zope-dev] Where to put custom schemas for z3c.form that depend onspecific libraries?
by Hermann Himmelbauer 20 Sep '08

20 Sep '08

Am Samstag 20 September 2008 03:37:00 schrieb Roger Ineichen: > Hi Hermann > > > Betreff: [Zope-dev] Where to put custom schemas for z3c.form > > that depend onspecific libraries? > > > > Hi, > > I need to create a specific schema for international bank > > account numbers (IBAN). I'd like to contribute this widget > > (maybe someone has use for it). > > However, this schema needs a specific library for validation, > > therefore I wonder where to put it? If I put it in z3c.schema > > (e.g. z3c.schema.iban / z3c.schema.payment), the library > > dependency will be problematic, I assume. > > > > Maybe I should create an own package for it? But with what > > name? What do you think? > > We should only put dependency less packages in to z3c.schema > because we will release that package as one egg. > > I think there is already a z3c.password schema field including a > widget etc. > > I recommend to put that package into the z3c namespace. > z3c.iban will be a very good name since the IBAN number > is now the defacto standard for international transactions. > > Does this makes sens for you? Yes, that's fine, "z3c.iban", then. Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

1 0

Where to put custom schemas for z3c.form that depend on specific libraries?
by Hermann Himmelbauer 20 Sep '08

20 Sep '08

Hi, I need to create a specific schema for international bank account numbers (IBAN). I'd like to contribute this widget (maybe someone has use for it). However, this schema needs a specific library for validation, therefore I wonder where to put it? If I put it in z3c.schema (e.g. z3c.schema.iban / z3c.schema.payment), the library dependency will be problematic, I assume. Maybe I should create an own package for it? But with what name? What do you think? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

2 1

date the KGS releases?
by Martijn Faassen 19 Sep '08

19 Sep '08

Hi there, Could we add dates to the KGS releases on the KGS page? http://download.zope.org/zope3.4/intro.html Where are the KGS versions listings tagged in SVN again? A link on the KGS page would be good too. Regards, Martijn

1 0

Re: [Zope-dev] zope.sqlalchemy locks up transaction
by Laurence Rowe 19 Sep '08

19 Sep '08

2008/9/19 Laurence Rowe <laurence(a)lrowe.co.uk>: > 2008/9/19 Hermann Himmelbauer <dusty(a)qwer.tk>: >> Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer: >>> Brian Sutherland wrote at 2008-9-17 12:33 +0200: >>> >On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote: >>> >> Brian Sutherland wrote: >>> >> > Hi, >>> >> > >>> >> > I've recently seen a situation where zope.sqlalchemy locked up the >>> >> > transaction machinery. I'm not sure exactly what happened, but have >>> >> > attached a failing test for at least one bug which may have caused it. >>> >> > Hopefully it's self explanatory;) >>> >> > >>> >> > If someone could help me solve this, that would be great! >>> >> >>> >> Could you try this with latest trunk. I checked in a fix the other day >>> >> that may help. >>> > >>> >I just checked in a fix, please feel free to comment on/revert it if >>> >it's not up to standard:) >>> >>> It looks not yet right to clear the state in "tpc_vote" when >>> a two phase commit is used (which is now supported by "SQLAlchemy"). >>> >>> In addition, there may be a problem in case "session.close()" raises >>> an exception. Then, "_finish" would not be called. >> >> This may not be connected, but I just wanted to point out a problem with >> configurations with "autoflush=False". If I change some database object >> attributes in the session but do not call session.flush(), the data is not >> stored into the database, as no commit() is called, which would then flush >> out/commit the data. >> >> So perhaps this is something to think about, or, at least something to be >> denoted in the documentation. >> >> I circumvented the problem by setting autoflush=True and modifying my code so >> that it works (although it's quite complicated). > > I don't think this is related to the above problem, but it may be a > bug in SQLAlchemy 0.4 whose behaviour I have replicated. > > In 0.4 orm.session during a commit flush is called: > > 245 if self.autoflush: > 246 self.session.flush() > > whereas in 0.5 flush is called unconditionally so long as there is not > a flush in progress. > > 358 if not self.session._flushing: > 359 self.session.flush() > > The documentation for 0.4 appears to be misleading: > > commit() serves two purposes; it issues a flush() unconditionally to > persist any remaining pending changes. > > > I think I should change zope.sqlalchemy to flush during it's tpc_begin > phase. This should only be done if a flush is not already in progress, > as otherwise sqlalchemy would raise an error. self.session._flushing > is only in 0.5 though, so maybe it is time to up the dependency. Or > maybe it is impossible for it to be in the flushing state at that > point anyway, as all user code will have completed. Correction, this is my misunderstanding of sqlalchemy, as explained on irc: <stepz> elro: that's when you do session.begin(autoflush=False) So I should just make it an unconditional flush() Laurence

1 0

Re: [Zope-dev] zope.sqlalchemy locks up transaction
by Hermann Himmelbauer 19 Sep '08

19 Sep '08

Am Freitag 19 September 2008 11:59:55 schrieb Laurence Rowe: > 2008/9/19 Hermann Himmelbauer <dusty(a)qwer.tk>: > > Am Donnerstag 18 September 2008 07:08:56 schrieb Dieter Maurer: > >> Brian Sutherland wrote at 2008-9-17 12:33 +0200: > >> >On Tue, Sep 16, 2008 at 02:01:07PM +0100, Laurence Rowe wrote: > >> >> Brian Sutherland wrote: > >> >> > Hi, > >> >> > > >> >> > I've recently seen a situation where zope.sqlalchemy locked up the > >> >> > transaction machinery. I'm not sure exactly what happened, but have > >> >> > attached a failing test for at least one bug which may have caused > >> >> > it. Hopefully it's self explanatory;) > >> >> > > >> >> > If someone could help me solve this, that would be great! > >> >> > >> >> Could you try this with latest trunk. I checked in a fix the other > >> >> day that may help. > >> > > >> >I just checked in a fix, please feel free to comment on/revert it if > >> >it's not up to standard:) > >> > >> It looks not yet right to clear the state in "tpc_vote" when > >> a two phase commit is used (which is now supported by "SQLAlchemy"). > >> > >> In addition, there may be a problem in case "session.close()" raises > >> an exception. Then, "_finish" would not be called. > > > > This may not be connected, but I just wanted to point out a problem with > > configurations with "autoflush=False". If I change some database object > > attributes in the session but do not call session.flush(), the data is > > not stored into the database, as no commit() is called, which would then > > flush out/commit the data. > > > > So perhaps this is something to think about, or, at least something to be > > denoted in the documentation. > > > > I circumvented the problem by setting autoflush=True and modifying my > > code so that it works (although it's quite complicated). > > I don't think this is related to the above problem, but it may be a > bug in SQLAlchemy 0.4 whose behaviour I have replicated. > > In 0.4 orm.session during a commit flush is called: > > 245 if self.autoflush: > 246 self.session.flush() > > whereas in 0.5 flush is called unconditionally so long as there is not > a flush in progress. > > 358 if not self.session._flushing: > 359 self.session.flush() > > The documentation for 0.4 appears to be misleading: > > commit() serves two purposes; it issues a flush() unconditionally to > persist any remaining pending changes. Ah, I see, that's really misleading. > I think I should change zope.sqlalchemy to flush during it's tpc_begin > phase. This should only be done if a flush is not already in progress, > as otherwise sqlalchemy would raise an error. That's maybe a good idea. > self.session._flushing > is only in 0.5 though, so maybe it is time to up the dependency. What do you mean with "up the dependency"? If you mean dropping support for SA 0.4, please, *please* don't do that (0.5's autoflushing breaks things here and Database support for MaxDB/SAPDB is somehow flawed.). Due to many incompatibilites, I cannot switch to SA 0.5, so I'd really appreciate support for SA 0.4! > Or > maybe it is impossible for it to be in the flushing state at that > point anyway, as all user code will have completed. If I understand it right, the problem does not occur in SA 0.5, right? If that's the case, maybe it is enough to outline the behaviour of SA 0.4 in the documentation and leave it as it is. Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

1 0

Zope Tests: 2 OK, 3 Failed
by Zope Tests Summarizer 19 Sep '08

19 Sep '08

Summary of messages to the zope-tests list. Period Thu Sep 18 11:00:00 2008 UTC to Fri Sep 19 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Sep 18 20:54:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010187.html Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Sep 18 20:56:23 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010188.html Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Sep 18 20:57:53 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010189.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu Sep 18 20:51:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010185.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Sep 18 20:53:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-September/010186.html

1 0