- Zope-Dev - Zope lists

[Zope 2.10] ZPT going Unicode
by Andreas Jung 17 Jan '06

17 Jan '06

As you might know I worked on the integration of the Zope 3 ZPT implementation for Zope 2.10. Before commiting the changes to the trunk I would like discuss my approach for Zope 2.10 - the ZopePageTemplate and PageTemplateFile classes will be replaced with wrapper classes around corresponding Zope 3 classes (no changes to the API, the existing unittest do pass with the wrappers) - the wrapper implementations store the content as Python unicode strings. The encoding of the content must be specified when creating/uploading new instances (either through the ZMI or through the 'encoding' parameters of the constructors). If the content is XML-ish then the encoding is taken from the XML preamble (defaults to utf8) - the ZMI screens for ZPTs use a _fixed_ UTF-8 encoding (is this also fine for asian users?) - deprecation of _all_ other methods, modules etc. from Products/PageTemplates (removal in 2.12 except of the wrapper classes) - deprecation of the TAL module (removal in 2.12) Open: - The ZPublisher will convert a 'unicode' ZPT using default_zpublisher_encoding (zope.conf) to a byte stream. The current encoding is iso-8859-15. I think it would make sense to change it to utf8. Otherwise we must explicitly set the content-type with charset=utf8 set. Thoughts? ToDo: in-place conversion of persistent ZPT instance through setstate() or so... Andreas

7 19

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 16 Jan '06

16 Jan '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2775 Blamelist: efge,jim BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Strange traceback or Error in the traceback ?
by Godefroid Chapelle 16 Jan '06

16 Jan '06

Hi, While seaching for objects of all types containing some text through the ZMI find tab, I got the traceback hereunder. (Zope 2.7.8-final on windows) Traceback (innermost last): Module ZPublisher.Publish, line 101, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module Shared.DC.Scripts.Bindings, line 306, in __call__ Module Shared.DC.Scripts.Bindings, line 343, in _bindAndExec Module App.special_dtml, line 175, in _exec Module DocumentTemplate.DT_With, line 61, in render Module DocumentTemplate.DT_Util, line 198, in eval - __traceback_info__: _ Module <string>, line 0, in ? Module OFS.FindSupport, line 151, in ZopeFind Module OFS.FindSupport, line 151, in ZopeFind Module OFS.FindSupport, line 113, in ZopeFind Module OFS.Image, line 425, in PrincipiaSearchSource AttributeError: content_typestartswith I went to the code and found the following : def PrincipiaSearchSource(self): """ Allow file objects to be searched. """ if self.content_type.startswith('text/'): return str(self.data) return '' IOW, the traceback is really strange. Anybody with a clue ? -- Godefroid Chapelle (aka __gotcha) http://bubblenet.be

2 1

Zope tests: 6 OK, 2 Failed
by Zope tests summarizer 16 Jan '06

16 Jan '06

Summary of messages to the zope-tests list. Period Sun Jan 15 12:01:02 2006 UTC to Mon Jan 16 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:10:28 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004024.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:11:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004025.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:01:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004018.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:02:57 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004019.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:04:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004020.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:05:57 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004021.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:07:27 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004022.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sun Jan 15 21:08:58 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004023.html

1 0

Zope tests: 6 OK, 2 Failed
by Zope tests summarizer 16 Jan '06

16 Jan '06

Summary of messages to the zope-tests list. Period Fri Jan 13 12:01:01 2006 UTC to Sat Jan 14 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:10:37 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004008.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:12:07 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004009.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:01:32 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004002.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:03:06 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004003.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:04:36 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004004.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:06:06 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004005.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:07:36 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004006.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Fri Jan 13 21:09:07 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004007.html

4 4

Removing 'inst'
by Philipp von Weitershausen 16 Jan '06

16 Jan '06

