Zope-Dev March 2009

zope-dev@zope.dev

59 participants
104 discussions

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

20 Mar '09

Summary of messages to the zope-tests list. Period Thu Mar 19 12:00:00 2009 UTC to Fri Mar 20 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 Mar 19 21:29:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011301.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Mar 19 21:31:58 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011302.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu Mar 19 21:33:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011303.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu Mar 19 21:35:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011304.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu Mar 19 21:37:59 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011305.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu Mar 19 21:40:05 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011306.html

1 0

Proposal: refactoring of zope.app.security
by Dan Korostelev 20 Mar '09

20 Mar '09

Hi people! One of most large packages that really wants to be refactored but still wasn't touched is zope.app.security. It has much in it and it brings many dependencies, including zope.app.form and company. And even some zope.* packages, like zope.securitypolicy still depend on it. So, let's finally refactor it :) Here's a sketch of a refactoring plan I wrote after taking a quick look at the current package: - Move IAuthentication and other interfaces into new zope.authentication package. Also move there PrincipalSource and the "checkPrincipal" utility function. Also move there the PrincipalTerms class, however that will add dependency on zope.browser (which is really really tiny, as you may know). - Move global principal registry, its IPrincipal/IGroup implementations and its directives into new zope.principalregistry package. - Move LocalPermission into new zope.localpermission package. I personally didn't ever need local permissions. - Rewrite PermissionsVocabulary and PermissionIdsVocabulary not to depend on zope.app.component and move them into zope.security. It's generally useful there and won't introduce any new dependencies. - Move zcml definition of zope.Public permission. Maybe move security declaration for the `zope.security.permission.Permission` class as well. - Leave all browser views, globalmodules.zcml, _protections.zcml, other zope.* permission definitions in zope.app.security as well as backward-compatibility imports. - Just to note: the "settings" module was recently moved to zope.securitypolicy as there's the right place for it. Not sure about: - ILoginPassword and its basic implementations. The interface should probably go into zope.authentication while implementations - into zope.publisher. It will add a dependency on zope.authentication to zope.publisher, but the zope.authentication are expected to be really tiny and already installed for most applications, so I believe that it's okay. - PrincipalLogging - the adapter from zope.security.interfaces.IPrincipal to zope.publisher.interfaces.ILoggingInfo. I'd just move it into zope.publisher, because it's already tied to zope.security. - ILogoutSupported flag interface/adapter. Looks like it's only ever used for enabling/disabling the "logout" button in the UI. I'd deprecate it and leave in zope.app.security. - _protections.py module. It defines a NoProxy checker for zope.i18nmessageid.Message and adds __name__ and __parent__ attributes to _available_by_default. This module was executed in zope.app.security.__init__ and generally does useful things for most of applications. The problem is that neither zope.i18nmessage, nor zope.location already depend on zope.security. One solution is to move the protections in that packages, placing the code into "try/except ImportError" block to avoid hard dependency. -- WBR, Dan Korostelev

5 18

ContainerOrderModifiedEvent
by Alan Runyan 19 Mar '09

19 Mar '09

It looks like zope.container.contained.notifyContainerModified is the event that is sent when *any* container modification occurs. Maybe this is too coarse grain? I would like to be able to differentiate when Ordering changes take place on a container. Are there any complaints against having ordering signal a more specific event? i.e. ContainerOrderModifiedEvent? It would inherient from ContainerModifiedEvent. specifically in: - zope.container.ordered.updateOrder - OFS.Folder.OrderSupport The problem is that it is very difficult to know if the Order has changed vs. some other container attribute has been changed. -- Alan Runyan Enfold Systems, Inc. http://www.enfoldsystems.com/ phone: +1.713.942.2377x111 fax: +1.832.201.8856

1 0

Reminder: Zope Foundation General meeting in less than one hour!
by Martijn Faassen 19 Mar '09

19 Mar '09

Hi Zope Foundation member, At 17:00 UTC, less than an hour from now as I write this, we will have the general meeting of the Zope Foundation. We'd of course like to meet the quorum for this meeting, so we kindly request all members to show up on the #zope-foundation channel. irc://irc.freenode.net/#zope-foundation Hope to see you all there! Martijn

