May 2009 - Zope-Dev - Zope lists

zc.relationship - can't pickle module objects
by Martin Aspeli 09 Nov '09

09 Nov '09

Hi, I *think* this is a bug in zc.relationship, but I'm not quite sure. I'm using ZODB3 3.8.1 (to get BLOB support) and trying to install plone.app.relations, which depends on zc.relationship 1.0.2. In particular, it subclasses zc.relationship.shared.Container, and stores a zc.relationship.index.Index object in self.relationIndex. Now, the __init__ of zc.relationship.index.Index, which derives from Persistent, contains the code below. In self._relTools and and self._attrs, there are a pile of modules, types and functions being stored. I think these are causing the ZODB to barf. Interestingly, with whatever version of ZODB that comes with Zope 2.10 (3.7?), there's no problem. Any ideas how to work around this, or even why it's a problem in one version of the ZODB but not another? zc.relationship.index.Index's initialiser: def __init__(self, attrs, defaultTransitiveQueriesFactory=None, dumpRel=generateToken, loadRel=resolveToken, relFamily=IFBTree, deactivateSets=False): self._name_TO_mapping = OOBTree.OOBTree() # held mappings are objtoken to (relcount, relset) self._EMPTY_name_TO_relcount_relset = OOBTree.OOBTree() self._reltoken_name_TO_objtokenset = OOBTree.OOBTree() self.defaultTransitiveQueriesFactory = defaultTransitiveQueriesFactory self._relTools = getModuleTools(relFamily) self._relTools['load'] = loadRel self._relTools['dump'] = dumpRel self._relLength = Length.Length() self._relTokens = self._relTools['TreeSet']() self.deactivateSets = deactivateSets self._attrs = _attrs = {} # this is private, and it's not expected to # mutate after this initial setting. seen = set() for data in attrs: # see README.txt for description of attrs. if zope.interface.interfaces.IElement.providedBy(data): data = {'element': data} res = getModuleTools(data.get('btree', IFBTree)) res['element'] = val = data['element'] res['attrname'] = val.__name__ res['name'] = data.get('name', res['attrname']) if res['name'] in _attrs or val in seen: raise ValueError('Duplicate in attrs', name, val) seen.add(val) _attrs[res['name']] = res res['dump'] = data.get('dump', generateToken) res['load'] = data.get('load', resolveToken) if (res['dump'] is None) ^ (res['load'] is None): raise ValueError( "either both of 'dump' and 'load' must be None, or neither") # when both load and dump are None, this is a small # optimization that can be a large optimization if the returned # value is one of the main four options of the selected btree # family (BTree, TreeSet, Set, Bucket). res['interface'] = val.interface res['multiple'] = data.get('multiple', False) res['call'] = zope.interface.interfaces.IMethod.providedBy(val) if res['TreeSet'].__name__.startswith('I'): Mapping = IOBTree.IOBTree else: assert res['TreeSet'].__name__.startswith('O') Mapping = OOBTree.OOBTree self._name_TO_mapping[res['name']] = Mapping() # these are objtoken to (relcount, relset) Regards, Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 15

zope.testrunner import location notifications
by Martijn Faassen 23 Jun '09

23 Jun '09

Hi there, (in particular Christian Theune) What's the status of the 'import location' notification functionality in zope.testrunner? What's the status of the ZODB migration code? Regards, Martijn

2 3

RFC: Site -> Locus
by Martijn Faassen 05 Jun '09

05 Jun '09

Hi there, We have a concept of "Site" in the Zope Toolkit, along with SiteManager and the like. What this concept allows us to do is locally register components. Most typically this is used for local utilities such as a catalog. During traversal, a thread-local is set with the current site, so that code that looks up a compoment will check the current site(s) before falling back on the global component registry. The word "site" has bothered myself and others for some time. It doesn't really have the right connotations for random programmers; when you hear site you think about website, and that's not really what this implies. The reason we called it site I think has to do with the idea that we expected Zope-based web sites to be applications with a lot of local components. I'm interested in refactoring zope.site to split it into two packages: one that has the pure site-based logic with minimal dependencies, and support to easily test with sites, and the other with dependencies on zope.container. While thinking about this, I figured this might be a good opportunity to rename the word 'site' to something better. I propose we use the word 'Locus' instead of 'Site'. This word doesn't have a lot of connotations in the web programming world, and people can guess by simply looking at the word it might have something to do with *local* components. It's also short. It's also a synonym of the word site. The dictionary says: "a place, a locality" and "the scene of any event or action". I think that works quite well. Two possible options for moving forward with this: * create a zope.locus package that contains the core locus support. It only speaks in terms of "locus" and doesn't use the word "site" * zope.locuscontainer will have the container support surrounding sites. * zope.site becomes a backwards compatible but deprecated package that does 'from .. import .. as' to keep 'getSite' and 'setSite' and such around. The package itself will be deprecated and people will be encouraged to depend on zope.locus (or zope.locuscontainer, but that will be rare). The other plan: * we fold the locus support into zope.component. This is assuming that the dependencies for Locus can be kept to a bare minimum (no ZODB dependencies either). * we add the LocusContainer support to zope.container directly; since it already uses zope.component this isn't a problem * zope.site is still a backwards compatible package (that depends on zope.container and zope.component, which it already does). The second plan is my favorite if it is possible dependency-wise and zope.component doesn't take on new dependencies. I think support for local components could very well be part of zope.component conceptually. It would allow us to eliminate one package (zope.site) without introducing any new packages (the other plan increases the amount of packages by one, trading zope.site for zope.locuscontainer). What do people think about: * the idea of renaming Site to Locus * the plan for refactoring? Regards, Martijn

