- Zope-Dev - Zope lists

issues with building zope2.11.3
by Jonas Meurer 02 Jul '09

02 Jul '09

Hello, at preparing zope2.11.3 for debian, i came across several byte-compiling errors. three of them are due to the new tests for python2.5 and python2.6, and are just failing because python2.4 is the python version debian uses for zope2.11. but the last one seems to be a real bug: Compiling /usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py ... File "/usr/lib/zope2.11/lib/python/mechanize/_firefox3cookiejar.py", line 91 yield row SyntaxError: 'yield' not allowed in a 'try' block with a 'finally' clause I also found this error in list archive logs of zope-tests(a)epy.co.at. from 'pydoc2.4 yield': The yield statement is not allowed in the try clause of a try ... finally construct. The difficulty is that there's no guarantee the generator will ever be resumed, hence no guarantee that the finally block will ever get executed. is this a known bug, and does a fix exist? greetings, jonas

2 5

zope.testing 3.7.7
by Christian Theune 02 Jul '09

02 Jul '09

I just released zope.testing 3.7.7. It only contains a single change: installing the test runner callable via a console_script entry point to allow simple usage without buildout. 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 4

FYI: svn.zope.org change for svn:// protocol service
by Jens Vagelpohl 02 Jul '09

02 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, This is a heads-up that affects anyone accessing the SVN repositories using the svn:// protocol (so it does not affect anyone accessing SVN over HTTP, or svn+ssh): So far the svn service was run through xinetd. We had recurring problems where either during really busy times or when too many svn service processes hung for unknown reasons xinetd would refuse to start more of them. This would lead to strange errors for people accessing the service. To hopefully solve that problem, and maybe solve the "hanging process" issues as well, I have switched to using the svnserve process in daemon mode instead of using it through xinetd. If you do use the svn:// protocol (maybe directly, or indirectly through a svn:extrnals definition, or for replicating the repositories with "svnsync") and see any issues please contact me directly off-list. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkpMwSkACgkQRAx5nvEhZLJgKwCglIvmEO9jeoEa3ZrYGo3fas+g 5LQAoJf+F7r4L31He5jrvubNqz7YnTpV =37QJ -----END PGP SIGNATURE-----

1 0

Re: [Zope-dev] How to test changes to ZTK packages?
by Jim Fulton 01 Jul '09

01 Jul '09

On Jun 30, 2009, at 10:14 AM, Stephan Richter wrote: > On Tuesday 30 June 2009, Jim Fulton wrote: >> I should know this, but I don't. What is the recommended way to test >> changes to core ZTK packages to mitigate the risk that changes affect >> other packages? Is there a page somewhere with instructions? >> >> I tried using using zope.release. Building the trunk of zope.release >> with Python 2.4 and running the tests gives lots of test import >> errors >> and test failures. (Lots of tests want to import z3c.pt.) The tests >> hang when I try to build and run with Python 2.6. > > Yes, I think testing with zope.release is a good way of doing this > right now. What is the difference between zope.release and zope.kgs? Is the latter a fossil? Does it need to go away? Why does zope.release have a 2-step build process? Perhaps naively, it seems that one could define a simple project that defined a test script over a "known good set" of projects. Is the 2-step process a consequence of maintaining the index or tar ball? (I'm not criticizing, I'm just trying to understand.) Jim -- Jim Fulton Zope Corporation

2 2

zope.interface 3.5.2 release
by Fred Drake 01 Jul '09

01 Jul '09

I just released zope.interface 3.5.2, which adds only this bug fix: - BaseAdapterRegistry.unregister, unsubscribe: Remove empty portions of the data structures when something is removed. This avoids leaving references to global objects (interfaces) that may be slated for removal from the calling application. I've made a source distribution available via PyPI: http://pypi.python.org/pypi/zope.interface/ Windows users would likely be thankful if someone with the appropriate tools and know-how to build Windows binary distributions were to do so and upload those to PyPI as well. Enjoy! -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller

2 2

Making PersistentList satisfy zope.schema.List
by Paul Carduner 01 Jul '09

01 Jul '09