1 0

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

19 Mar '09

Summary of messages to the zope-tests list. Period Wed Mar 18 12:00:00 2009 UTC to Thu Mar 19 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 Mar 18 21:25:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011295.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 18 21:27:34 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011296.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 18 21:29:35 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011297.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Mar 18 21:31:35 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011298.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Mar 18 21:33:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011299.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Mar 18 21:35:36 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011300.html

1 0

zope.password
by Roger Ineichen 19 Mar '09

19 Mar '09

Hi steering group and Dan During update z3c.authenticator and replace the password with the new zope.apssword implementation, I saw that the vocabulary "Passsword Manager Names" is not available in the zope.password package. I think the password package should also provide this vocabulary. Or at least the zope.app.authentication package should not configure that. Do you see any solution to solve that problem that not both package zope.app.authentication and z3c.authenticator configure that utility within the same name (needs the exclude directive for make that working) Regards Roger Ineichen _____________________________ END OF MESSAGE

8 22

ZPT attributes and ""
by Malthe Borch 18 Mar '09

18 Mar '09

Currently, if an attribute expression evaluates to any value that's boolean False, it's omitted (e.g. 0, "", object()). I think that's unexpected. Instead, attributes should only be omitted when the expression evaluates to ``None``. How do folks feel about changing this behavior in ``zope.pagetemplate``. \malthe

6 12

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

18 Mar '09

Summary of messages to the zope-tests list. Period Tue Mar 17 12:00:00 2009 UTC to Wed Mar 18 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 Mar 17 21:23:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011289.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 17 21:25:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011290.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 17 21:27:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011291.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Mar 17 21:29:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011292.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Mar 17 21:31:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011293.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Mar 17 21:33:57 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011294.html

1 0

Re: [Zope-dev] SVN: zope.component/trunk/ Merge the 'tseaver-wo_zope_deferredimport' branch:
by Tres Seaver 18 Mar '09

18 Mar '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dan Korostelev wrote: > 2009/3/5 Tres Seaver <tseaver(a)palladion.com>: >> Log message for revision 97501: >> Merge the 'tseaver-wo_zope_deferredimport' branch: > > Great! Thank you! > >> - Added a pure-Python 'hookable' implementation, for use when >> 'zope.hookable' is not present. > > Can that pure-python implementation of zope.hookable be merged into > zope.hookable as a fallback to a C version if it's not available (like > it's done in zope.interface)? It probably could be (in fact, I prototyped it there first). However, it turns out that zope.hookable has effectively *no* clients beyond zope.component, which meant that I could lose the 'install_requires' dependency altogether by moving the pure-Python bits to zope.component. Thoughts, 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 iD8DBQFJrxua+gerLs4ltQ4RAnCJAJ490SAR690RcrSqc9BDGQh/9FrtIQCfXZ1r GNr3pgAVeNxJLjN9MWzYatk= =nVPS -----END PGP SIGNATURE-----

5 5

[zope.testbrowser] r84900
by Malthe Borch 18 Mar '09

18 Mar '09

Code snippet: >>> def open(self, url, data=None): >>> """See zope.testbrowser.interfaces.IBrowser""" >>> url = str(url) This string coercion is unfortunate, because ``mechanize`` accepts a (mechanize-) request-object in place of a URL string here. Using a custom request object allows us to do such things as setting the REQUEST_TYPE header string, which is not possible throught the standard API. Changeset comment: - Remove vendor import of mechanize. - Fix bug that caused HTTP exception tracebacks to differ between version 3.4.0 and 3.4.1. - Workaround for bug in Python Cookie.SimpleCookie when handling unicode strings. - Fix bug introduced in 3.4.1 that created incompatible tracebacks in doctests. This necessitated adding a patched mechanize to the source tree; patches have been sent to the mechanize project. Not sure which of the above this coercion is trying to solve, but perhaps it could be solved in a way that didn't break the mechanize functionality. \malthe

2 2

← Newer
1
2
3
4
5
6
7
...
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev March 2009