December 2005 - Zope-Dev

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 20 Dec '05

20 Dec '05

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: 2339 Blamelist: andreasjung BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 20 Dec '05

20 Dec '05

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2338 Blamelist: andreasjung,chrisw,jim,poster BUILD FAILED: failed test sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 20 Dec '05

20 Dec '05

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: 2337 Blamelist: andreasjung,chrisw,jim,poster BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Re: sessions in the presence of conflicts
by Florent Guillaume 20 Dec '05

20 Dec '05

[Using zope-dev@ instead of zope@] Dennis Allison wrote: > A more session-friendly conflict resolution might use: > > 1. if any of the states are invalid (that is, has a key '_invalid') > return the invalid state. > > 2. if any any of the states attributes ['token','id','_created'] > differ then there is a conflict, raise the conflict exception. > > 3. order the newState and savedState by modification time (or if that > cannot be computed, by access time). > > 4. any key appearing in oldState's dictionary but not appearing in > both savedState and newState should be removed from all. This > corresponds to a key-value pair being deleted in one of the > transactions. Insertions will be managed automatically by > the updates. > > 5. beginning with the oldest, update oldState dictionary of key-value > pairs using the dictionary part of newState and savedState. Return > oldState. > > This does several things. First, it captures independent key-value > changes made in both potentially conflicting transactions. Second, it > provides a reasonable ordering for multiple (potentially conflicting) > key-value pair updates. Third, it manages insertions and deletions to the > session variable set in the presence of conflicts. > > Does this make sense? I have yet to figure out how to map a > TransientObject "state" back to the object it represents, but it clearly > is possible. I certainly makes sense from a high level description, but the devil is in the details. I'd be interested in looking at it if you code something. Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

5 7

Modifying a ZPT state based on a certain parameter
by Takahashi, Michael 20 Dec '05

20 Dec '05

Hi guys, I am running on Zope 2.7.6 with Plone 2.0.5. I am currently building a dynamic application using MySQL as the backend database. I'd like to be able to change a ZPT's state based on a parameter passed by the db. For example, I have a ZPT that displays information for a particular course. However, if this courses "active" field is set to NO, then I would like to be able to have the ZPT's state be visible. If the courses "active" field is set to "yes" then I would like to modify the state so that the ZPT is published. I'm thinking I'd probably have to use the wf_tool in conjunction with portal_workflow? A call similar to something like so: tal:condition="python:records.active=='yes'" ...then implement the necessary call to modify the workflow and make the ZPT published and vice versa. Any help is greatly appreciated. Thanks, Mike

2 1

Announcement: the Zope Subversion repository will be down for maintenance on December 25th, 2005
by Jim Fulton 19 Dec '05

19 Dec '05

Jens Vagelpihl has graciously offered to convert the subversion repository to use a file-system back end. The repsository will be inaccessable for some portion of December 25. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

2 2

Unit Test Failures
by Benji York 19 Dec '05

19 Dec '05

The Zope2 unit tests have been failing for some time on buildbot.zope.com. Looks like a Five-related problem: http://buildbot.zope.org/Zope%20trunk%202.4%20Linux%20zc-buildbot/builds/10… -- Benji York Senior Software Engineer Zope Corporation

5 11

Re: [Zope-dev] RFV: Unicode in Zope 2
by Jürgen Herrmann 19 Dec '05

19 Dec '05

On Mon, December 19, 2005 17:44, Andreas Jung wrote: > > > --On 9. Dezember 2005 10:11:42 -0500 Jim Fulton <jim(a)zope.com> wrote: > >> > I forgot a very important need: >> >> - Common approach to Unicode >> >> >> We need to migrate Zope 2 to use a similar strategy. We need volunteers to brainstorm how this can be done and make one or more proposals. This is likely a prerequisite for finishing the publisher and ZPT work. >> > > I think there are two approaches. Textual content can be produced by nearly > every Zope object (and its methods). Content can be composed by the basic Zope functionalities like DTML, ZPT, PyScripts and external methods (in the > sense that these functionalities are able to call other objects and their methods). > > a) one could enforce all objects to return unicode (which would be a very hard requirement) and possibly break any application hi all! i think, a) is surely the cleaner solution. actually i always... - inlcude an content-type header and set the charset for all forms to utf8 - use :utf8:ustring/utext/ulines/utokens converters on all forms this way i always have unicode strings in my db. up to now i never had any unicode problems, expect when interfacing external systems and not doing the proper unicode conversion dance there... why not design a migration script that converts all non-ascii strings in the db to unicode strings, based on the default encoding, etc... also just some thoughts :) jürgen herrmann ps: what's especially critical here is code that handles filenames. some filesystems just don't handle unicode filenames, already had some headache there :) > > b) convert non-unicode content produced by Zope objects from where they are > called (DTMl, ZPT, PyScript, Extmethods) to unicode. This would limit the number of places where we need to change code. The encoding of the non-unicode content could be from the 'content-type: XXX; charset=XXXX' header > (if set) or as fallback from the configured zpublisher_default_encoding. An > object could also set a property "my_output_encoding" (or so)... > > just-some-thoughts... > -aj > > _______________________________________________ > Zope-Dev maillist - Zope-Dev(a)zope.org > http://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > http://mail.zope.org/mailman/listinfo/zope-announce > http://mail.zope.org/mailman/listinfo/zope ) > _______________________________________________________________________ >> 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 _______________________________________________________________________ >> 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

1 0

RFV: Unicode in Zope 2
by Jim Fulton 19 Dec '05

19 Dec '05

A few weeks ago, I mentioned 3 big things I'd like to see for merging Zope 2 and Zope 3: - Common Publisher - Common Security frameworks - Common ZPT implementations I forgot a very important need: - Common approach to Unicode In particular, In Zope 3, all text is stored and managed as Unicode. The publisher decodes request data and encodes response data. The vast majority of application and library code can ignore encoding issues. (The exceptions are applications and frameworks that need to exhange text with non-Unicode-aware external systems.) This has provided great simplifications and allowed us to avoid common pitfals from mixing Unicode and encoded text. We need to migrate Zope 2 to use a similar strategy. We need volunteers to brainstorm how this can be done and make one or more proposals. This is likely a prerequisite for finishing the publisher and ZPT work. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

5 10

ZPublisher, ZPT and XHTML
by Andreas Jung 19 Dec '05

19 Dec '05

Another usecase where Zope does not play nicely: You can create a ZPT with XHTML content where the content is encoded as UTF-8 (which the corresponding encoding declaration within the XML preamble). When you redefine the zpublisher_default_encoding Zope might convert the UTF8 body of the ZPT to some other encoding. This leads to two possible problems: a) the new encoding is not available from the content-type header and b) the encoding inside the XML preamble still contains the original encoding...both is wrong...any ideas how to deal with that problem (perhaps the problem is only a constructed problem?) -aj

1 0