- Zope-Dev - Zope lists

Zope Tests: 6 OK
by Zope Tests Summarizer 24 Dec '09

24 Dec '09

Summary of messages to the zope-tests list. Period Wed Dec 23 12:00:00 2009 UTC to Thu Dec 24 12:00:00 2009 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: Wed Dec 23 20:37:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013251.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Dec 23 20:39:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013252.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 23 20:41:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013253.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 23 20:43:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013254.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 23 20:45:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013255.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 23 20:47:04 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013256.html

1 0

zope.testing.doctestunit and BBB
by Marius Gedminas 23 Dec '09

23 Dec '09

My app's buildbot went all red last night, because its config wants the latest zope.testing (for our developers' convenience), and the latest zope.testing release no longer ships its own copy of doctest.py, I guess: from zope.testing.doctestunit import DocTestSuite ImportError: cannot import name DocTestSuite Does anybody have any objections for a BBB import, making DocTestSuite available from the old location? I don't think breaking API is appropriate in a point-release (3.8.4), so I'd like to release 3.8.5 with that fixed. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development

6 16

Zope Tests: 6 OK
by Zope Tests Summarizer 23 Dec '09

23 Dec '09

Summary of messages to the zope-tests list. Period Tue Dec 22 12:00:00 2009 UTC to Wed Dec 23 12:00:00 2009 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: Tue Dec 22 20:37:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013245.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Dec 22 20:39:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013246.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 22 20:41:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013247.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 22 20:43:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013248.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 22 20:45:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013249.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 22 20:47:09 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013250.html

1 0

New release of zope.interface
by Fabio Tranchitella 23 Dec '09

23 Dec '09

I fixed the unit tests of the zope.interface package, which were broken by the last release of zope.testing. Can somebody make a release, or give me access to the PyPI package? My nickname is kobold. Best regards. Fabio

6 8

Testrunner option for running tests in random order?!?
by Christian Theune 23 Dec '09

23 Dec '09

Hi, I *thought* the test runner had a feature to run tests in randomized order, but I can't find it. Is that something that Zope 2 had and that was never ported to zope.testing? I couldn't find in the history either. /me is confused. -- 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

5 15

Zope2 and WSGI
by Hanno Schlichting 23 Dec '09

23 Dec '09

Hi Tres, I've seen you started some work on Zope2 and its WSGI publisher. This is awesome :) How does this relate to repoze.zope2? I'd love to have Zope2 actually support WSGI out-of-the-box. It should probably be based on either a simplified repoze.zope2 codebase or simply something that gets the job done. So what's your goal with this and is there any way I can help? Thanks, Hanno

5 6

Interfaces vs ZCA concepts
by Thomas Lotze 22 Dec '09

22 Dec '09

So we've decided to let interfaces grow `adapt` and `utility` methods. I've written a simple and straight-forward implementation of them (see the tlotze-component-API branches of zope.interface and zope.component) that is closely modelled on the exisiting `__call__`. In particular, the new methods use component hooks which are like adapter hooks but with a richer set of call parameters. There are a few tests for the new methods as well, so everything should be fine. Except that I don't like the implications now that I have actually written down the code. I'll describe the problem I see and then suggest an idea that I don't think we've been considering in the discussion two weeks ago: We're intentionally leaking the concept of utilities to zope.interface. Assuming we're entirely fine with this, we still need to decide how much of the particulars of the ZCA we want to bring along: named components, lookup contexts, the ComponentLookupError. My current implementation tries to introduce enough generic behaviour into the `adapt` and `utility` methods so that they don't cause too obvious (conceptual) dependencies of zope.interface on zope.component: * `adapt` and `utility` don't define particular optional arguments but pass all keyword parameters except for `default` to the component hook which, being implemented by zope.component, keeps the knowledge about named adapters and lookup contexts within the latter package. * The hook invokes the `query*` functions to play nice with any other component hooks and the interface methods raise a TypeError if all of them fail to find a component. However, the generic behaviour gets in our way: the method signatures become useless and hooks lose the possibility of raising useful exceptions. I've tried some variations but as long as the `adapt` and `utility` methods are actually implemented by zope.interface, it will always come down to a compromise that either renders the new methods unusable with anything that's not very much like zope.component, or makes for a half-hearted copy of the functionality we currently have in the zope.component API. I discussed this a bit with Wolfgang as we both don't like this kind of compromise in such core functionality. We came up with the idea that a clean solution would be to keep any implementation of the two methods out of zope.interface and rather inject them into the interface API by code kept entirely within zope.component. We do realise how close to the concept of monkey-patching this comes, but maybe it wouldn't be so bad if we could do it in a more structured way (being intentionally vague here yet). In particular, keeping the concrete `adapt` and `utility` methods out of the core implementation of interfaces would address the concern raised by somebody on this list that we were going to tailor zope.interface too much to the needs of the Zope ecosystem. Uses of interfaces other than adaptation and component lookup could get convenience methods registered by the same mechanism zope.component would end up employing, which is a big conceptual advantage from my point of view. What do people think of this? -- Thomas

15 65

zope.schema
by Godefroid Chapelle 22 Dec '09

22 Dec '09

Hi, Jean-Francois and I made a few improvements to zope.schema. Would it be possible to get a new release ? Or to give us access on Pypi so that we can make it ourselves ? Thanks -- Godefroid Chapelle (aka __gotcha) http://bubblenet.be

2 7

Removing dependency between zope.location and zope.copy
by Fabio Tranchitella 22 Dec '09

22 Dec '09

Hello, I'm wondering if it would be possible to drop the dependency between zope.location and zope.copy. It makes sense to me because zope.location depends on zope.copy only because it registers a LocationCopyHook, not because it is really using anything from that package. Attached to this message you can find my (proposed) patch to remove the dependency making the adapter registration optional, and informing the developer that zope.copy is needed is he is importing directly the zope.location.pickling module. Comments? Thanks, Fabio

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 22 Dec '09

22 Dec '09

Summary of messages to the zope-tests list. Period Mon Dec 21 12:00:00 2009 UTC to Tue Dec 22 12:00:00 2009 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: Mon Dec 21 20:37:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013239.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Dec 21 20:39:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013240.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 21 20:41:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013241.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 21 20:43:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013242.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 21 20:45:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013243.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 21 20:47:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013244.html

1 0