- Zope-Dev - Zope lists

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

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

18 Jul '08

Summary of messages to the zope-tests list. Period Thu Jul 17 11:00:00 2008 UTC to Fri Jul 18 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: Thu Jul 17 21:01:24 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009870.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 17 21:02:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009871.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 17 21:04:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009872.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 17 21:05:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009873.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Jul 17 21:07:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009874.html

1 0

Re: Buildout site
by Ethan Jucovy 18 Jul '08

18 Jul '08

On Thu, Jul 17, 2008 at 2:17 PM, Martijn Faassen <faassen(a)startifact.com> wrote: >> Just FYI, the final resting place for this information will likely be >> inside a more general documentation website, the address buildout.zope.org >> is just a temporary resting place. > > Just to make a discussion Jens and I were having in the background explicit. > > While it's good if this appears in the "Zope stack" documentation site, I > think it's also important for there being a separate identity for the > buildout project. This goes beyond documentation, but also talks about a > developer community and invites people to use it in their own projects, as > well as contribute. I also think an overview of recipes could be a good part > of this. > > I think a separate website is part of such an identity. Other things that > could help establish an identity are things like a logo. I think this is a really fantastic idea. To speak broadly, it's great that you're so mindful of the real importance of identity -- in both a "branding" sense and simply in the sense of being a self-contained entity -- for the development of software communities and software itself. Buildout is a standalone product independent of the Zope framework or libraries, but that's only meaningful if it actively establishes an independent identity in people's minds. I think you're doing a really great thing for the community by paying attention to these issues. So, in short, thanks. :) Cheers, Ethan > > Regards, > > Martijn > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) >

1 0

repoze.bfg
by Chris McDonough 18 Jul '08

18 Jul '08

I've been working on a new web framework named (provisionally) repoze.bfg. The relevant README is here: http://svn.repoze.org/repoze.bfg/trunk/README.txt It is essentially a "Zope lite". It is Zope-ish in that: - it uses a lot of Zope libraries and concepts (interfaces, some CA constructs, ZCML) - it uses graph-traversal-based URL dispatch. - by default it provides ZPT (actually z3c.pt) templates. - it provides built-in authorization facilities based on permissions and users/groups. It is unlike Zope (variously 2 or 3) inasmuch as: - It uses a different publisher and authorization model. - It is heavily dependent on WSGI. - Its equivalent of the publisher doesn't attempt to traverse into *code* stored in the object graph. All code is on the filesystem. The only thing in the object graph is "model" data. - It doesn't attempt to provide any server functionality. This duty is left over to WSGI. - It doesn't provide *authentication* functionality (just authorization functionality). Authentication is left up to upstream server/middleware (e.g. repoze.who). - It's not meant to be "plugged in to". A repoze.bfg application is not a plugin to repoze.bfg (e.g. it's not a Zope2 Product). Instead, a repoze.bfg application is just a Python package that happens to use repoze.bfg facilities. - The graph root is not effectively assumed to be a ZODB database. - It provides no built-in through-the-web management interface. It's unlike Grok inasmuch as: - It doesn't try to hide ZCML for configuration. If I were to characterize it succintly and informally, I migh say it's a bit like Django built around graph traversal dispatch instead of URL-based dispatch. Speed is a priority. A "hello world" template is currently clocking in at around 550 req/sec on my MacBook (including security lookups). It's my intent to continue to develop it, along with a package named "repoze.lemonade", which will integrate repoze.bfg with ZODB and provide various persistence-related features (folders, object events, indexing and so forth). In any case, I thought maybe some folks would be interested in using/contributing to it. It can be checked out via: svn co http://svn.repoze.org/repoze.bfg/trunk/ Thanks, - C

6 18