February 2006 - Zope-Dev

Re: SVN: Zope/trunk/lib/python/OFS/Traversable.py using startswith()
by Florent Guillaume 28 Feb '06

28 Feb '06

Why? x[0] is much faster than x.startswith(). Or do you expect to have empty path components? Florent Andreas Jung wrote: > Log message for revision 65598: > using startswith() > > -=- > Modified: Zope/trunk/lib/python/OFS/Traversable.py > =================================================================== > --- Zope/trunk/lib/python/OFS/Traversable.py 2006-02-28 16:59:49 UTC (rev 65597) > +++ Zope/trunk/lib/python/OFS/Traversable.py 2006-02-28 17:17:12 UTC (rev 65598) > @@ -173,7 +173,7 @@ > name = path_pop() > __traceback_info__ = path, name > > - if name[0] == '_': > + if name.startswith('_'): > # Never allowed in a URL. > raise NotFound, name > > > -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 0

Re: [Zope3-dev] Re: Two visions
by Martijn Faassen 28 Feb '06

28 Feb '06

Max M wrote: > Jim Fulton wrote: > >> 2) In an alternate vision, Zope 2 evolves to Zope 5. > > > Zope 2 is complicated! It has too many layers of everything. > > The reason for Zope 3 is to make it simpler for developers. > > Therefore I believe that any succesfull strategy would require Zope 3 to > be usable completely without all the Zope 2 layers. > > If Zope 3 becomes just another layer on top of Zope 2 -> CMF -> Plone it > will not reduce complexity, as any developer would still need to learn > the entire stack. > > Wherever practical, Zope 2 technologies should be rewritten to Zope 3 > technologies to remove layers from the stack. I think these are good points. Five runs the risk of being yet another layer on a stack like Plone, but Five also gives the chance of us stripping off these layers and replacing it with something cleaner, and at the same time Five is giving an impulse to Zope 3 development as things slowly get ported to Zope 3 or written in a Zope 3 style. The Five project has the right attitude to deal with such integration issues. We have been quite successful: In Zope 2.9 it's possible to build modern Zope 3-style apps, using formlib and sqlos and so on (we've done it). In this vision, the Zope 3 project should stay where it is and push things forward. That doesn't mean Five should be ignored by Zope 3 developers, but it should be compartmentalized in people's minds. Zope 3 does innovation, Five does integration, and then the big codebases can move forward using both. Regards, Martijn

3 3

Re: [Zope3-dev] Two visions
by Shane Hathaway 28 Feb '06

28 Feb '06

Jeff Shell wrote: > Perhaps it's not the greatest name, but I've become enamored with *lib > names like 'formlib'. > > 'zopelib' > > Hmmm. Not the prettiest thing. But it does say "Zope Library". If that > becomes the *core* of the mythical Zope 5, awesome. This sounds familiar. :-) http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ZopeLibPac… Unfortunately, this discussion is too fuzzy for me to understand exactly what's being proposed. How about something concrete: will the Zope 3 in vision #2 have a ZMI, and will typical ZODB objects have a __parent__ and __name__? (Either yes or no is fine, but "maybe" or "sometimes" is a lot harder to interpret.) Shane

2 1

ImageFile weirdness?
by Jürgen Herrmann 27 Feb '06

27 Feb '06

hi all! i have a class ImageContainer in a python product, that has an ImageFile attached, it's named 1.gif: ... image = ImageFile('1.gif', '/some/where') setattr(self.__class__, '1.gif', image) ... i have an ImageContainer instance in my zope root. if i point my browser to http://localhost/ImageContainer/1.gif , i can see the image in the browser, everything seems fine, image is displayed. if however the image is named "1" only, e.g. ... image = ImageFile('1', '/some/where') setattr(self.__class__, '1', image) ... i notice a difference when viewing http://localhost/ImageContainer/1 . the browser pops up a download window, showing the content type is application/octet-stream. using firefox' livehttpheaders extension i found out that the content-type header is missing. if i view http://localhost/ImageContainer/1/ everything is fine however. now i peeked into App.ImageFile, where i can find a index_html() method, where the content-type header is set. viewing http://localhost/ImageContainer/1 never calls the index_html method though, http://localhost/ImageContainer/1/ obviously does. that's where i'm stuck now, who handles the ImageFile's invokation, if called like http://localhost/ImageContainer/1 ? ImageFile inherits from Acquisition.Explicit, nothing else... thanks for your attention, regards, juergen herrmann _______________________________________________________________________ >> XLhost.de - eXperts in Linux hosting << Jürgen Herrmann Bruderwöhrdstraße 15b, DE-93051 Regensburg Fon: +49 (0)700 XLHOSTDE [0700 95467833] Fax: +49 (0)721 151 463027 WEB: http://www.XLhost.de

2 3

Re: [Zope3-dev] Re: Two visions
by Dario Lopez-Kästen 27 Feb '06

27 Feb '06

