- Zope-Dev - Zope lists

Looking for Zope content management developers in Israel
by Lior Rudnik 23 May '06

23 May '06

If you are in Israel and know Zope please contact me. Best regards, Lior Rudnik CTO, Logia. Mobile: +972-52-3098113 Office: +972-9-9701669 Fax: +972-9-9701821 http://www.logiamobile.com <https://mail2.logiamobile.com/exchweb/bin/redir.asp?URL=http://www.logiamob…>

1 0

Re: SVN: Zope/branches/ajung-zpt-end-game/lib/python/Products/PageTemplates/Expressions.py Officially deprecate the BBB methods on the iterator and add a note
by Tres Seaver 23 May '06

23 May '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philipp von Weitershausen wrote: > Log message for revision 68231: > Officially deprecate the BBB methods on the iterator and add a note > regarding our plans for the other iterator BBB code > > > Changed: > U Zope/branches/ajung-zpt-end-game/lib/python/Products/PageTemplates/Expressions.py > > -=- > Modified: Zope/branches/ajung-zpt-end-game/lib/python/Products/PageTemplates/Expressions.py > =================================================================== > --- Zope/branches/ajung-zpt-end-game/lib/python/Products/PageTemplates/Expressions.py 2006-05-22 01:08:55 UTC (rev 68230) > +++ Zope/branches/ajung-zpt-end-game/lib/python/Products/PageTemplates/Expressions.py 2006-05-22 01:17:43 UTC (rev 68231) > @@ -35,6 +35,7 @@ > > # BBB 2005/05/01 -- remove after 12 months > import zope.deprecation > +from zope.deprecation import deprecate > zope.deprecation.deprecated( > ("StringExpr", "NotExpr", "PathExpr", "SubPathExpr"), > "Zope 2 uses the Zope 3 ZPT engine now. Expression types can be " > @@ -98,7 +99,12 @@ > > __allow_access_to_unprotected_subobjects__ = True > > - # these used to be properties in ZTUtils.Iterator.Iterator > + # The things below used to be attributes in > + # ZTUtils.Iterator.Iterator, however in zope.tales.tales.Iterator > + # they're methods. We need BBB on the Python level so we redefine > + # them as properties here. Eventually, we would like to get rid > + # of them, though, so that we won't have to maintain yet another > + # iterator class somewhere. > > @property > def index(self): > @@ -116,18 +122,27 @@ > def item(self): > return super(ZopeIterator, self).item() > > - # these aren't in zope.tales.tales.Iterator, but were in > - # ZTUtils.Iterator.Iterator > + # The following things were in ZTUtils.Iterator.Iterator but > + # aren't anymore in zope.tales.tales.Iterator. For a good reason. > + # They're just insane. > > + # BBB 2005/05/01 -- to be removed after 12 months > + > @property > + @deprecate("The 'nextIndex' method has been deprecated and will disappear " > + "in Zope 2.12. Use 'iterator.index+1' instead.") > def nextIndex(self): > return self.index + 1 > > + @deprecate("The 'first' method has been deprecated and will disappear " > + "in Zope 2.12. Use the 'start' property instead.") > def first(self, name=None): > if self.start: > return True > return not self.same_part(name, self._last, self.item) > > + @deprecate("The 'last' method has been deprecated and will disappear " > + "in Zope 2.12. Use the 'end' property instead.") > def last(self, name=None): > if self.end: > return True > I don't think deprecating 'first' and 'last' is appropriate here: they *aren't* synonyms for 'start' and 'end; they are used to implement sort-break processing. Here is the comment from the checkin which initially documented them (http://mail.zope.org/pipermail/zpt/2001-December/002598.html) > > + Note that 'first' and 'last' are intended for use with sorted > + sequences. They try to divide the sequence into group of items > + with the same value. If you provide a path, then the value > + obtained by following that path from a sequence item is used for > + grouping, otherwise the value of the item is used. You can > + provide the path by passing it as a parameter, as in > + "python:repeat['item'].first('color')", or by appending it to the > + path from the repeat variable, as in "repeat/item/first/color". > + I'm pretty sure that such changes ought to be proposed on the 'zpt' list, as they are germane outside Zope's own ZPT implementation. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEcS80+gerLs4ltQ4RAgMJAKCApnKFQfGOsPmvXDwu52S0cPqnmACeLK6i gkrqn4HkVCFaEG+5QCIgTzE= =OSnn -----END PGP SIGNATURE-----

3 7

Zope 3 ZPTs in Zope 2: Nearly done
by Philipp von Weitershausen 23 May '06

23 May '06

Hi, as some of you might have seen from the checkins, I'm trying to complete Andreas's work of bringing the Zope 3 ZPT engine to Zope 2. Andreas has done a great job dealing with the very non-trivial unicode and persistency-compabitibility issues already. I've taken over since to fix up Five accordingly (which is basically done) and make everything else work again (also nearly done). Hanno Schlichting from the Plone crowd has helped me a lot there by running 3rd party software like the CMF (which uses the PageTemplate implementation for filesystem-based templates) against our branch and pointing out backward compatibility issues (which could be fixed with his help). So far it's looking good. There are many subtle differences between the two implementations that make progress slow. Right now I've hit three minor problems (I'm sure there are more, but this is what I have on my plate right for now) regarding some incompatibilities between the Zope 2 and Zope 3 implementations. I've sketched out the problems next to their corresponding (failing) unit tests (look for the XXX comments): http://svn.zope.org/Zope/branches/ajung-zpt-end-game/lib/python/Products/Pa… http://svn.zope.org/Zope/branches/ajung-zpt-end-game/lib/python/Products/Pa… All three require some effort in order to provide full backward compatibility. Thus I thought I run these by you, let you read what I think about them and hopefully get some feedback on how to proceed. Silence is treated as consent with what I propose in the comments. Philipp P.S.: For those of you who want to try this out or help, check out the 'ajung-zpt-end-game' branch of Zope 2 (which will automatically pull the corresponding Five branch as well).

6 9

url with space "%20" on end fails
by Erik Dahl 22 May '06

22 May '06

I have an object that has a space at the end of its id (I know this is bogus but I guess its a valid id). its url is: http://zenoss/zport/dmd/Devices/Power/UPS/devices/POB%202nd%20Floor% 20%20 Trying to navigate to this url fails with "Resource not found". Zope seems to be trimming the spaces of the end. Adding a "/" on the end makes this work correctly. Not sure where I start to look for the problem... any thoughts? (other than take the " " off the end of your ids :)) -EAD

4 3

ZCTextIndex bug?
by Chris Withers 16 May '06

16 May '06

I know it's an old Zope version, but it doesn't look like the code's changed in this area since then... Should it be possible for the following to happen? File "C:\Zope\2.7.6\lib\python\Products\ZCatalog\ZCatalog.py", line 558, in uncatalog_object self._catalog.uncatalogObject(uid) File "C:\Zope\2.7.6\lib\python\Products\ZCatalog\Catalog.py", line 411, in uncatalogObject x.unindex_object(rid) File "C:\Zope\2.7.6\lib\python\Products\ZCTextIndex\ZCTextIndex.py", line 181, in unindex_object self.index.unindex_doc(docid) File "C:\Zope\2.7.6\lib\python\Products\ZCTextIndex\OkapiIndex.py", line 68, in unindex_doc BaseIndex.unindex_doc(self, docid) File "C:\Zope\2.7.6\lib\python\Products\ZCTextIndex\BaseIndex.py", line 176, in unindex_doc self._del_wordinfo(wid, docid) File "C:\Zope\2.7.6\lib\python\Products\ZCTextIndex\BaseIndex.py", line 304, in _del_wordinfo del doc2score[docid] KeyError: 1833646546 cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

zpkg, building zope from source
by Sidnei da Silva 16 May '06

16 May '06

