April 2006 - Zope-Dev

Re: [Zope-dev] Branches finished for merging.
by Lennart Regebro 27 Apr '06

27 Apr '06

On 4/26/06, Andreas Jung <lists(a)zopyx.com> wrote: > What are the possible risks of those changes? What is the goal of this > branch? Integration as an optional feature or replacement of > ZPublisher/ZServer? The direct goal of this is to make it more pluggable, so that we can introduce twisted or zope.publisher as alternatives. Twisted, so that we can write new servers for Zope2, and zope.publisher, so that we can closer to the goal of being able to run both Zope3 and Zope2 software under the same server. The long term goal is to replace ZServer/ZPublisher with whatever Zope3 uses, which at that point in time most likely will be twisted/zope.publisher, to tighten the Z2/Z3 integration, and reduce the amount of code we need to maintain. The risks is that somehow we introduce some subtle behavioural change that isn't tested for. The traversal refactoring means that the role checking is now done after each traversal step, instead of intermingled with it. The functionality should be the same, but perhaps there is some untested special case when it changes. We have had much larger incompatibility changes in earlier major releases though. The WSGI refactoring may mean that somebody using internal features of ZServer might need to change something. Also it means that what the publish_module() method expect as parameters will change. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 1

[ANN] pythonproducts 1.0beta1 released
by Rocky Burt 23 Apr '06

23 Apr '06

I'm pleased to announce the first beta release of pythonproducts. pythonproducts ============== Description A mechanism to construct Zope 2 products as regular python packages. This enables a python package to be deployed as a Zope 2 product using a similar strategy as Zope 3. Author/Maintainer `Rocky Burt <rocky(a)serverzen.com>`__ Latest Release `1.0beta1 <http://dev.serverzen.com/site/projects/pythonproducts/releases/pythonproduc…>`__ License BSD-style, see LICENSE.txt for details Source Control http://codespeak.net/svn/z3/pythonproducts/ Requirements - Python 2.3.5 or higher in 2.3.x series - Zope 2.8 or 2.9 - Five 1.2 or higher Installing Uses regular python distutils for installation. Simply run:: python ./setup.py install --home /some/path/to/zope_instance_home Usage Once pythonproducts has been installed, the standard practise of installing a python package as a Zope 2 product is as follows: 1. edit (or create it if it doesn't exist already) ``$YOUR_PKG_SOURCE/configure.zcml`` and add the line ``<five:registerPackage package="." initialize=".initialize" />`` 2. copy your python package to ``$INSTANCE_HOME/lib/python`` 3. create a ZCML "slug" by creating the file `` $INSTANCE_HOME/etc/package-includes/yourpackage-configure.zcml`` and populating it with ``<configure package="yourpackage" />`` Explanation of Usage Step 1: Your python package needs to register itself as a Zope 2 product. This is accomplished by using the new ``registerPackage`` directive. This directive takes a (required) "package" attribute which declares any python package as a Zope 2 product (with "." meaning this package). Another (optional) attribute is the 'initialize' attribute. If this attribute is defined, a function with that name will be invoked in a traditional Zope 2 style with a ProductContext instance as the sole argument. Step 2: Your python package needs to exist *somewhere* on PYTHONPATH. With Zope 2.8, $INSTANCE_HOME/lib/python is added to the PYTHONPATH so copying your python package there ensures its somewhere in PYTHONPATH. But really your python package could be copied to any directory that exists on PYTHONPATH (ie /usr/lib/python2.3/site-packages). Step 3: The standard way of registering a package with Zope 3 is to create a ZCML "slug" in the $INSTANCE_HOME/etc/package-includes directory. This file can be called anything as long as it ends with "-configure.zcml". Regards, Rocky -- Rocky Burt AdaptiveWave - Content Management as a Service http://www.adaptivewave.com Content Management Made Simple

4 7

cvs.zope.org/Products -> svn.zope.org?
by Andreas Jung 23 Apr '06

23 Apr '06

Hi, almost all big Zope projects have changed to Subversion fortunately. Using svn:externals is a nice way to build bundles and helps a lot deploying software. However projects still have some dependencies from cvs.zope.org some older material (possibly not updated material). So the current solution is to write a shell script that pulls the stuff manually from cvs.zope.org. Wouldn't it make sense to migrate the complete Products hierarchy from cvs.zope.org to svn.zope.org? Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope & Plone development, Consulting

5 11

Zope 3 ZPT integration for Zope 2.10 needs more work
by Andreas Jung 22 Apr '06

22 Apr '06

Hi, as you might know I have been working on the integration of the Zope 3 ZPT implementation for Zope 2.10. Unfortunately I won't have enough time to finish my work (due to customer projects). What's the current state? - all integration work done so far is on the "/ajung-final-zpt-integration" branch (I've only touched Products/PageTemplates) - the ZopePageTemplate and PageTemplateFile class already use the ZPT code from Zope Z3 - the TALES engine of Zope 2 is also already replaced with the Zope 3 TALES engine So what's missing? - basically four or five unittests fail (depending if you use the current trunk or the trunk version from February (when I created the development)) I spent two hours today trying to resolve the remaining issues but I am somehow spinning around without getting closer to solution. It would be fine if someone with some deeper ZPT insights could have look at the outstanding problems. Otherwise we must defer the Zope 3 ZPT integration until Zope 2.11...any volunteers? :-) Andreas

1 0

Re: [Zope-dev] Trunk seems broken
by Lennart Regebro 21 Apr '06

21 Apr '06

On 4/21/06, Andreas Jung <lists(a)zopyx.com> wrote: > I'll try to resolve the outstanding issues on my branch this weekend end. > Reverting the changes would not be the problem since this represents an > older state. I was not aware of the fact that macros did not work. > Obviously we don't have any unittests for this ZPT part :-/ No, I couldn't find any. I just checked in a very trivial (and currently failing) test that runs on on 2.9.2. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

1 1

Re: [Zope-dev] Trunk seems broken
by Lennart Regebro 21 Apr '06

21 Apr '06

On 4/21/06, Andreas Jung <lists(a)zopyx.com> wrote: > My ajung-final-zpt-integration branch contains a version that does no > longer require the Zope 2 TALES implementation (but uses the Zope 3 > codebase)...but > this branch needs some more work for 2.10. That would probably be good. Currently you can't do any thing with macros in trunk, so we need either that, or revert the pagetemplate changes that has been done. And that would be uncool. :) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 1

Trunk seems broken
by Lennart Regebro 21 Apr '06

21 Apr '06

Everytime I try to view a page template I get Exception Value Context instance has no attribute 'getValue' Traceback (innermost last): * Module ZPublisher.Publish, line 115, in publish * Module ZPublisher.mapply, line 88, in mapply * Module ZPublisher.Publish, line 41, in call_object * Module Shared.DC.Scripts.Bindings, line 313, in __call__ * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec * Module Products.PageTemplates.ZopePageTemplate, line 291, in _exec * Module zope.pagetemplate.pagetemplate, line 117, in pt_render Warning: Macro expansion failed Warning: exceptions.AttributeError: Context instance has no attribute 'getValue' * Module zope.tal.talinterpreter, line 277, in __call__ * Module zope.tal.talinterpreter, line 352, in interpret * Module zope.tal.talinterpreter, line 902, in do_useMacro AttributeError: Context instance has no attribute 'getValue' the offending line is outer = self.engine.getValue('macroname') and self.engine is a Products.PageTemplates.TALES.Context instance In Zope2, as far as I can see, neither engines or contexts has a getValue method. Should we really use Zope TALES with Zope3 page templates? -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

2 1

64-bit BTrees
by Fred Drake 21 Apr '06

21 Apr '06

I have a need for 64-bit BTrees (at least for IOBTree and OIBTree), and I'm not the first. I've created a feature development branch for this, and checked in my initial implementation. I've modified the existing code to use PY_LONG_LONG instead of int for the key and/or value type; there's no longer a 32-bit version in the modified code. Any Python int or long that can fit in 64 bits is accepted; ValueError is raised for values that require 65 bits (or more). Keys and values that can be reported as Python ints are, and longs are only returned when the value cannot be converted to a Python int. This can have a substantial effect on memory consumption, since keys and/or values now take twice the space. There may be performance issues as well, but those have not been tested. There are new unit tests, but more are likely needed. If you're interested in getting the code from Subversion, it's available at: svn://svn.zope.org/repos/main/ZODB/branches/fdrake-64bits/ Ideally, this or some variation on this could be folded back into the main development for ZODB. If this is objectionable, making 64-bit btrees available would require introducing new versions of the btrees (possibly named LLBTree, LOBTree, and OLBTree). I welcome comments. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Don't let schooling interfere with your education." -- Mark Twain

8 14

Re: [Zope-dev] Traversal issue which affects Five
by Alec Mitchell 21 Apr '06

21 Apr '06

On 4/21/06, Andreas Jung <lists(a)zopyx.com> wrote: > > > --On 21. April 2006 07:09:45 -0400 Jim Fulton <jim(a)zope.com> wrote: > > In general, I think that new features in bug-fix releases are a bad idea. > > Of course, the line between bug-fix and feature is not always crisp. > > Something that is really a new feature should wait for a feature release. > > > > Sure, in this particular case the issue is bug for Alec and Philipp, others > consider it a feature :-) A behavior introduced because by some > implementation bug is likely to be considered as a bug (this justifies the > change in Five 1.3.3).... Perhaps it's just my perspective here, but I think it's a stretch to describe the fix I've committed as a "feature". Before the fix, when a __bobo_traverse__ method returned an object obtained via acquisition it was treated very differently than an object returned by normal traversal, and when that object had an acquisition wrapper everything works (there is very explicit code and tests that ensure this), however if the object returned has no Acquisition wrapper (because it is a method, string, etc) then a very cryptic Unauthorized error is raised ("Container None has no security assertions"). It's hard for me to see this as anything but a bug, and the fact that it causes serious problems for anyone who wants to use attribute acquisition with Five makes it a rather serious one. Dieter's proposed fix introduces feature (which I think is the source of this bug/feature confusion). Though as he says, it is one which has close to no consequences because it has no effect until product developers (Five included) take advantage of it by raising a new exception from their __bobo_traverse__ methods. Even in that case, the implementation of the feature should be somewhat tirvial and unlikely to be error prone. Nonetheless, the two proposals serve somewhat different purpooses, though Dieter's new feature could easily be used to allow products to circumvent the above bug and simplify existing product code. Alec

1 0

Re: [Zope-dev] Traversal issue which affects Five
by Lennart Regebro 21 Apr '06

21 Apr '06

It would be very nice if we could get a list of use cases and expected behaviour, as I hope to refactor the Zope2 traversal in the near future and get rid of five:traversable completely. To do this without making everybody angry, I need usescases so I can make sure it works. :)

1 0