[Zope-dev] Zope Tests: 8 OK

2009-10-11 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list.
Period Sat Oct 10 12:00:00 2009 UTC to Sun Oct 11 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: Sat Oct 10 20:47:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012752.html

Subject: OK : Zope-2.11 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Oct 10 20:49:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012753.html

Subject: OK : Zope-2.12 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Oct 10 20:51:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012754.html

Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux
From: Zope Tests
Date: Sat Oct 10 20:53:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012755.html

Subject: OK : Zope-2.12 Python-2.6.2 : Linux
From: Zope Tests
Date: Sat Oct 10 20:55:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012756.html

Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Sat Oct 10 20:57:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012757.html

Subject: OK : Zope-trunk Python-2.6.2 : Linux
From: Zope Tests
Date: Sat Oct 10 20:59:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012758.html

Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux
From: Zope Tests
Date: Sat Oct 10 21:01:50 EDT 2009
URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012759.html

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] ZODB Competing read/writes: How to find out which attribute?

2009-10-11 Thread Jim Fulton
On Sat, Oct 10, 2009 at 10:00 PM, Shane Hathaway sh...@hathawaymix.org wrote:
 Hermann Himmelbauer wrote:
 That's exactly the problem - it's a read operation and there should not be 
 any
 write operation involved. However, it's hard to find out where the write
 operation in my code occurs, I can't find it in the view, maybe there's
 something in the authentication code, but I'd have to dig deep through my
 source. So It would be extremely helpful to know a faster way to find out
 what code triggered this warning.

 The code that modifies something will indirectly call the register()
 method of the ZODB.Connection class.  If you arrange for
 Connection.register() to raise an exception when the transaction is not
 supposed to modify anything, you should get a traceback that pinpoints
 what is doing the modification.  Unfortunately, there is no API for
 that, so the easiest thing to do is modify the source code of the
 register() method in ZODB.Connection.  Fortunately, this is Python, so
 modifying someone else's code is usually quite easy. :-)

Easier yet, in a development environment, add a breakpoint in register
and make a read-only request to see what's causing it to be called and
why.

Jim

-- 
Jim Fulton
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] zope.site.hooks

2009-10-11 Thread Fabio Tranchitella
Hello,

* 2009-10-09 15:37, Martijn Faassen wrote:
 I'm okay with *not* doing the split up and going with your idea, but I
 think eventually such a split up would simplify things. One advantage
 would be that someone could examine repoze.zcml and not see distracting
 ZCML implementations in zope.component *too*.

I may be wrong, but I suppose the dependency on zope.security in
zope.component is the only reason why repoze.zcml is around.

I tried to implement my idea here:

  
svn://svn.zope.org/repos/main/zope.component/branches/conditional-zope.security

This is a quite intrusive change, so please take it as a suggestion and
not as a real proposal: is this the right approach? I did not (yet) write
all the tests needed (and I don't like the idea of duplicating the tests in
zcml_conditional.txt, to be honest).

Thanks,
Fabio
___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )