Thanks Johannes and Tres, the trick you both suggested works!
I am forced to use this old product because I'll need to migrate a site (from zope2.10) that is using it. The Calendar product comes from here: http://old.zope.org/Members/teyc/CalendarTag/ Now, that the Calendar works, what should we do with it? Release it again with a new version number, or just forget about it? (It is old, indeed). regards, Giampiero On Mar 27, 2013, at 18:04 13, johannes raggam wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 03/27/2013 04:44 PM, Giampiero Benvenuti wrote: >> Still, one problem is this type of error: >> >> SyntaxError: Non-ASCII character '\xf1' in file >> /Applications/zope21319/Products/Calendar/CalendarTag.py on line >> 139, but no encoding declared; > just place this line on top of the file: > > # -*- coding: utf-8 -*- > > with this, you declare the encoding of the file to be utf-8, which is > probably the encoding you need. http://www.python.org/dev/peps/pep-0263/ > > what you describe sounds as if the Calendar product is not actively > maintained. what usecase do you want to solve? where did you get the > Calendar product from? > > best, > johannes raggam > > > > - -- > programmatic web development > di(fh) johannes raggam / thet > python plone zope development > mail: off...@programmatic.pro > web: http://programmatic.pro > http://bluedynamics.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iEYEARECAAYFAlFTJo0ACgkQW4mNMQxDgAd1UACgrZPkmA6qECH9kqplNG3vAz2N > MNIAn1corxQzogbnr5MHe38SlSSI2xCo > =zNPb > -----END PGP SIGNATURE----- _______________________________________________ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
