- Zope-Dev - Zope lists

[PATCH] Better error support in subunit output formatter
by Jonathan Lange 11 Apr '10

11 Apr '10

Hello, The subunit output formatter that was added recently currently raises NotImplementedError when it's given a generic "error". The error() method on formatters is used to communicate user error (e.g. when the user selects incompatible options), internal framework errors (afaict, only when there's a subprocess read error) and layer setUp errors. I find the idea of masking layer setUp errors to be unconscionably awful, so I've attached the following patch, which changes the subunit formatter's error() method to print out whatever it gets. It doesn't have any tests, but it's simple enough, and none of the other formatters have tests for this method either. Ideally, I think there should be a new method on OutputFormatter to handle layer setup failure. Probably teardown failure too. If someone wants to push back on this simple patch in favour of a new method, I could probably be persuaded to do the work, provided I had clear backwards compatibility guidelines. jml

2 4

[PATCH] zope.app.testing: Use doctest instead of deprecated zope.testing.doctest
by Jonathan Lange 10 Apr '10

10 Apr '10

Hello, Recent versions of zope.testing deprecate the zope.testing.doctest module in favour of the standard library's doctest module. zope.app.testing currently uses zope.testing.doctest for its tests and to provide its functional testing features. This patch changes it to use standard library doctest. The patch also deletes a repeated import line from zope.app.testing.functional, caught thanks to pyflakes. jml

1 0

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

10 Apr '10

Summary of messages to the zope-tests list. Period Fri Apr 9 12:00:00 2010 UTC to Sat Apr 10 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 677 projects From: ct at gocept.com Date: Fri Apr 9 21:09:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013890.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 9 21:29:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013891.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Apr 9 21:31:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013892.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Apr 9 21:33:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013893.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Apr 9 21:35:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013894.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Apr 9 21:37:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013895.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Apr 9 21:39:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013896.html

1 0

Stacking zope.component registries
by Martin Aspeli 09 Apr '10

09 Apr '10

Hi, I'd like to come up with a way to set up a test fixture that does the component registry equivalent of stackable DemoStorage's: whilst a layer is in effect, calls to provideAdapter() and friends (and ZCML execution) go into a global registry that is stacked on top of the default global one. On layer tear-down, the registry is popped, leaving the original (or previous) global registry intact. In zope.component.globalregistry, I see: def provideUtility(component, provides=None, name=u''): base.registerUtility(component, provides, name, event=False) base is a module-level variable of type BaseGlobalComponents(). I guess there'd be a way to use __bases__ to create this kind of stack, but I'm not clear on the details, and in particular whether this would really work with provideAdapter() and the rest of the (test-oriented) Python API. Martin

4 12

Summary of this weeks' meeting
by Jan Smith 09 Apr '10

09 Apr '10

Hi Christian, > From: Christian Theune <ct(a)gocept.com> > To: zope-dev(a)zope.org > Date: Wed, 31 Mar 2010 17:16:38 +0200 > Subject: [Zope-dev] Summary of this weeks' meeting (2010-03-30) > Hi, > > here's this week's summary. > > For those of you who can't/don't participate in those meetings, there's the open > question about how useful you consider my summaries to be. Please tell! Your summaries are extremely useful for people on the other side of the planet. The irc meetings are held at 3pm UTC - this is sleeping time for most of us downunder and means it's difficult to participate. I've published the irc meeting summaries on the Australian OzZope site - it also has an rss feed available. http://www.ozzope.org/weekly-zope-development-meeting Jan Smith http://www.ozzope.org/ > > Also in short: we decided to keep going with the meetings, so I'd be happy to see you guys next week in #zope. (Hopefully without screwing up the time then.) > > 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 0 · fax +49 345 1229889 1 > Zope and Plone consulting and development >

3 2

Re: [Zope-dev] [Checkins] SVN: ZConfig/trunk/setup.py correct metadata: I really did write this.
by Fred Drake 09 Apr '10

09 Apr '10

On Fri, Apr 9, 2010 at 10:27 AM, Fred Drake <fdrake(a)gmail.com> wrote: > Setting the ZF as maintainer appears sufficient to appease the policy checker. Or not. The fixer script won't edit this, but the checker script will still whine about it. Changing the author to the ZF really isn't a good thing; if anything, the maintainer (and maintainer_email!) should be set to the ZF (and zope-dev?). Changing the author doesn't really make sense, and is falsification for many packages (certainly for all those created before the ZF existed). -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 09 Apr '10

09 Apr '10

Summary of messages to the zope-tests list. Period Thu Apr 8 12:00:00 2010 UTC to Fri Apr 9 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 8 21:29:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013884.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Apr 8 21:31:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013885.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:33:36 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013886.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:35:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013887.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:37:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013888.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Apr 8 21:39:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-April/013889.html

1 0

[ann] BugDay 2010-04-24
by Adam GROSZER 09 Apr '10

09 Apr '10

Hello, As discussed at the weekly meeting, we're planning a BugDay. The wiki page is here: http://wiki.zope.org/bluebream/BugDaysList Don't wonder, we're planning it together with BB. Feel free to add your inputs. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: It is generally agreed that "Hello" is an appropriate greeting because if you entered a room and said "Goodbye," it could confuse a lot of people. - Dolph Sharp

2 1

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