Re: [Zope-dev] Zope Tests: 42 OK, 12 Failed
Am 21.09.2010 um 15:43 schrieb Hanno Schlichting: On Tue, Sep 21, 2010 at 3:39 PM, Michael Howitz m...@gocept.com wrote: @Hanno: Could you please decide in the ZTK release team, whether zope.testing 3.10 is a goal for the ZTK trunk. If so, I could merge the branch to the trunk and we could start fixing the tests. But maybe we should do this after the 1.0 final release. It's a goal for ZTK 1.1 (trunk) to use zope.testing 3.10 / zope.testrunner. It's definitely outside the scope for ZTK 1.0. If we already have lots of failing tests in the current state on trunk anyways, I'd be fine with you going ahead and merging the branch. We can fix all the other packages in the coming days. If we have an almost stable trunk, I'd prefer the work to be done on a branch first and only get it merged once the tests pass again. Okay, then I'll do the work on the branch as the trunk currently seems to be quite stable. There seems to be only the zope.app.authentication vs. zope.app.securitypolicy issue left to be fixed on trunk. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On 21/09/2010 23:59, Marius Gedminas wrote:
On Tue, Sep 21, 2010 at 07:39:46PM +0100, Chris Withers wrote:
So, would anyone object if I change the default, on both trunk and the
2.12 branch to some variant of:
class BasicEncodingConflictResolver(object):
implements(IUnicodeEncodingConflictResolver)
def resolve(self, context, text, expression):
logging.warn('You should register an '
'IUnicodeEncodingConflictResolver that matches '
'your content')
return text.decode('ascii','replace')
...and delete that devil spawn turd that is PreferredCharsetResolver?
If this means Zope2-the-application becomes unusable out of the box if
you've non-ASCII data in your database, then I'm -1.
I'd call having the odd '?' shown in pages and a warning in your logs
telling you about the problem in clear terms versus sporadic total
failures by way of unicode exceptions a lot more usable, rather than the
current situation, which is conceptually insane *and* unusable ;-)
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On 22/09/2010 03:50, Andreas Jung wrote:
I also strongly object such a change in the default behavior.
I'm sorry, but WHAT?
I did a
lot of testing of the current implementation and configuration with
various browsers and Zope applications and add-ons in order to make the
Zope 3 ZPT engine in Zope 2 work out-of-the-box for most applications.
Er, you can't be serious...
The idea of asking the user agent what encoding is used to encode data
in the database is like telling an obese person they can have their foot
amputated in order to lose weight.
A less insane version of that default would be:
class BasicEncodingConflictResolver(object):
implements(IUnicodeEncodingConflictResolver)
def resolve(self, context, text, expression):
logging.warn('You should register an '
'IUnicodeEncodingConflictResolver that matches '
'your content')
encodings = ['utf-8','latin-1']
mpc = getattr(context,'management_page_charset',None)
if mpc:
encodings.insert(0,mpc)
for enc in encodings:
try:
return unicode(text,enc)
except UnicodeDecorError:
pass
return unicode(text,sys.getdefaultencoding(),'replace')
However with the given constraints there will be always applications or
bad written code
PreferredCharsetResolver *is* bad code.
I'll say it again, 'cos the message doesn't seem to be getting through:
What on earth do the character sets accepted by the browser have to do
with the python string encoding used in the data on the server, which up
until that request, most likely has never been anywhere near that
browser before?!
resolver. That's why it is pluggable.
Yes, and well documented and advertised too... not!
existing resolver smarter and more efficient: +1 for tuning the
implementation but the proposed solution above does not solve anything
and will break a bunch of apps.
bull crap.
Chris
--
Simplistix - Content Management, Batch Processing Python Consulting
- http://www.simplistix.co.uk
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
Am 22.09.2010, 10:24 Uhr, schrieb Chris Withers ch...@simplistix.co.uk: I'd call having the odd '?' shown in pages and a warning in your logs telling you about the problem in clear terms versus sporadic total failures by way of unicode exceptions a lot more usable, rather than the current situation, which is conceptually insane *and* unusable Next Wednesday is bug day - a good chance for a concerted operation on this. Chris, your description that the current implementation contravenes interface specification means that it is a bug. But no change should simply break existing applications. Can we come up with some tests (ZODB data and presumably client encodings) and a workaround to enable the fudge? I don't know how much non-ASCII you have but the odd ? might turn out to be quite a lot for some people. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On 21/09/2010 21:18, Andreas Jung wrote: I can not recall all details but at the time of the integration of the Zope 3 ZPT engine the unicode resolver approach was the best thinkable solution for dealing all possible edgecase where encoding issues may pop *for the sake of backwards compatibility* ...where it miserably failed. The projects I've hit this on have all been running flawlessly on Zope 2.1(ish) through to Zope 2.9. Zope 2.11 onwards, in my experience, phail, spectacularly... Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
On 22/09/2010 03:50, Andreas Jung wrote:
I also strongly object such a change in the default behavior.
I'm sorry, but WHAT?
I did a
lot of testing of the current implementation and configuration with
various browsers and Zope applications and add-ons in order to make the
Zope 3 ZPT engine in Zope 2 work out-of-the-box for most applications.
Er, you can't be serious...
The idea of asking the user agent what encoding is used to encode data
in the database is like telling an obese person they can have their foot
amputated in order to lose weight.
A less insane version of that default would be:
class BasicEncodingConflictResolver(object):
implements(IUnicodeEncodingConflictResolver)
def resolve(self, context, text, expression):
logging.warn('You should register an '
'IUnicodeEncodingConflictResolver that matches '
'your content')
encodings = ['utf-8','latin-1']
mpc = getattr(context,'management_page_charset',None)
if mpc:
encodings.insert(0,mpc)
for enc in encodings:
try:
return unicode(text,enc)
except UnicodeDecorError:
pass
return unicode(text,sys.getdefaultencoding(),'replace')
However with the given constraints there will be always applications or
bad written code
PreferredCharsetResolver *is* bad code.
I'll say it again, 'cos the message doesn't seem to be getting through:
What on earth do the character sets accepted by the browser have to do
with the python string encoding used in the data on the server, which up
until that request, most likely has never been anywhere near that
browser before?!
resolver. That's why it is pluggable.
Yes, and well documented and advertised too... not!
existing resolver smarter and more efficient: +1 for tuning the
implementation but the proposed solution above does not solve anything
and will break a bunch of apps.
bull crap.
Chris
Please calm down - I am not up to reply to a posting written in a tone
that is even far beyond my personal style when ranting on other peoples
crap.
As said: the discussion is documented in some Launchpad ticket.
If you think it is crap then I cam happy to accept that (and I don't
mind much because Zope 2 is not my radar right now). You are committer
and you can fix my crap. Blame me for having written this crap but you
could also blame me for having on this whole Zope 3 ZPT engine
integration :-)
Cheers,
Andreas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQGUBAEBAgAGBQJMmcU5AAoJEADcfz7u4AZj1wMLvRQ9riRMebLtqZe4VY9U0SCg
v8S8uS/gZXvBDlDodoNoPurumWGlabCXORD5GRgVZhGiSub1GmTXqslHD5Hro1xf
FeGr3skMlTlAis9xjH3qUuBUbivk5+ebk75ii/jPKJmxRg87a3Gwhi1eFnnCZBTg
AGWzYu5QFmKI/iHgWpYjdQiJ1fS2MtRrisF6JCVuduBJs3kenHAV8huw8/7azv6l
uI/tUQjg2N49s14NWZbIObe/cDY6SkSoiu4ifINTJX68aJxgywVqzGu1aiqR33t3
/j2v347/4TCwdfJGFBopvHLBdoI0WIHA4DB9C2VMuAYO/eOQSrH84gGLqbWeRBku
tfh7KqLa5mulyufXVc3YtgF14rk2kJ5TvRohM4YuR1RFB/0WGU6p0FzD8KZ23pB+
CXk9puJi/FTsIO+eSgDcuPZhoc6ZJoPgA2s03TD+8ghspnWSXU4hbZ2DncYzlDOu
Ss+ri+thcf5APSrvfCb4B7xLq/tW2do=
=yS8z
-END PGP SIGNATURE-
attachment: lists.vcf___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On 22/09/2010 09:58, Andreas Jung wrote: If you think it is crap then I cam happy to accept that (and I don't mind much because Zope 2 is not my radar right now). You are committer and you can fix my crap. Blame me for having written this crap but you could also blame me for having on this whole Zope 3 ZPT engine integration :-) Can you please answer me one thing though: in what way could it ever be a good idea to consult the browser's list of acceptable character sets to decide how to decode python strings into python unicode objects in a database that the browser has never had anything to do with? Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: On 21/09/2010 21:18, Andreas Jung wrote: I can not recall all details but at the time of the integration of the Zope 3 ZPT engine the unicode resolver approach was the best thinkable solution for dealing all possible edgecase where encoding issues may pop *for the sake of backwards compatibility* ...where it miserably failed. The projects I've hit this on have all been running flawlessly on Zope 2.1(ish) through to Zope 2.9. Zope 2.11 onwards, in my experience, phail, spectacularly... Sorry, not my problem! The Zope 3 ZPT engine together with the resolver is now available for at least two or three yearswe had a *very long* beta phase for the ZPT integration..have you tested? Obviously no...blaming me for doing a lot of testing while having seen zero contributions in terms of code and testing in this particular case is laughable. Such allegations were one of the reasons for quitting as Zope 2 release manager. If the release manager is the idiot doing the dirty work and taking the beating from people not contributing to the project that I was happy being the Zope 2 idiot for years but I am no longer interested dealing with a minority of people knowing better and constantly playing the niggler. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMmcdSAAoJEADcfz7u4AZjn+4LvA2JtT++GJD+taeZZ+B95UGt fB7fINT1nUyXNWxDV6OyoZd2zgJoCX2Yg3V3FibVaz5uiQjGNkZnPvLooLP+9ESn lSyc6D7tYgHzPhNU/OitwUp8pjZeOWhLXShR0PH1TVtv9I8PAx/0NRDNZDLpE9Cx v1TbTlRztY+crRDkGK4xf9runTNZwVw5yyBk6NJXnKr1yMIOhZ72Fz0LAReiIHq0 vkgSakS7vhYde2acsPi4lXC4lS6s7T67/GjbcPWQAtUw4f4Xc4linYERvFCHUYOT w4z2CDahhyu7ZTfzguGCuUEQZAffi9OlY5LbFlXMSF9crFjrCrqxvPhGmAQXN5O+ z6tYlAXGCZpuV3gMNIPjJBej6UujYP/mnjT8SC5BYkGlYrriNfoBttVynK5TJpMk z5s90fDZa4hETaIXAxTkpCiBfX0IFUp7aqb+lU7HsSs4rHj331cknbemX/iq+S7O ohb5SMgDqJg20UTxxNFH/2ZLSdWsOm8= =Wyxr -END PGP SIGNATURE- attachment: lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: On 22/09/2010 09:58, Andreas Jung wrote: If you think it is crap then I cam happy to accept that (and I don't mind much because Zope 2 is not my radar right now). You are committer and you can fix my crap. Blame me for having written this crap but you could also blame me for having on this whole Zope 3 ZPT engine integration :-) Can you please answer me one thing though: in what way could it ever be a good idea to consult the browser's list of acceptable character sets to decide how to decode python strings into python unicode objects in a database that the browser has never had anything to do with? Check with Launchpad - neither I can remember the details nor am I interested right now thinking about. There were reasons *and* real-world tests with browsers obviously required that. As said: the encoding handling is a game you can only lose inside Zope 2. - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMmcfoAAoJEADcfz7u4AZjQ90LwLQoiWZzKwnLhYJBaO/j4Hs5 RXxURlWAPX2VB1iNbzmzZgadffYdF4Tigmh/kuZFZwZLizJw+SnYwPwJJgAHM/dn aq2Q9JV3atjlu0p/OGe/54BY5ZfMWSE/AjS2gKSJExNdp9rKZbvOdKWg/J+utzq3 M/U7E2AXvOtG3YWZYggQF1QZlY3PZu08XlXHUCNdiK3fAu9dtJQstRGGdggdxhuQ QiheKAs2Tu/hKWsVPURlxes9zGtylpDAQxt5ycRxTxYToJyCQtFdSzBsbLC1rkGG fMDOOL/fPR3UlTzyhvB87ugaiBH7owng+n8tia3Ro06LzGp0oy5PdytrhfQ2BGn2 RzPre7tGavUFn6sxYSEZ6akIuHwk1KQgvMFN2ngsa/F1N1xqZpQUXwF1ALrEFzWc qg4CeO4UDdkh1V8ZlawbKgbih/0eaNYKreCg0vCb2xNqXvsl5OL0QERj0v4u/gWp pJ1zGB+BVHbtZifhHSHkKYmx9Dgpl3I= =EwM7 -END PGP SIGNATURE- attachment: lists.vcf___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] buildbots should have an svn info step
On Wed, Sep 22, 2010 at 00:54, Marius Gedminas mar...@gedmin.as wrote: On Tue, Sep 21, 2010 at 04:33:35PM +0200, Adam GROSZER wrote: Hello Patrick, Could you nag the buildbot maintainers to add an svn info step for their bots? The issue is that you can get the svn URL only from the bot config, which is not always available. Patrick asked me a while ago to switch to using mode='clobber', which means the initial checkout step always does an rm -rf followed by an svn checkout with the full URL. Yes, but some rightfully objected that creates lots of traffic. I think it would be nice if everybody sweeps their slaves contents once in a while, like weekly. I also really like the svn info step. I have seen ccomb has something a bit more advanced, but I have to check that again. Apart from that, I think it was your idea, that everybody should try to trigger their buildbots at the same time, like midnight GMT. That sounds also good. Next week I will go through the current buildbot list and collect some more information, and contact each one individually. This week I won't find the time. Best regards, Patrick Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkyZN4YACgkQkVdEXeem14/m4ACePID0XyNjE8oWd+LwxAjACQg1 dZ8An3m61AwCgwkdlUk+m2yGW4p2h01t =5+MJ -END PGP SIGNATURE- ___ Zope-Dev maillist - zope-...@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope ) signature.asc Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 34 OK, 13 Failed, 3 Unknown
Summary of messages to the zope-tests list. Period Tue Sep 21 12:00:00 2010 UTC to Wed Sep 22 12:00:00 2010 UTC. There were 50 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 21 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 8 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Sep 21 09:14:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020354.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Sep 21 09:15:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020355.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 16:45:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020358.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Sep 21 16:55:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020359.html Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:34:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020366.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Sep 21 19:18:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020369.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Sep 21 19:44:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020371.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Tue Sep 21 23:15:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020388.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Tue Sep 21 23:15:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020389.html Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Tue Sep 21 23:15:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020390.html Subject: FAILED : ZTK 1.0 / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Wed Sep 22 01:42:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020396.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Sep 22 04:39:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020402.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Sep 22 04:45:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020403.html Unknown --- Subject: UNKNOWN : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 16:35:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020357.html Subject: UNKNOWN : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 17:20:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020360.html Subject: UNKNOWN : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Sep 21 17:46:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020361.html Tests passed OK --- Subject: OK : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 10:51:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020356.html Subject: OK : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 17:55:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020362.html Subject: OK : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:04:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020363.html Subject: OK : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:13:30 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020364.html Subject: OK : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:22:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020365.html Subject: OK : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:46:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020367.html Subject: OK : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 18:59:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020368.html Subject: OK : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Sep 21 19:31:42 EDT 2010 URL:
Re: [Zope-dev] Zope Tests: 34 OK, 13 Failed, 3 Unknown
Am 22.09.2010 um 13:58 schrieb Zope Tests Summarizer: Summary of messages to the zope-tests list. Period Tue Sep 21 12:00:00 2010 UTC to Wed Sep 22 12:00:00 2010 UTC. There were 50 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 21 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 8 from jdriessen at thehealthagency.com. Test failures - [...] Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Tue Sep 21 23:15:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020388.html This failure is due to missing zope.generations which is needed by zope.app.generations 3.7. So I switched to a maintenance branch of zope.app.generations. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On Wed, Sep 22, 2010 at 09:34:59AM +0100, Chris Withers wrote:
On 22/09/2010 03:50, Andreas Jung wrote:
I also strongly object such a change in the default behavior.
I'm sorry, but WHAT?
I did a
lot of testing of the current implementation and configuration with
various browsers and Zope applications and add-ons in order to make the
Zope 3 ZPT engine in Zope 2 work out-of-the-box for most applications.
Did various browsers include Safari and MSIE, I wonder? Because those
are the ones causing me pain and UnicodeDecodeErrors.
A less insane version of that default would be:
class BasicEncodingConflictResolver(object):
implements(IUnicodeEncodingConflictResolver)
def resolve(self, context, text, expression):
logging.warn('You should register an '
'IUnicodeEncodingConflictResolver that matches '
'your content')
encodings = ['utf-8','latin-1']
mpc = getattr(context,'management_page_charset',None)
if mpc:
encodings.insert(0,mpc)
for enc in encodings:
try:
return unicode(text,enc)
except UnicodeDecorError:
pass
return unicode(text,sys.getdefaultencoding(),'replace')
I would prefer this to current implementation.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] IUnicodeEncodingConflictResolver moronosity
On Wed, Sep 22, 2010 at 09:24:11AM +0100, Chris Withers wrote: On 21/09/2010 23:59, Marius Gedminas wrote: If this means Zope2-the-application becomes unusable out of the box if you've non-ASCII data in your database, then I'm -1. I'd call having the odd '?' shown in pages and a warning in your logs telling you about the problem in clear terms versus sporadic total failures by way of unicode exceptions a lot more usable, rather than the current situation, which is conceptually insane *and* unusable ;-) There are people who install Zope 2 and then build their websites through the web exclusively. Asking them to figure out how to write and register a utility when they upgrade their 2.12 Zope site to 2.13 is a bit too much, in my opinion. Why replace a bad situation with a different bad situation? How would you like a piece of software that r?pl?c?d ?ll th? v?w?ls w?th q??st??n m?rks ??t ?f th? b?x unless you did a highly technical voodoo dance under the hood? I would be happy with the other version you pasted in this thread, the one that tries context.management_page_charset, UTF-8, and Latin-1. Let's do that instead. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 34 OK, 13 Failed, 3 Unknown
2010/9/22 Michael Howitz m...@gocept.com: Am 22.09.2010 um 13:58 schrieb Zope Tests Summarizer: Summary of messages to the zope-tests list. Period Tue Sep 21 12:00:00 2010 UTC to Wed Sep 22 12:00:00 2010 UTC. There were 50 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 21 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 8 from jdriessen at thehealthagency.com. Test failures - [...] Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Tue Sep 21 23:15:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-September/020388.html This failure is due to missing zope.generations which is needed by zope.app.generations 3.7. So I switched to a maintenance branch of zope.app.generations. I would add zope.generations rather than switch to maintenance branch. The independent zope.generations is what contains the code to use by applications. Nothing else apart from the split has changed, compatibility imports and zcml are left in place, so it should be safe to have the two packages in ZTK 1.0. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