15 42

Zope Tests: 8 OK
by Zope Tests Summarizer 31 May '09

31 May '09

Summary of messages to the zope-tests list. Period Sat May 30 12:00:00 2009 UTC to Sun May 31 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 30 20:50:29 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011827.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat May 30 20:52:31 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011828.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat May 30 20:54:31 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011829.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat May 30 20:56:31 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011830.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Sat May 30 20:58:31 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011831.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat May 30 21:00:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011832.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat May 30 21:02:32 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011833.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Sat May 30 21:04:33 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011834.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 30 May '09

30 May '09

Summary of messages to the zope-tests list. Period Fri May 29 12:00:00 2009 UTC to Sat May 30 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri May 29 20:49:41 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011819.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri May 29 20:51:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011820.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Fri May 29 20:53:46 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011821.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Fri May 29 20:55:48 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011822.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Fri May 29 20:57:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011823.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Fri May 29 20:59:49 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011824.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Fri May 29 21:01:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011825.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Fri May 29 21:03:50 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011826.html

1 0

Zope Tests: 8 OK
by Zope Tests Summarizer 29 May '09

29 May '09

Summary of messages to the zope-tests list. Period Thu May 28 12:00:00 2009 UTC to Fri May 29 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 20:50:16 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011811.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 20:52:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011812.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 20:54:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011813.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Thu May 28 20:56:19 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011814.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Thu May 28 20:58:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011815.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Thu May 28 21:00:20 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011816.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Thu May 28 21:02:21 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011817.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Thu May 28 21:04:25 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011818.html

1 0

Re: [Zope-dev] [Checkins] SVN: zope.app.http/trunk/ - Replaced the dependency on zope.deprecation with BBB imports
by Stephan Richter 28 May '09

28 May '09

On Monday 25 May 2009, Shane Hathaway wrote: > +- Replaced the dependency on zope.deprecation with BBB imports As a general question, how will people know that an import location changed? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

6 17

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 28 May '09

28 May '09

Summary of messages to the zope-tests list. Period Wed May 27 12:00:00 2009 UTC to Thu May 28 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (errors=1) : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 21:02:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011808.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:51:54 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011803.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:53:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011804.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed May 27 20:55:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011805.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed May 27 20:58:00 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011806.html Subject: OK : Zope-trunk Python-2.6.1 : Linux From: Zope Tests Date: Wed May 27 21:00:04 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011807.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed May 27 21:04:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011809.html Subject: OK : Zope-trunk-alltests Python-2.6.1 : Linux From: Zope Tests Date: Wed May 27 21:06:07 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-May/011810.html

1 0

Test failure in zope.traversing 3.7.0
by Andreas Jung 27 May '09

27 May '09

I get the following failure while running the Zope 2.12 tests: ajung@suxmac2:~/sandboxes/Zope-2.12/2.12 bin/alltests Test-module import failures: Module: zope.traversing.tests.test_vhosting Traceback (most recent call last): File "/Users/ajung/.buildout/eggs/zope.traversing-3.7.0-py2.5.egg/zope/traversing/tests/test_vhosting.py", line 28, in <module> from zope.app.zptpage.zptpage import ZPTPage File "/Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/__init__.py", line 18, in <module> from zptpage import ZPTPage File "/Users/ajung/.buildout/eggs/zope.app.zptpage-3.5.0-py2.5.egg/zope/app/zptpage/zptpage.py", line 29, in <module> from zope.app.pagetemplate.engine import AppPT ImportError: No module named engine Andreas

2 2

Zsql and oracle CLOB column
by harshad behere 27 May '09

27 May '09

Dear list, While inserting data into one of the oracle table's CLOB column using zsql via python script, we observed that zope process (running in debug mode) is getting terminated/killed if length of text data >= 4094 with message on command prompt Input string too long, limit 4096 Whereas for text data with length >=4001 and <=4093 - It throws following error OperationalError on <Products.mxODBCZopeDA.ZopeDA.DatabaseConnection "DSN=test_clob_oracle" thread 3672/3672 at 0x3ac3530>: ('HY000', 1704, '[Oracle][ODBC][Ora]ORA-01704: string literal too long\n', 6113) python script details: print context.clob_zsql_test(i_description='A'*4095). return printed zsql details - INSERT INTO CLOB_TEST(description) VALUES(<dtml-sqlvar i_description type="string">) Table/column details : id - number description - clob Where as if we use mxODBCZopeDA execute API with following insert query syntax string_value = 'A'*5000 query = """ INSERT INTO CLOB_TEST(document) VALUES(?) """ result = test_connection.execute(query, string_value) it works fine even with text data having length > 10000 After googling on the same found that execute method uses/support parameters binding (is it similar to oracle bind varibles ? thats may be reason why it works well). Do we have similar support for zsql or is there other workaround ? Configuration/other details are as follows : RDBMS : Oracle Database 10g Release 10.2.0.1.0 ODBC used : Oracle ODBC which shipped with Oracle-Client-10g Python adapter : mxODBC Python ODBC Interface - 2.1 Related Zope Product : mxODBCZopeDA-1.0.10 Zope : Zope 2.11.1-final Python : python 2.4.4 Operating system : win32 ZEO setup : Yes No of ZEO nodes : one Threads per ZEO node : 10 Any kind of pointers/suggestions would be of great help. Thanking you, Harshad.

1 1