I noticed that PersistentList and PersistentDict do not satisfy zope.schema.List or zope.schema.Dict, which is rather annoying. For example: class IBlogPost(Interface): tags = zope.schema.List(title=u'Tags', value_type=zope.schema.TextLine) class BlogPost(Persistent): implements(IBlogPost) tags = FieldProperty(IBlogPost['tags']) def __init__(self): super(BlogPost, self).__init__() self.tags = persistent.list.PersistentList() #aaah, WrongType error... will throw a WrongType: ([], <type 'list'>) error, which is especially confusing because the repr for PersistentList makes it look an awful lot like a regular list. same thing happens with PersistentDict. I would like to modify zope.schema._bootstrapfields by changing the _type attribute of the List class to (list, UserList), and do the same for Dict with (dict, UserDict). Then anything inheriting from UserList (including PersistentList) will satisfy the schema. Can anyone think of a reason why this would be bad? -- Paul Carduner http://www.carduner.net

3 2

Zope Tests: 8 OK
by Zope Tests Summarizer 30 Jun '09

30 Jun '09

Summary of messages to the zope-tests list. Period Mon Jun 29 12:00:00 2009 UTC to Tue Jun 30 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: Mon Jun 29 20:49:37 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012059.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 29 20:51:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012060.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 29 20:53:47 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012061.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Jun 29 20:55:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012062.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Mon Jun 29 20:57:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012063.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Jun 29 20:59:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012064.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Jun 29 21:01:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012065.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Mon Jun 29 21:03:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-June/012066.html

1 0

Re: [Zope-dev] SVN: zope.dublincore/trunk/setup.py Add 'zope.app.component' to the 'test' extra in the setup.py so that the
by Tres Seaver 29 Jun '09

29 Jun '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aaron Lehmann wrote: > Log message for revision 101312: > Add 'zope.app.component' to the 'test' extra in the setup.py so that the > creatorannotator tests can pass. > > > > Changed: > U zope.dublincore/trunk/setup.py > > -=- > Modified: zope.dublincore/trunk/setup.py > =================================================================== > --- zope.dublincore/trunk/setup.py 2009-06-29 11:48:01 UTC (rev 101311) > +++ zope.dublincore/trunk/setup.py 2009-06-29 13:36:38 UTC (rev 101312) > @@ -36,7 +36,11 @@ > namespace_packages=['zope'], > include_package_data=True, > extras_require=dict( > - test=['zope.testing', 'zope.security', 'zope.app.testing'] > + test=[ > + 'zope.app.component', > + 'zope.testing', > + 'zope.security', > + 'zope.app.testing'] > ), > install_requires = ['setuptools', > 'zope.annotation', This *can't* be the right fix! (/me checks the tests). Those tests are *terrible*: we should be rewriting them, rather than papering over a completely stupid dependency on zope.app.component. 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 iD8DBQFKSSGE+gerLs4ltQ4RAkieAJ4hBsR9MoQ/oVRgOAYIxfH4IeQYRQCgsU4j ioE53ucXAZwYIwBu/3SDm6c= =xEN8 -----END PGP SIGNATURE-----

1 0

ZCatalog and indexes cleanup
by yuppie 29 Jun '09

29 Jun '09

Hi! I did plan to work on a small catalog improvement, but after looking at the code I'd like to do some cleanup first: 1.) remove the deprecated TextIndex The deprecation warning says: 'Using TextIndex is deprecated (will be removed in Zope ' '2.12). Use ZCTextIndex instead.' 2.) remove CHANGES.txt, README.txt and version.txt from Products/ZCatalog These files seem to be obsolete. 3.) remove security declarations from ZCTextIndex and DateRangeIndex All the other indexes don't have security declarations. AFAICS there is no way to access indexes from untrusted code without having the 'Manage ZCatalogIndex Entries' permission. 4.) add 'indexSize' to IPluggableIndex and implement it where missing ZCatalog uses that method and most indexes implement it already. If there are no objections, I'll make these changes on the 2.12 branch and the trunk. Cheers, Yuppie

3 4

Schema to JSON
by Paul Wilson 29 Jun '09

29 Jun '09

Hi, I'm about to embark on a module to serialize Zope schemas into the JSON format for my application, taking inspiration from z3c.schema2xml. I've had a look around SVN to see if this functionality has already been implemented but can't find anything - does anybody know whether this has already been done somewhere? Also, it makes sense in my mind for a schema2xml and schema2json to implement the same interface. How does Zope handle this case? With a format agnostic interface module or something? Many thanks, Paul

4 3