- Zope-Dev - Zope lists

Zope 3.4.0 candidate 1 Released
by Stephan Richter 03 Feb '08

03 Feb '08

January 31, 2008 - The Zope 3 development team announces the Zope 3.4.0c1 release. This release is the first release candidate for Zope 3.4.0. It was preceeded by an early beta 2 release back in November, 2007. Zope 3.4 introduces support for binary large objects in the ZODB, and provides a new postprocessing hook for publishing results. Many of the packages also provide small feature improvements that are too numerous to list at this point. Packages and Eggs ----------------- Since the first Zope 3.4 alpha and beta releases, we have finished the transition to a completely egg-based system. This largely means that most Zope 3 developers do not use the classic Zope 3 tar ball release anymore. However, for your convenience, the Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series and probably for 3.5 as well. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) ~~~~~~~~~~~~~~~~~~~~~~~~ The known good set -- or in short KGS -- is a package index that derives from the official Python Package Index (PyPI) and thus contains all available packages in the Python world. But for a controlled set of packages, only certain versions that are known to work together are available. The list of controlled packages and their versions for Zope 3.4 can be found at the index page [1]_. The index can be used in several ways -- described here for `buildout`-based projects. The easiest method is to specify the index option in your ``buildout.cfg`` file:: [buildout] index = http://download.zope.org/zope3.4 ... You can also "nail" the versions by downloading the versions [2]_ and insert them as follows: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Philipp von Weitershausen has developed a package called `zopeproject` to quickly setup the boilerplate for any Zope 3 based project. Ample documentation is provided at the `zopeproject` home page [3]_. `zopeproject` uses Paste or ZDaemon to create a working server. Here are the necessary commands to get a project started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~~~~~~~~~~~~~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. (I hope one gets developed before Zope 3.4.0 final.) However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, do the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.1 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://download.zope.org/zope3.4/controlled-packages.cfg .. [2] http://download.zope.org/zope3.4/versions.cfg .. [3] http://pypi.python.org/pypi/zopeproject What is Zope 3? --------------- Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 -------------------------- Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. Downloads --------- - Zope 3.4 Egg Index: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/controlled-packages.cfg - Zope 3.4 Latest Versions: http://download.zope.org/zope3.4/versions.cfg - The classic Zope 3 source release can be downloaded from: http://zope.org/Products/Zope3 Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4.4 to run. You must also have zlib installed on your system. Resources --------- - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope3-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net Acknowledgments --------------- Much thanks to everyone who contributed to this release. Since all contributions are now spread over a multitude of packages, listing all contributors is not feasible anymore.

11 26

Re: [Zope3-Users] Re: [Zope-dev] Zope 3.4.0 candidate 1 Released
by Martijn Faassen 03 Feb '08

03 Feb '08

Hey, On Feb 1, 2008 11:52 PM, Martin Aspeli <optilude(a)gmx.net> wrote: > Stephan Richter wrote: > > On Friday 01 February 2008, Martijn Faassen wrote: > >> http://www.openplans.org/projects/zorg-redux > > > > This project does not seem to be public. > > Right - thanks Martijn for spilling the beans prematurely. ;-) I hadn't realized that thing was private, but I don't feel too guilty. The Foundation hasn't been hiding this effort, we just don't want too many cooks involved before it's ready. Anyway, Martin, I'm just recruiting people who want to write content for you and giving you people to add to your list of volunteers to write about Zope 3. I'm hoping you are keeping a list. :) Regards, Martijn

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 03 Feb '08

03 Feb '08

Summary of messages to the zope-tests list. Period Sat Feb 2 12:00:00 2008 UTC to Sun Feb 3 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:03:18 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009047.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:04:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009048.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:06:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009049.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:07:49 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009050.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:09:19 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009051.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Feb 2 21:10:50 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009052.html

1 0

Zope Tests: 5 OK, 1 Failed
by Zope Tests Summarizer 03 Feb '08

03 Feb '08

Summary of messages to the zope-tests list. Period Fri Feb 1 12:00:00 2008 UTC to Sat Feb 2 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:06:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009044.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:02:00 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009041.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:03:30 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009042.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:05:01 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009043.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:08:01 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009045.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 21:09:31 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009046.html

2 1

Zope Tests: 5 OK
by Zope Tests Summarizer 01 Feb '08

01 Feb '08

Summary of messages to the zope-tests list. Period Thu Jan 31 12:00:00 2008 UTC to Fri Feb 1 12:00:00 2008 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 1 06:33:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009036.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Feb 1 06:34:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009037.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 06:36:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009038.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 06:37:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009039.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Feb 1 06:39:09 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-February/009040.html

1 0

some broken publishers on retry
by Adam Groszer 31 Jan '08

