- Zope-Dev - Zope lists

[Zope 2.8.2] Minor delay
by Andreas Jung 09 Oct '05

09 Oct '05

Hi, I originally scheduled Zope 2.8.2 for October 12th but I have to delay the release for some days (possibly one week) because of unforeseeable travel and a lot of important work. I hope this is fine for everyone. Andreas

2 3

default encoding used in ZPublisher.
by Chris Withers 08 Oct '05

08 Oct '05

Hi All, I'd like to backport the change I made to fix: http://www.zope.org/Collectors/Zope/1490 ...to the 2.8 branch, would anyone have any objections to this? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 6

Decoding of source for text/xml ZPTs
by Chris Withers 08 Oct '05

08 Oct '05

Hi All, During complication, the XML parser that processes non-HTML mode ZPT's decodes the string of the source into unicode instructions. In HTML mode, the parse does no decoding and so we get string instructions. My question as a result is: what characterset does the XML parser in non-HTML mode assume and can it be controlled in any way? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 1

New mailinglist for Zope 3 translators
by Philipp von Weitershausen 06 Oct '05

06 Oct '05

Hello all, [Sorry for the cross-post, please CC replies to zope3-i18n(a)zope.org only.] two months ago, I started an initiative [1] to translate Zope 3.1 using Ubuntu's Launchpad system [2]. Since then, I've received a lot of emails from numerous volunteers around the world and many of them made some excellent progress [3]. Thanks to everyone who contributed so far. A new mailinglist at zope3-i18n(a)zope.org will now help translators and developers like me to coordinate their work. For example, all those translations will have to be integrated back into the Zope 3.1 repository at some point which has to be coordinated somehow. Also, translators themselves will want to coordinate the work among them. The mailinglist will serve as a forum for discussing and coordinating things like that. So, if you're involved into Zope 3 translations OR if you would like to contribute something to Zope 3 by helping to translate it into your language, please subscribe to the new list [4]. If you have any questions, feel free to email me or even better the new list. Best regards Philipp [1] http://mail.zope.org/pipermail/zope3-dev/2005-August/015113.html [2] https://launchpad.net [3] https://launchpad.net/products/zope/+series/zope3.1/+pots/zope [4] http://mail.zope.org/mailman/listinfo/zope3-i18n

1 0

log levels
by Florent Guillaume 05 Oct '05

05 Oct '05

Now in Zope 2 trunk, more and more components use the standard python logging framework. For instance the transaction code logs at DEBUG level every transaction start and end (self.log.debug(...)). This makes the logs very verbose, and any other code I write that logs at DEBUG level gets drowned in it. Previously transaction logs were at TRACE level but this doesn't exist anymore, and the python logging framework doesn't have anything between INFO and DEBUG or below DEBUG. I don't have a solution really, I can log at level BLATHER and limit my logs at that, but that's not very satisfying. And if zLOG is deprecated I'd rather avoid it. Any idea? Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

2 1

Allowing @ in object ids
by Florent Guillaume 04 Oct '05

04 Oct '05

