- Zope-Dev - Zope lists

Need help
by Roopesh P Raj 01 Dec '09

01 Dec '09

I have to use a logging framework in my zope product. The logging framework makes it mandatory to use the same object instance to fire various logging calls (like log start, log end). I want to store the object instance somewhere so that I can use it from any module in my zope product. I tried to store it in context._ProductContext__app. There are two patch classes of httprequest and httpresponse inside which the context is not available. How do I do this in Zope-2.8.8 Thanks Roopesh

2 1

Object schema field validation
by Markus Kemmerling 01 Dec '09

01 Dec '09

I stumbled upon a problem with Object schema field validation. The problem occurs, e.g., if the the Object field's schema itself contains a Choice field with a dynamically computed vocabulary. For the latter to validate correctly the field must be bound to the instance. But the Object field validation code in zope.schema._fields._validate_fields validates the attributes of the Object field instance without binding them first: def _validate_fields(schema, value, errors=None): ... try: attribute = schema[name] if IField.providedBy(attribute): # validate attributes that are fields attribute.validate(getattr(value, name)) except ValidationError, error: ... Replacing the line attribute.validate(getattr(value, name)) with field = attribute.bind(value) field.validate(getattr(value, name)) fixes the problem. Looks like a bug to me. Regards, Markus Kemmerling

2 1

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

01 Dec '09

Summary of messages to the zope-tests list. Period Mon Nov 30 12:00:00 2009 UTC to Tue Dec 1 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 Nov 30 20:38:25 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013113.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Nov 30 20:40:25 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013114.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Nov 30 20:42:25 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013115.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Nov 30 20:44:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013116.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Nov 30 20:46:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013117.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Nov 30 20:48:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013118.html

1 0

Proposal: zope.app.publisher refactoring
by Dan Korostelev 30 Nov '09

30 Nov '09