Tim Peters wrote: > Log message for revision 41291: > Pain, pain, and more pain. > > The build-the-installer process now completes, and running > the installer creates something that may or may not be a > working Zope. It starts fine as a Windows Service, and at > least "looks like a Zope" ;-) All hail Tim Peters! :) > Nothing in the build-the-Windows-installer process here > uses anything in the root of the inst/ directory anymore. > Instead the WinBuilders zope.mk builds Zope all by itself, > using the Python created by python.mk. Everything these > used to use in the root of the inst/ directory was so out > of whack with current reality that there was no point even > trying to reverse-engineer what it thought it was doing. It seems that 'inst' holds nothing of value anymore except 'Makefile.in' and 'WinBuilders'. I propose moving those two items to the root and remove 'inst'. Philipp

3 5

Seeking brave souls to try Zope 2.9 Windows installer
by Tim Peters 15 Jan '06

15 Jan '06

Most of the last two days I've been whacking on Zope 2.9 to build a "Zope 2 style" Windows installer that bundles Python 2.4.2, and cooperates with the new zpkgtools-created tarball layout. The build-the-Windows-installer code got simpler as a result, but ... This work is being done on branch: //svn.zope.org/repos/main/Zope/branches/tim-2.9-windows-installer which was branched off the 2.9 tag. All changes on the branch are under inst/WinBuilders/, so the idea is that when "this works", it can be merged into the 2.9 tag as well as the trunk (the stuff under WinBuilders/ isn't used for anything except building a Windows installer, and on the 2.9 tag the WinBuilders/ part is wholly broken). It's in a state now where it's not obviously broken to my eyes, but I have little experience running Zope2 so my eyes aren't reliable here. People on Windows who want to try it, knowing in advance that it may be broken in various ways, can download an experimental installer: Zope-Experimental-2.9.0-win32.exe from my member page: http://www.zope.org/Members/tim_one Please report problems to zope-dev, not to me directly. After tomorrow, I'll be on vacation for 2 weeks, and won't be terribly responsive :-) Note that I'm copying Sidnei in the hope that he can be persuaded to take up the slack. If there are problems, they're likely to be in the layout of the code: missing pieces, wrong directories, stuff like that. The 2.9 tarball's install.py installed everything it was told to install, and if there are problems there they're in Zope 2.9, not in the chain of code building the Windows installer. Nevertheless, the Windows installer could be taught to patch over them. And, of course, the build-the-installer dance may introduce new errors of its own. I hope it works for someone ;-)

3 5

Zope tests: 6 OK, 2 Failed
by Zope tests summarizer 15 Jan '06

15 Jan '06

Summary of messages to the zope-tests list. Period Sat Jan 14 12:01:02 2006 UTC to Sun Jan 15 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:10:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004016.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:12:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004017.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:01:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004010.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:03:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004011.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:04:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004012.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:06:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004013.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:07:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004014.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:09:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004015.html

1 0

Re: Putting pullparser and clientform where they belong (reverting 39890)
by Philipp von Weitershausen 15 Jan '06

15 Jan '06

Brian Sutherland wrote: > Since we are close to the release, I felt compelled to ask before I did > this. Could I revert 39890 [1] for the 3.2 release? > > It seems that phillip finished zpkg's module support some time ago [2]. > > (I ask as this is causing me headaches doing the Debian packaging for > the latest zope3) > > [1] http://mail.zope.org/pipermail/zope3-checkins/2005-November/026485.html > [2] http://mail.zope.org/pipermail/zpkg/2005-November/000077.html Sorry for replying to this so late, I only stumbled upon this recently. While I agree that the sys.modules/sys.path mangling was bad, this now raises the problem of correctly stitching in pullparser and ClientForm into Zope 2. Unfortunately, svn:externals doesn't work with files, so we'll have to make copies. They will have to be updated whenever pullparser and ClientForm have been updated and a newer Zope 3 is stitched in. Philipp

1 0

zpkgsetup
by Shane Hathaway 15 Jan '06

15 Jan '06

I just updated a trunk checkout of Zope 2. When I use 'python setup.py build_ext -i', I get this: Traceback (most recent call last): File "setup.py", line 32, in ? import zpkgsetup.package ImportError: No module named zpkgsetup.package 'make' fails the same way. My checkout has nothing called zpkgsetup. Any clues? Shane

2 2