Max M said the following on 2006-02-27 17:26: > Jim Fulton wrote: > >> 2) In an alternate vision, Zope 2 evolves to Zope 5. > > > Zope 2 is complicated! It has too many layers of everything. > read the full sentence that Jim wrote: > 2) In an alternate vision, Zope 2 evolves to Zope 5. > ... > > Note that Zope 5 will leverage Zope 3 technologies to allow a > variety of configurations, including a Zope 2-like configuration > with implicit acquisition and through-the-web development, and a > Zope 3-like configuration that looks a lot like the current Zope > 3 application server. Maybe, there will be a configuration that > allows Zope 2 and Zope 3 applications to be combined to a > significant degree. In this scenario I cannot see how much of the old ways of zope2 remain (unless I have a totally unrealistic view of what Jim proposes). zope 2 or zop3 become an issue of configuring which "components"/parts to use. /dario -- -- ------------------------------------------------------------------- Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech. Lyrics applied to programming & application design: "emancipate yourself from mental slavery" - redemption song, b. marley

2 1

Re: [Zope3-dev] Re: Two visions
by Stefane Fermigier 27 Feb '06

27 Feb '06

Max M wrote: > Jim Fulton wrote: > >> 2) In an alternate vision, Zope 2 evolves to Zope 5. > > Zope 2 is complicated! It has too many layers of everything. Layers are good, when they reliably hide complexity. > The reason for Zope 3 is to make it simpler for developers. Yep. 14'30'' wikis and such. > Therefore I believe that any succesfull strategy would require Zope 3 > to be usable completely without all the Zope 2 layers. > > If Zope 3 becomes just another layer on top of Zope 2 -> CMF -> Plone > it will not reduce complexity, as any developer would still need to > learn the entire stack. You mean, "on top" -> "below" ? (And "Plone" -> "CPS" ;) ). > Wherever practical, Zope 2 technologies should be rewritten to Zope 3 > technologies to remove layers from the stack. To make discussion concrete, is there a list of (core, not CMF) Zope 2 technologies that are currently missing from Zope 3 ? S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source!

1 0

[ANN] pythonproducts 1.0alpha1 released
by Rocky Burt 27 Feb '06

27 Feb '06

Hi all, I've now made available the first public 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.0alpha1 <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.4 or higher in 2.8.x series - Five 1.2 or higher Installing Uses regular python distutils for installation. Simply run:: ./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". -- Rocky Burt AdaptiveWave - Consulting, Training, and Content Management as a Service http://www.adaptivewave.com Content Management Made Simple

1 0

Five 1.2.1 and 1.3.2 released!
by Philipp von Weitershausen 26 Feb '06

26 Feb '06

The Five team is happy to announce two bugfixes releases of Five today, Five 1.2.1 and 1.3.2! What is Five ------------ Five is a Zope 2 product that allows you to integrate Zope 3 technologies into Zope 2, today. Among others, it allows you to use Zope 3 interfaces, ZCML-based configuration, adapters, browser pages (including skins, layers, and resources), automated add and edit forms based on schemas, object events, as well as Zope 3-style i18n message catalogs. We've tried to keep the Five experience as close to Zope 3 as possible, so this means that what you learn while using Five should also be applicable to Zope 3, and viceversa. More information about Five can be found on our website, http://codespeak.net/z3/five/. Changes in Five 1.2.1/1.3.2 --------------------------- * Five's traversing machinery now mimicks the ZPublisher correctly: When no Zope 3-style view is found, first the object's original ``__bobo_traverse__`` is tried. If that does not exist, Traversable resorts to attribute look-up. * Unit tests that did i18n via Localizer would fail because the request attribute that keeps Localizers list of preferred languages did not exist. For more information please consult the changes document, http://codespeak.net/z3/five/CHANGES.html Download -------- Five 1.2.1 requires Zope 2.8 and can be downloaded at http://codespeak.net/z3/five/release/Five-1.2.1.tgz. Five 1.3.2 requires Zope 2.9 and can be downloaded at http://codespeak.net/z3/five/release/Five-1.3.2.tgz. Note that Five 1.3.2 will be included in Zope 2.9.2. About the Zope 3 Base --------------------- Five is part of the *Zope 3 Base* project, which aims to offer an approachable area for developers of Zope 3 related software. More about the Zope 3 base and its projects can be found on the project website, http://codespeak.net/z3/.

1 0

Five moved to svn.zope.org
by Philipp von Weitershausen 26 Feb '06

26 Feb '06

Hi all, thanks to Jens we successfully moved the Five source code and all of its history to svn.zope.org. It now lives at svn.zope.org/Products.Five/. Zope 2.9 and the trunk use svn:externals to stitch in Five from the 1.3.2 tag. I didn't bother to update the 2.8 branch. Note that we now use the svn.zope.org directory naming convention for directories ('tags', 'branches') as well as branches (x.y) and tags (x.y.z). You may resume your check-ins :). Philipp

1 1

Re: [Zope3-dev] The Zope Software Certification Program and Common Repository Proposal
by Stephan Richter 24 Feb '06

24 Feb '06

On Thursday 23 February 2006 20:29, Jim Fulton wrote: > This is quite a document and vision. I hope we can pull something > like it off. (Like many, I recognize the daunting size of the task.) I have already working parsers and writers for all file formats. I have also a preliminary (but tested) implementation of registering, managing, unregistering a package in the repository with the ZSCP. Kamal Gill has agreed to do some initial artwork for the site, which should be done mid-March. We will see how it proceeds. Roger suggested to maybe even do some of the work during the Swiss Eastern Spring. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training

1 0