Today @ is forbidden in object ids. That's controlled by the bad_id regexp in OFS.ObjectManager, which tries to ensure that ids will be useable as URL components. However, there's no reason to disallow this, as the URL spec (http:// www.ietf.org/rfc/rfc1738.txt) says: An HTTP URL takes the form: http://<host>:<port>/<path>?<searchpart> [...] Within the <path> and <searchpart> components, "/", ";", "?" are reserved. The "/" character may be used within HTTP to designate a hierarchical structure. Note that somewhere else in the spec, it says that @ (and others) MAY be reserved by some schemes, but HTTP doesn't actually make it reserved. Furthermore, many projects have monkey-patched bad_id to allow @ and see no ill-effects. Having @ in ids is very useful for various things, one of them being to have email-like identifiers (think jabber for instance). There are other uses. Unless there's opposition, I'll change the code to allow it. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 1

Zope 2 trunk OFS tests failing
by Florent Guillaume 04 Oct '05

04 Oct '05

The OFS.testObjectManager tests are failing when run in isolation on the Zope 2 trunk (also on the 2.8 branch). Any idea? I'll look at it anyway, but if someone's seen this already... bin/zopectl test -v --libdir lib/python --dir lib/python/OFS testObjectManager ....E........F..... ====================================================================== ERROR: test_delObject_exception_debug_manager (OFS.tests.testObjectManager.ObjectManagerTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/fguillaume/zope/zope2/lib/python/OFS/tests/ testObjectManager.py", line 290, in test_delObject_exception_debug_manager om._delObject(ob.getId()) File "/Users/fguillaume/zope/zope2/lib/python/OFS/ ObjectManager.py", line 350, in _delObject if not getSecurityManager().getUser().has_role('Manager'): AttributeError: 'NoneType' object has no attribute 'has_role' ====================================================================== FAIL: test_setObject_set_owner_with_emergency_user (OFS.tests.testObjectManager.ObjectManagerTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/fguillaume/zope/zope2/lib/python/OFS/tests/ testObjectManager.py", line 104, in test_setObject_set_owner_with_emergency_user , om._setObject, 'should_fail', si ) File "/usr/local/lib/python2.3/unittest.py", line 295, in failUnlessRaises raise self.failureException, excName AssertionError: EmergencyUserCannotOwn ---------------------------------------------------------------------- Ran 19 tests in 0.077s Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

2 2

Can't fetch externals???
by Paul Winkler 30 Sep '05

30 Sep '05

I'm trying to fix a bug assigned to me, and for some reason I can use svn to make and check out my branch but it fails when fetching externals. Anybody else seen this? [pwinkler@dev-zope tmp]$ svn co svn+ssh://slinkp@svn.zope.org/repos/main/Zope/branches/slinkp-collector_1895 A slinkp-collector_1895/Extensions A slinkp-collector_1895/Extensions/README.txt A slinkp-collector_1895/log.ini A slinkp-collector_1895/configure A slinkp-collector_1895/doc .... (SNIP) .... A slinkp-collector_1895/skel/README.txt U slinkp-collector_1895 Checked out revision 38707. Fetching external item into slinkp-collector_1895/doc/ZEO svn: Connection refused svn: Can't connect to host 'svn.zope.org' And then I get the same thing if I do svn up: [pwinkler@dev-zope tmp]$ cd slinkp-collector_1895/ [pwinkler@dev-zope slinkp-collector_1895]$ svn up At revision 38707. Fetching external item into doc/ZEO svn: Connection refused svn: Can't connect to host 'svn.zope.org' -- Paul Winkler http://www.slinkp.com

4 9

problems setting up methods for a product that registers no classes
by Chris Withers 30 Sep '05

30 Sep '05

...zdb in this case. I need to make a "global recompile" function available, since zdb requires the co_filename attribute of the script's func_code object to be set to something meaningful, rather than the useless "Script (Python)" it usually gets set to. Once zdb is installed, any scripts editted will have this set, but I wanted to provide a utility method in a similar vein to python scripts' recompile function that could be globally accesed, however since zdb registers no classes, I ended up having to do some fairly horrific stuff, the following code is from zdb's __init__.py: # recompilation utlitity def initialize(context): # This horrificness is required because Zope doesn't understand the concept # of a Product that doesn't register any classes :-( pack=context._ProductContext__pack fd=getattr(pack, '__FactoryDispatcher__', None) if fd is None: class __FactoryDispatcher__(FactoryDispatcher): "Factory Dispatcher for a Specific Product" fd = pack.__FactoryDispatcher__ = __FactoryDispatcher__ if not hasattr(pack, '_m'): pack._m=fd.__dict__ pack._m['debug_compile'] = debug_compile pack._m['debug_compile__roles__'] = ('Manager',) Now, this breaks in 2.8, so what SHOULD I be doing to make a method globally available in a way that works in both 2.7 and 2.8? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

Strange security issue with Zope 2.8.1
by Jens Vagelpohl 30 Sep '05

30 Sep '05

I have found a strange security issue with Zope 2.8.1 that seems to stem from code not doing what it was supposed to do in Zope 2.7.x, but which works in 2.8.1 and then causes other side effects in code that relied on the broken behavior. Symptom: In Zope 2.8.1 it is *impossible* to override a ClassSecurityInfo security declaration in an Archetypes-derived content item. (I have a small set of unit tests that proves the behavior under Zope 2.8.1 if anyone is interested) A little background: When you register an Archetypes-derived content type, it will do all the generated accessor/setter method magic and then call InitializeClass a second time. The code in lib/python/App/class_init.py has changed between Zope 2.7.x and Zope 2.8 in order to support new-style classes. To be more precise, instead of manipulating the class __dict__ directly we now use setattr/delattr/etc. This change seems to have "un-broken" code which did not do what the code comments suggest. Namely, when a class is sent through class_init.default_class_init__ (better known as Globals.InitializeClass) the class __dict__ is searched to find objects that look like ClassSecurityInfo instances in order to read and apply the security settings. After finding the ClassSecurityInfo instance, it is force-deleted from the object (the comments say, "out of paranoia"). However, somehow this did not work correctly in Zope 2.7.x, where the deletion call looked like... del dict[key] (dict being the class __dict__, and key being the name of the ClassSecurityInfo instance). Under Zope 2.8, it looks like this: delattr(self, key) (self being the class object). Under Zope 2.7, the security object *would still be there* when hitting InitializeClass for the second time via Archetypes' registerType, which in turn meant Archetypes would not instantiate its own ClassSecurityInfo instance and stuff it with the declarations from whatever Archetypes-derived base class you used. In Zope 2.8, the deletion actually works as intended - but due to that fact Archetypes will instantiate its own ClassSecurityInfo and populate it with the declarations from the base class that I am trying to override. So the overridden settings are all overwritten again by the base class declaration. My question is, what is the reasoning behind deleting the ClassSecurityInfo object from the class after it has been read the first time? How can this be implemented in a sane way so that custom security declarations can be retained? jens

2 2