31 Jan '08

Hello, After a day of debugging I came to the finding that at some places the request and response gets faked after a retry occurred. zope.app.testing.functional calls the publisher like this: publish(request, handle_errors=handle_errors) deep in publish a new instance of request is created in case of a retry old one dropped, works on the new one def publish(request, handle_errors=True): ... return request (returns the newly instantiated request) back to zope.app.testing.functional: publish(request, handle_errors=handle_errors) it just drops the return value I found the following likely places that could be affected: zope.app.testing.functional response = ResponseWrapper(request.response, path) if env.has_key('HTTP_COOKIE'): self.loadCookies(env['HTTP_COOKIE']) publish(request, handle_errors=handle_errors) self.saveCookies(response) ... response = ResponseWrapper(request.response, path) publish(request, handle_errors=handle_errors) return response zope.server.ftp.publisher.py: response = request.response publish(request) return response.getResult() zope.app.twisted.ftp.utils.py: response = request.response publish(request) return response.getResult() zope.app.debug.debug.py: request = self._request(path, stdin, *args, **kw) getStatus = getattr(request.response, 'getStatus', lambda: None) _publish(request Anybody for/against fixing those? -- Best regards, Adam Groszer mailto:agroszer@gmail.com -- Quote of the day: This dead of midnight is the noon of thought, And Wisdom mounts her zenith with the stars. - Lady Barbauld

2 1

Zope 3.4 final?
by Tom Hoffman 31 Jan '08

31 Jan '08

Hi All, This is a manually-generated reminder that it would be very, very helpful to the SchoolTool project if there would be a Zope 3.4 "final" release in the next month. 3.4.0b2 is designated as "stable" on zope.org, and while it may only be a semantic distinction to remove the "b2," it will allow us to move zope3 packages into Debian and Ubuntu, and in turn move a whole stack of other Zope3 related packages, and SchoolTool, into those distributions. Thanks for your consideration, Tom Hoffman

2 1

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 31 Jan '08

31 Jan '08

Summary of messages to the zope-tests list. Period Wed Jan 30 12:00:00 2008 UTC to Thu Jan 31 12:00:00 2008 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.11 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 30 20:59:09 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009035.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 30 20:53:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009031.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 30 20:54:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009032.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 30 20:56:08 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009033.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 30 20:57:38 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009034.html

1 0

FileUpload and blob on Windows
by Leonardo Rochael 30 Jan '08

30 Jan '08

Hi all, ZODB.blob.Blob.consumeFile() needs a real, existing filesystem location passed into it to work, which is why plone.app.blob[1] patches ZPublisher.HTTPRequest.FieldStorage to generate a tempfile.NamedTemporaryFile() instead of a tempfile.TemporaryFile() for large uploaded files. However, if one tries to consume a NamedTemporaryFile and then open its generated blob before closing the tempfile, Windows complains: >>>> import ZODB.blob, tempfile >>>> f = tempfile.NamedTemporaryFile() >>>> b = ZODB.blob.Blob() >>>> b.consumeFile(f.name) >>>> b.open('r') > Traceback (innermost last): > ... > IOError: [Errno 13] Permission denied: 'c:\\buildout\\var\\tmp\\tmpsuykkc' > Closing the NamedTemporaryFile after consuming it and before opening the blob makes the matters worse, since Windows removes the file from under Blob *after* it has been consumed, so we'll have to think of a different strategy for consuming request files on Windows, but whichever strategy ends up being used, the problem remains that we cannot keep the FileUpload instance from the request open in 'w+' mode (readable and writable) while allowing the blob instance to be opened in the same request. So I'd like to ask some policy questions: 1. Is it ok to close a FileUpload instance from the request? 2. Alternatively, is it ok to replace it on the request with a read-only file-like object with the same contents, or maybe even force it to be read-only to begin with? If none of the above are ok, then we'll be forced to copy the whole file on Windows when consuming an uploaded file from the request into a blob, unless we use some non-portable win32 code to allow writing and reading to the same file simultaneously. [1] http://dev.plone.org/plone/browser/plone.app.blob -- View this message in context: http://www.nabble.com/FileUpload-and-blob-on-Windows-tp15129190p15129190.ht… Sent from the Zope - Dev mailing list archive at Nabble.com.

5 8

Zope Tests: 5 OK
by Zope Tests Summarizer 30 Jan '08

30 Jan '08

Summary of messages to the zope-tests list. Period Tue Jan 29 12:00:00 2008 UTC to Wed Jan 30 12:00:00 2008 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 29 20:51:43 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009026.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 29 20:53:13 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009027.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 29 20:54:43 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009028.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 29 20:56:13 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009029.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 29 20:57:44 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-January/009030.html

1 0