July 2008 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 21 Jul '08

21 Jul '08

Summary of messages to the zope-tests list. Period Sun Jul 20 11:00:00 2008 UTC to Mon Jul 21 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sun Jul 20 21:02:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009885.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 20 21:04:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009886.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 20 21:05:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009887.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 20 21:07:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009888.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 20 21:08:59 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009889.html

1 0

PAULA: bringing Zope 3's authentication to Plone and beyond
by Florian Friesdorf 21 Jul '08

21 Jul '08

Hi *, within the scope of google summer of code I am integrating zope 3's PAU with Plone's PAS and further enable (non-AT) content objects as source for users and groups. All functionality is developed in pure zope3, the plone integration is happening in a separate packages. All documents describing the project, as well as links to the code can be found here: https://chaoflow.net/projects/gsoc2008/z3membrane-ldap The code is not very interesting right now, but now would be the time to take any influence on what will be created during the next month - I am planning to continue to work on the project after the SoC. I will keep you updated on major advancements of the code. regards florian

10 30

Re: SVN: grokcore.view/trunk/ get rid of another collective'ism :)
by Tres Seaver 20 Jul '08

20 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp von Weitershausen wrote: > Log message for revision 88608: > get rid of another collective'ism :) > many people don't seem to know this, but you can do > > svn propedit svn:ignore > > There's no need to keep a separate file around for the ignores. I think originally folks started doing this because the properties (svn:ignore, svn:externals) can't be viewed from the web interface. I'm not arguing for the practice, and in fact would prefer that we update the webapp to something which *can* expose the properties. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIgjNV+gerLs4ltQ4RAgVLAJ4otrLYZ9BXKbhhF6uZOIoRnLr/GACffxNk CkZdKAzFcBK7QP6lsO+KYOY= =xE2B -----END PGP SIGNATURE-----

4 3

Zope Tests: 5 OK
by Zope Tests Summarizer 20 Jul '08

20 Jul '08

Summary of messages to the zope-tests list. Period Sat Jul 19 11:00:00 2008 UTC to Sun Jul 20 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat Jul 19 20:58:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009880.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 19 20:59:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009881.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 19 21:01:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009882.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 19 21:02:41 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009883.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 19 21:04:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009884.html

1 0

Strange zc.testbrowser.real issues (javascript problem)
by Graham Stratton 20 Jul '08

20 Jul '08

Hi, I've been developing tutorialtest ( http://grahamstratton.org/straightornamental/entries/z3ctutorialtest ), and hit on a couple of issues with zc.testbrowser.real. These may be Firefox bugs, but I know very little about DOM stuff, and my Javascript books are 11,000 miles away. My web application allows the user to toggle the visibility of some forms. I found that setting the value of form elements in forms that had at one point been hidden failed. It turns out that setAttribute('value', ...) stops working, as shown in the REPL session below. Initally it's possible to set values quite happily (note that element.value consistently gives the value that is displayed and submitted. element.getAttribute(value) consistently gives the value set with setAttribute; the problem is when these differ): repl> content .document.getElementById('form.name').setAttribute('value','three') repl> content.document.getElementById('form.name').value "three" repl> content .document.getElementById('form.name').setAttribute('value','four') repl> content.document.getElementById('form.name').value "four" Now if we hide and show the element (or any enclosing element), setAttribute stops working: repl> content.document.getElementById('form.name').style.display "" repl> content.document.getElementById('form.name').style.display = 'none' "none" repl> content.document.getElementById('form.name').style.display = '' "" repl> content .document.getElementById('form.name').setAttribute('value','three') repl> content.document.getElementById('form.name').value "four" I edited real.py to read and write the property directly rather than using (s/g)etAttribute for all elements except file controls. After that, all the tests still pass. I suspect this is not good practice, but it makes it work. Should I check in this patch, or is there a better fix? Many thanks, Graham Patch against MozLab 0.1.9 branch of zc.testbrowser: Index: src/zc/testbrowser/real.py =================================================================== --- src/zc/testbrowser/real.py (revision 88569) +++ src/zc/testbrowser/real.py (working copy) @@ -399,7 +399,7 @@ def value(): def fget(self): - if self.type == 'textarea': + if self.type != 'file': return self.browser.execute('tb_tokens[%s].value' % self.token) return self.browser.execute( @@ -419,7 +419,7 @@ self.mech_control.items[0].selected = bool(value) else: self.browser.execute( - 'tb_tokens[%s].setAttribute("value", %s)' %( + 'tb_tokens[%s].value = %s' %( self.token, simplejson.dumps(value))) return property(fget, fset)

1 0

No events in zope.annotation
by Stephan Richter 19 Jul '08

19 Jul '08

Hi everyone, I just tried to create a catalog for an annotation and noticed that it does not get filled. Digging around in the zope.annotation package, I noticed that the zope.annotation package does not send out any object events. This sucks. ;-) Thus I propose: - Add ObjectCreatedEvent event notification to zope.annotation factory call. - Add ObjectAddedEvent to attribute annotations __setitem__. - Add ObjectRemovedEvent to attribute annotations __delitem__. This would mimic the behavior of the other containers. the downside is that we have 2 new dependencies, zope.event and zope.lifecycleevent, both of which are acceptable in my opinion. Comments? Silence is consent as always. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. "Zope Stephan Richter"

7 22

Zope Tests: 5 OK
by Zope Tests Summarizer 19 Jul '08

19 Jul '08

Summary of messages to the zope-tests list. Period Fri Jul 18 11:00:00 2008 UTC to Sat Jul 19 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri Jul 18 21:01:14 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009875.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jul 18 21:02:45 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009876.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jul 18 21:04:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009877.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jul 18 21:05:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009878.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Jul 18 21:07:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009879.html

1 0

zope.sqlalchemy and in-memory sqlite
by Malthe Borch 18 Jul '08

18 Jul '08

With an in-memory engine, I seem to lose track of the tables after the first response. Turn of events: 1. Request comes in 2. Create some tables 3. Add content and commit transaction 4. Query content 5. Return response Now... 6. New request comes in 7. Query content (OperationalError) no such table: mytable ... With a disk-based database, no errors occur. The point of my little story line was to illustrate that this does not have anything to do with transactions being committed. \malthe

2 1

Zope 3 on Python 2.5, Zope 3 releases
by Martijn Faassen 18 Jul '08

18 Jul '08

Hi there, I'm curious about the plans of Zope 3 on Python 2.5. * Are people using Zope 3 with Python 2.5 already? What are your experiences? * Are there plans for a release after Zope 3.4? I'm just assuming that Zope 3.4.0c1 is actually the only release that Zope 3.4 is going to see. Any plans or interest in a Zope 3.5? * Is someone exercising the "trunk" version of KGS, running the tests to see whether everything works together? Is someone actually updating the versions? Could we somehow broaden the community for this? I'd be nice if we could move Grok to Python 2.5, but it'd be nice to if that were somehow coordinated with Zope 3. What would the policy be for checkins of Zope-related packages? Could we use new Python 2.5 features, for instance? Regards, Martijn

11 33

Please use 'svn mv'
by Philipp von Weitershausen 18 Jul '08

18 Jul '08

I would like to remind everyone that when you do refactorings and move code around, to please use 'svn mv' or 'svn cp'. For instance, when you split a large file into two smaller ones, use 'svn cp' to create the second file and then remove stuff from it that doesn't go there. That way, version history isn't lost for neither parts of the code. The same goes for splitting up packages (moving components into a library package, for instance). Thanks.

1 0