Hi all. I think it's time to clean the mess in the zope.app.publisher package. Currently it contains many things that could be moved into separate packages or merged with base zope packages. So here's a sketch plan about where to move things: Menu mechanism (the browser:menuItem directive and friends) - move this to the new "zope.browsermenu" package. This should be easy as nothing else in zope.app.publisher seem to depend on menus. Browser view directives (browser:page and friends) - move this to some "zope.browserpage" package and make its structure more clean, so people could understand the magic of browser page class generation. :-) BrowserSkinsVocabulary - this can be moved to zope.publisher.browser and rewritten with zope.schema's SimpleVocabulary not to introduce dependency on zope.componentvocabulary. ManagementViewSelector (the @@SelectedManagementView.html view) - leave it there as is. Resource mechanism (files, directories, etc.) - probably the most complicated code, but it should be easy to move it to the new "zope.browserresource" package. One problem is with PageTemplateResource that introduces a dependency on zope.pagetemplate. It should probably moved to another package, like "zope.ptresource" and made dependent on z3c.ptcompat to support chameleon engine. ModifiableBrowserLanguages implementation - move to zope.publisher.browser. It's the useful thing that won't introduce any new dependencies. "date" fieldconverter - I don't think anyone uses it, I'd leave it there as is and forget about it :) http.zcml - this file contains security declarations for zope.publisher's HTTP-related classes. move them to zope.publisher. xmlprc - move the IXMLRPCView interface and XMLRPCView base class to zope.publisher as a counterpart to zope.publisher.browser.BrowserView. Move MethodPublisher, MethodTraverser, xmlrpc:view ZCML directive to new "zope.xmlrpcview" package. Also I'd merge MethodTraverser with MethodPublisher to make it easier to understand and to decrease number of entities :) IXMLRPCPublisher adapters for zope.container - move them to zope.container. The IBrowserPublisher adapters that are already there, so it won't make things worser. The zope.container package may be refactored later to break dependency on zope.publisher though. IHTTPView and IFTPView interfaces - move that into zope.publisher as a counterpart to IBrowserView. (BTW, shouldn't IBrowserView be a subclass of IHTTPView?) IFTPDirectoryPublisher interface - not sure what's this and where is it used. Probably should be moved to zope.publisher.interfaces.ftp as well. ILogin, ILogout from zope.app.publisher.interfaces.http - looks like these don't really mean anything and are used only in zope.app.security. I'd move them to zope.app.security even without BBB imports (not to make zope.app.publisher dependent on zope.app.security), but maybe I just don't know something about them? :) That's all for now. I'd like to see some comments/propositions/objections before I start. Also, maybe there are more beautiful names for new packages? After refactorings it will be much easier to clean and develop features that are currently provided by zope.app.publisher. For instance I'd like to try to simplify browser resources code somewhat, but it's for another proposal :) -- WBR, Dan Korostelev

8 23

Zope Tests: 6 OK
by Zope Tests Summarizer 30 Nov '09

30 Nov '09

Summary of messages to the zope-tests list. Period Sun Nov 29 12:00:00 2009 UTC to Mon Nov 30 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: Sun Nov 29 20:38:22 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013107.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Nov 29 20:40:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013108.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Nov 29 20:42:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013109.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Nov 29 20:44:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013110.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Nov 29 20:46:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013111.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Nov 29 20:48:23 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013112.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 29 Nov '09

29 Nov '09

Summary of messages to the zope-tests list. Period Sat Nov 28 12:00:00 2009 UTC to Sun Nov 29 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: Sat Nov 28 20:39:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013101.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Nov 28 20:41:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013102.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Nov 28 20:43:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013103.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Nov 28 20:45:31 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013104.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Nov 28 20:47:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013105.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Nov 28 20:49:32 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013106.html

1 0

make zope.component.registry.Components inherit from dict?
by Chris McDonough 28 Nov '09

28 Nov '09

We've been handling some constructive criticisms from repoze.bfg developers with respect to verbosity resulting from use of unnamed utility registrations in a component architecture registry. These criticisms, and our ameliorations are detailed here: <http://docs.repoze.org/bfg/1.1/designdefense.html#bfg-uses-the-zope-compone…> In repoze.bfg, we've actually decided to use a subclass of the component registry which also inherits from "dict". This makes it possible to spell common unnamed "utility" registrations and lookups as: utility = SomeUtilityImplementation() registry['someutility'] = utility someutility = registry['someutility'] Instead of the more familiar: class ISomeUtility(Interface): pass utility = SomeUtilityImplementation() registry.registerUtility(utility, ISomeUtility) Doing this was extremely simple. Here's the "meat" of the subclass: from zope.component.registry import Components class Registry(Components, dict): pass I think it would be reasonable to make this change in zope.component itself. Dissenters? - C

10 39

Zope Tests: 6 OK
by Zope Tests Summarizer 28 Nov '09

28 Nov '09

Summary of messages to the zope-tests list. Period Fri Nov 27 12:00:00 2009 UTC to Sat Nov 28 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: Fri Nov 27 20:38:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013095.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Nov 27 20:40:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013096.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Nov 27 20:42:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013097.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Nov 27 20:44:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013098.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Nov 27 20:46:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013099.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Nov 27 20:48:38 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013100.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 27 Nov '09

27 Nov '09

Summary of messages to the zope-tests list. Period Thu Nov 26 12:00:00 2009 UTC to Fri Nov 27 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: Thu Nov 26 20:38:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013089.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Nov 26 20:40:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013090.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Nov 26 20:42:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013091.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Nov 26 20:44:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013092.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Nov 26 20:46:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013093.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Nov 26 20:48:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-November/013094.html

1 0

z3c.schema2xml and z3c.schema2json
by Jan-Wijbrand Kolman 26 Nov '09

26 Nov '09

Hi, I'm about to work a bit on z3c.schema2json [1]. As has been briefly discussed before (a while ago [2]), z3c. schema2json is so similar to z3c.schema2xml [3] in what it does and how it does it, that I wonder about merging the two packages somehow. One way to do this - maybe - is to use named registrations for the (de)serialization adapters. The name could reflect the serialization "mode" - for example "xml" or "json". But maybe there're other ideas to achieve this? Or, could it be that merging has no real benefit? regards, jw [1] http://svn.zope.org/Sandbox/paulwilson/z3c.schema2json/ [2] https://mail.zope.org/pipermail/zope-dev/2009-June/037091.html [3] http://svn.zope.org/z3c.schema2xml/

3 2