April 2010 - Zope-Dev

Repository policy testing
by Tres Seaver 08 Apr '10

08 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I woul like for the checkouts made to test repository policy should use the '--ignore-externals' flag, because the code brought in as externals is either checked separately, or else corresponds to a (non-checked) tag. 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku8qGwACgkQ+gerLs4ltQ5qEACeIH3Is3u6syMlIO8s9SevkzW+ 3QYAniG6BHS4U8se6fau4dbiMoAzRvAa =s2cC -----END PGP SIGNATURE-----

3 5

short svn.zope.org downtime
by Hanno Schlichting 08 Apr '10

08 Apr '10

Hi, looks like SVN and viewcvs weren't responding for a couple minutes. I could log into the machine via SSH and Apache serving docs.zope.org still worked. I only noticed: 27059 simon 20 0 98664 6388 4360 R 100 0.2 43327:19 darcs Why do we have darcs running on that machine and more importantly why does it run with 100% cpu load for minutes (or hours?). Hanno

7 11

Zope Tests: 6 OK, 1 Failed
by Zope Tests Summarizer 08 Apr '10

08 Apr '10

Summary of messages to the zope-tests list. Period Wed Apr 7 12:00:00 2010 UTC to Thu Apr 8 12:00:00 2010 UTC. There were 7 messages: 6 from Zope Tests, 1 from ct at gocept.com. Test failures ------------- Subject: FAILED: Repository policy check found errors in 697 projects From: ct at gocept.com Date: Wed Apr 7 21:11:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013877.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 7 21:29:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013878.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Apr 7 21:31:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013879.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 7 21:33:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013880.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 7 21:35:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013881.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 7 21:37:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013882.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Apr 7 21:39:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013883.html

1 0

Re: [Zope-dev] zc.authorizedotnet support for Automated Recurring Billing
by Zvezdan Petkovic 07 Apr '10

07 Apr '10

On Apr 7, 2010, at 2:35 PM, David Glick wrote: > Understood. Now that Plone 4 is almost ready and using Python 2.6, > there are a number of Plone GetPaid users who are ready to use these > changes as soon as they're released. :) zc.ssl-1.2 and zc.authorizedotnet-1.3.1 have been tagged and released on PyPI. Regards, Zvezdan

1 0

Re: [Zope-dev] zc.authorizedotnet support for Automated Recurring Billing
by Zvezdan Petkovic 07 Apr '10

07 Apr '10

On Apr 7, 2010, at 1:33 PM, David Glick wrote: > I also need to make some updates to make zc.authorizedotnet work with > Python 2.6, as it currently depends (via zc.ssl) on ssl-for-setuptools, which is a backport of the ssl module that ships with Python 2.6. You will not need to make those updates. I already did. :-) I have the changes ready for commit and will do that very soon. However, zc.authorizedotnet *must* continue working with Python 2.4. > Having heard no further response, I will proceed by forking the packages I need to modify and releasing them in the z3c namespace -- but please contact me if we can avoid that. Yes we can. As explained above, I'll commit the changes. I'm sorry for not replying immediately, but I've been *very* busy and since the thread referred to in the initial message is over two years old I didn't think this was so urgent. So, please have a little patience, I'll commit all the necessary changes that make zc.authorizedotnet, zc.ssl, and zc.creditcard Python2.4 to 2.6 compliant. Regarding the interest in the other protocol for Authorize.Net recurring payments, I think it could be a small package itself. It's a feature/protocol independent of the zc.authorizedotnet and can be seen as an additional functionality. Best regards, Zvezdan

1 0

Segfault in zope.configuration
by Martin Aspeli 07 Apr '10

07 Apr '10

Hi, I'm not sure if this is a Python issue or a zope issue. We're getting a segfault on 64-bit SuSE Linux (SLES 11), originating from z3c.autoinclude, which in turn called zope.configuration's <include /> implementation. This calls expat, which then crashes (no error, log message, or core file, but it has all the markings of a segfault) during parsing of the file. The weird thing is that it's not parsing of any file: it happens during a standard configure.zcml (for the collective.xdv package), but z3c.autoinclude itself is invoked from another ZCML file, so it must've been able to read that. Any tips on how to debug or similar experiences would be appreciated! Martin

6 20

NEO High Performance Distributed Fault Tolerant ZODB Storage
by Vincent Pelletier 07 Apr '10

07 Apr '10