I was looking at zpkg for the first time today, and was sorry to realize it won't run to completion on a Windows machine due to some minor use of os.WIFEXITED which is due to a dubious use of the 'tar' command, since Python has a 'tarfile' module in the standard library. Since it looks like using tarfile there should work just fine, would anyone mind if I replace this? -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214

3 6

xmlrpc OverflowError fault
by Willi Langenberger 15 May '06

15 May '06

Trying to get a Zope DateTime object (as dictionary value) via xml-rpc gives on OverflowError! You can try it yourself: (I used a freshly installed Zope-2.9.3 [with python-2.4.3] on Linux FC3; but other versions should behave equally.) Add a Python Script in the Zope OFS root folder: return {'root_modification_time': container.bobobase_modification_time()} The www request returns: {'root_modification_time': DateTime('2006/05/13 14:33:12.445 GMT+2')} But the XML-RPC returns: xmlrpclib.Fault: (-1, 'Unexpected Zope exception: exceptions.OverflowError - long int exceeds XML-RPC limits' The reason for this is, that the DateTime object is treated as a normal instance by xmlrpclib, ie __dict__ is marshalled (which, unfortunately, contains the attribute '_millis', which is usually too big). It would be better anyway, if Zope DateTime objects would be marshalled as XML-RPC dates (dateTime.iso8601). Eg like that: --- xmlrpclib.py.ori 2006-05-13 13:29:45.606954800 +0200 +++ xmlrpclib.py.wlang 2006-05-13 13:32:45.923542512 +0200 @@ -701,10 +701,15 @@ def dump_instance(self, value, write): # check for special wrappers + import DateTime as ZopeDateTime if value.__class__ in WRAPPERS: self.write = write value.encode(self) del self.write + elif value.__class__ == ZopeDateTime.DateTime: + self.write = write + DateTime(value).encode(self) + del self.write else: # store instance attributes as a struct (really?) self.dump_struct(value.__dict__, write) However, this would modify xmlrpclib.py from the python distribution, wich is plain ugly. Can anyone think of a better solution? Is it possible to change xmlrpclib.WRAPPERS from Zope, but leave python's xmlrpclib.py unaffected? \wlang{} -- Willi.Langenberger(a)wu-wien.ac.at Fax: +43/1/31336/9207 Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria

2 2

Re: [Zope-dev] Zope 2.9.3 release
by Alec Mitchell 10 May '06

10 May '06

On 5/9/06, Andreas Jung <lists(a)zopyx.com> wrote: > > > --On 9. Mai 2006 17:32:06 -0700 Alec Mitchell <apm13(a)columbia.edu> wrote: > > > On 5/9/06, Andreas Jung <lists(a)zopyx.com> wrote: > >> Hi, > >> > >> I plan to release Zope 2.9.3 by this weekend. The release contains > >> some important fixes and a Five update. Any objections? > > > > Sounds good to me, any chance of a new 2.8 release as well? Or is 2.8 > > completey 100% dead already. > > I'll have to look at the changelog first... My main concern is that the traversal security issue which affects any object that tries to acquire attributes and has been marked five:traversable (thankfully this nonsense is gone in 2.10) was a problem for both 2.8 and 2.9. Unless there's a 2.8 with that fix, Plone 2.5 will not be able to run on Zope 2.8. Though this would doubtlessly make a few people happy, the Plone Windows installer apparently needs to use 2.8 unless the Plone release is heavily delayed to get the installer woking with Python 2.4/Zope 2.9. Alec

1 0

Re: [Zope-dev] Zope 2.9.3 release
by Alec Mitchell 10 May '06

10 May '06

On 5/9/06, Andreas Jung <lists(a)zopyx.com> wrote: > Hi, > > I plan to release Zope 2.9.3 by this weekend. The release contains > some important fixes and a Five update. Any objections? Sounds good to me, any chance of a new 2.8 release as well? Or is 2.8 completey 100% dead already. Alec

3 2

Zope 2.9.3 release
by Andreas Jung 09 May '06

09 May '06

Hi, I plan to release Zope 2.9.3 by this weekend. The release contains some important fixes and a Five update. Any objections? Andreas

1 0