March 2009 - Zope-Dev

Common permissions (final bits of zope.app.security refactoring)
by Dan Korostelev 25 Mar '09

25 Mar '09

Hey, people! The refactoring of zope.app.security is now almost done. There's still some polishing work to do and two little issues to resolve. One of them is the zope's "common permissions". Most of zope.* and zope.app.* (and other) packages define some security protections for their classes and views using common permission names defined in zope.app.security. We decided to move those permission definitions to a separate and excludable/overridable zcml file to zope.security, so packages that use them would't need to install anything additional. But we want only generic and useful permissions to be a part of "common set", so we need to select ones from zope.app.security. Currently, zope.app.security defines these permissions (not counting zope.Public, that already migrated to zope.security): - zope.View - zope.Security - zope.ManageContent - zope.ManageBindings - zope.ManageCode - zope.ManageServices - zope.ManageSite - zope.ManagePrincipals - zope.ManageApplication Permissions, that needs to be in a common set (IMHO), mostly because it's used by current zope.* packages: - zope.View - zope.ManageContent - zope.Security - zope.ManageServices - zope.ManageSite To be honest, I don't quite get the difference between zope.ManageSite and zope.ManageServices. Can someone clear this point for me? May be they should be merged somehow. Permissions that can stay in zope.app.security, and reasons: - zope.ManageBindings - What's that? I can't find any usage of it. - zope.ManagePrincipals - That looks like it was intended for something like zope.app.authentication, but zope.ManageServices is used there instead. - zope.ManageCode - I guess it's intended for TTW development that's not used/developed much and even discouraged now-a-days? If so, I believe that it can stay in zope.app.security. - zope.ManageApplication - Looks like it's intended for and used mostly in "zope.app.applicationcontrol" which has more to do with "zope3, the application server", than the "zope.framework". -- WBR, Dan Korostelev

3 3

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

24 Mar '09

Summary of messages to the zope-tests list. Period Mon Mar 23 12:00:00 2009 UTC to Tue Mar 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: Mon Mar 23 21:26:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011325.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Mar 23 21:28:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011326.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Mar 23 21:30:38 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011327.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Mar 23 21:32:39 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011328.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Mar 23 21:34:40 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011329.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Mar 23 21:36:41 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011330.html

1 0

z3c.form render & traversal bug?
by Nick Bower 24 Mar '09

24 Mar '09

In trying to work out how to traverse from a z3c.form Form for a simple scenario, I've uncovered something a little confusing with the Form code. In my case the user specifies search criteria then gets a results page. I am doing the following; from z3c.form import form from zope.app.pagetemplate.viewpagetemplatefile import ViewPageTemplateFile class SearchForm(form.Form): # usual stuff fields=... def @handleSearch(self, action): # process criteria and setup for displaying results ... self.template = ViewPageTemplateFile('www/results.pt') Which breaks because of BaseForm's render() method (see comments): def render(self): '''See interfaces.IForm''' # render content template if self.template is None: template = zope.component.getMultiAdapter((self, self.request), IPageTemplate) return template(self) # ** displays ok default edit form return self.template() # ** breaks results page no instance Should the last line be self.template(self) because ViewPageTemplateFile.__call__(self, instance, *args **kw) requires a single mandatory argument? Although ViewPageTemplateFile requires an argument, IPageTemplate doesn't mandate it so I'm wondering if there were other adapters the code's author had in mind when doing this. It seems a little inconsistent to a zope3 novice anyway.

1 0

Question: additional context for IAnnotations adapter?
by Dan Korostelev 23 Mar '09

23 Mar '09

Hi there! While looking at the zope.app.principalannotation package, I discovered that both zope.annotation and zope.app.principalannotation register their IAnnotations adapters twice: fisrt, as a simple adapter and second, as a multi adapter for some additional context object. The zope.annotation doesn't use that additional context at all - it just allows to get annnotations by multi-adapter lookup. The zope.app.principalannotation uses the additional context object as context argument for getSiteManager, which I believe is not needed and/or used in most cases, because application components, like zope.site provide their hooks to get the right site manager. There's no documentation or any tests for that behaviour neither in zope.app.principalannotation, nor in zope.annotation, so I made an assumption that these registrations are there just to support some very old annotation pattern, that was deprecated ages ago. If it's like that, I'd like to remove that registration for zope.principalannotation that is about to born as well as for zope.annotation. Can someone clarify this point? -- WBR, Dan Korostelev

4 7

Windows binary egg for zope.interface 3.5.1?
by Chris Withers 23 Mar '09

23 Mar '09

Hi All (maybe just Jim? ;-) ), Just did a buildout involving zope.interface and got: Getting distribution for 'zope.interface'. ******************************************************************************** WARNING: An optional code optimization (C extension) could not be compiled. Optimizations for this package will not be available! Python was built with Visual Studio 2003; extensions must be built with a compiler than can generate compatible binaries. Visual Studio 2003 was not found on this system. If you have Cygwin installed, you can try compiling with MingW32, by passing "-c mingw32" to setup.py. ******************************************************************************** Got zope.interface 3.5.1. Any chance someone could roll and release a Windows binary egg for this? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

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

23 Mar '09

Summary of messages to the zope-tests list. Period Sun Mar 22 12:00:00 2009 UTC to Mon Mar 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: Sun Mar 22 21:24:15 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011319.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Mar 22 21:26:18 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011320.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sun Mar 22 21:28:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011321.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sun Mar 22 21:30:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011322.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sun Mar 22 21:32:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011323.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sun Mar 22 21:34:22 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011324.html

1 0

Re: [Zope-dev] SVN: zc.buildout/trunk/ Switched from using os.popen* to subprocess.Popen
by Tres Seaver 23 Mar '09

23 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam GROSZER wrote: > close_fds=True is not supported on win32. I see that described here: http://docs.python.org/library/subprocess.html#using-the-subprocess-module I thought somebody else already took out the 'close_fds' bit. > The biggest problem is that after making it False on win32 still > breaks seemingly all doctests using system(). > The output seemingly matches exactly the expected output, but the > tests burps on it. Sorry, no clue. 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 iD8DBQFJx26r+gerLs4ltQ4RAgDkAKC6GQHe+q4N7gRokjmlaTb4LUt/SwCgsMMn KB6PMWDgqr4DWAKEt0bmW5g= =WGOY -----END PGP SIGNATURE-----

1 0

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

22 Mar '09

Summary of messages to the zope-tests list. Period Sat Mar 21 12:00:00 2009 UTC to Sun Mar 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: Sat Mar 21 21:22:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011313.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 21 21:24:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011314.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 21 21:26:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011315.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 21 21:28:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011316.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 21 21:30:08 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011317.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 21 21:32:09 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011318.html

1 0

zope.site
by Dan Korostelev 21 Mar '09

21 Mar '09

Please, can someone review the current zope.site's trunk? It fails the "persistent_interfaces" tests. I didn't ever work with persistent code, so I don't have idea about what's going on. But I'd like to make a release of this package. Anyone? -- WBR, Dan Korostelev

2 3

Zope Tests: 6 OK
by Zope Tests Summarizer 21 Mar '09

21 Mar '09

Summary of messages to the zope-tests list. Period Fri Mar 20 12:00:00 2009 UTC to Sat Mar 21 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 Mar 20 21:24:24 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011307.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Mar 20 21:26:27 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011308.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri Mar 20 21:28:28 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011309.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri Mar 20 21:30:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011310.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri Mar 20 21:32:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011311.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri Mar 20 21:34:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011312.html

1 0