Hi, I would like to present you the NEOPPOD project, aiming at improving ZODB Storage scalability. The implementation is in a rather good shape, although it fails at a few ZODB tests at the moment (they are currently being worked on). Scalability is achieved by distributing data over multiple servers (replication and load balancing) with the ability to extend/reduce cluster on-line. Its code is available under the GPL, more information can be found on the project website[1]. One nice aspect is that the underlying protocol is being analysed with model-checking tools based on Petri Nets by a team of post-doc, PhD students and researchers. An article should appear in PETRI NETS 2010 [2]. We hope that NEO will be usable for production systems in 12 months from now, and will notify the community the day we think it is, ie. after using it ourselves. Meanwhile, it can be interesting for research and fun. Contributions are very welcome (extend portability beyond Linux 2.6, replace MySQL daemon dependency with a lighter & embeddable transactional storage, etc). For now, it has been manually confirmed to run Plone and ERP5. Of course, to get the best out of NEO, a Zope application (or ZODB-based application) needs to be designed in a way taking advantage of back-end parallelism (much in the same way that a single-process application cannot take advantage of SMP). We wrote a presentation[3] out of our experience with ERP5 scalability testing & improvement, which might be an interesting read for people developing on the Zope framework. It describes what was the most common mistakes we corrected, and tools we developed to further extend scalability at various levels (NEO being the latest). And for most productions system, ZEO is really great. We have for example used ZEO for now more than 2 years to operate a Central Bank ERP with 300 concurrent users and ZEO never crashed. [1] http://www.neoppod.org/ [2] http://acsd-petrinets2010.di.uminho.pt/ [3] http://www.myerp5.com/kb/enterprise-High.Performance.Zope/view Note: If this mail would fit another list better, please advise. Regards, -- Vincent Pelletier

3 5

Zope Tests: 6 OK, 1 Failed
by Zope Tests Summarizer 07 Apr '10

07 Apr '10

Summary of messages to the zope-tests list. Period Tue Apr 6 12:00:00 2010 UTC to Wed Apr 7 12:00:00 2010 UTC. There were 7 messages: 6 from Zope Tests, 1 from ct at gocept.com. Test failures ------------- Subject: FAILED: Repository policy check found errors in 707 projects From: ct at gocept.com Date: Tue Apr 6 21:42:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013876.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 6 21:29:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013870.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Apr 6 21:31:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013871.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Apr 6 21:33:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013872.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Apr 6 21:35:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013873.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Apr 6 21:37:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013874.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Apr 6 21:39:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013875.html

1 0

z3c.form radio widget question
by Wichert Akkerman 07 Apr '10

07 Apr '10

I am wondering why the z3c.form radio widget appends :list to the names of the generated input elements. Since a radio list can never have more than one option selected I can't see any reason to do that. Does anyone know this is done? Wichert.

1 0

Summary of this week's IRC meeting (2010-04-06)
by Tres Seaver 06 Apr '10

06 Apr '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am attaching this week's summary. 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku7XikACgkQ+gerLs4ltQ7dqgCgkbMWiQU3QVtidL19Vi+rkPnr /voAn2FL6c/mJPZGWW0Deq/pq5j42Jk7 =9P6u -----END PGP SIGNATURE----- ============================= Weekly Zope developer meeting ============================= This is the summary of the weekly Zope developer meeting which happened on Tuesday, 2010-04-06 on #zope(a)irc.freenode.org from 3pm to 3:30pm (UTC). The agenda for this meeting is available in the mailing list archives: https://mail.zope.org/pipermail/zope-dev/2010-April/039981.html The IRC logs are located here: http://zope3.pov.lt/irclogs-zope/%23zope.2010-04-06.log.html#t2010-04-06T18… Tres Seaver was filling in for Christian Theune as conventer due to illness. Zope2 release manager --------------------- The community welcomes Hanno Schlichting as the new release manager for Zope2. In addition to closing / responding to dozens of bugs in the past week, Hanno has also proposed a roadmap for Zope 2.13 and has made the release tag for Zope 2.12.4. Porting packages to Zope3 ------------------------- Lennart Regebro reported that he has branches waiting for the first three "most depended-on" ZTK packages (``zope.event``, ``zope.interface``, and ``zope.testing``). After considering naming the new releases ``4.0``, the consensus was to just name them the next "normal" major release, as long as there are no backward-incompatible API changes. Some discussion of the general problem of doctests breaking due to exception formatting led to a suggestion from Jim Fulton that we implement a testing API similar the ``unittest.TestCase.assertRaises``, but with the additional feature that it returns the exception value, to permit further assertions about the state of that object. Buildbots --------- No one had new updates on the topic. Sidnei da Silva reported that he is close to reconstructing the script used to build ``win64`` images for Amazon EC. Tres Seaver reported that his request to Microsoft for dontaed VisualStudio licnese to support builds / tests of ``zope.*`` packages on Windows for Python 2.4 and 2.5 is still stalled. Baiju M noted that Rackspace can also support Windows in its cloud: http://www.rackspacecloud.com/ . Tracker status -------------- Charlie Clark reported that he had gotten his script for checking Launchpad for "languishing" bugs working. He posted that package to ``zope-dev(a)zope.org`` during the meeting. Bug Days -------- After some discussion, Adam Groszer and Baiju M agreed to widen their planned ``bluebream`` sprint to include more general ZTK issues. The sprint, originally set for Saturday, 2010-04-10, was rescheduled to Saturday, 2010-04-24. Charlie Clark asked for announcments, plus volunteers willing to help mentor new exterminators during the bug day. Adam and Baiju will organize a web page for coordinating the bug day activity, and send out the announcements. Carried Over ------------ - Resurrecting the "sprint schedule" page, http://wiki.zope.org/zope3/SprintSchedule - A more general calendar (e.g., for Zope / Python related conferences, symposia, sprints, etc.)

3 2