From: Stefan M. <sm...@oe...> - 2011-06-01 17:52:48
|
Hi Günter! 3 weeks (22 days) ago Guenter Milde wrote: > On 2011-04-25, Stefan Merten wrote: >> Last week (8 days ago) Guenter Milde wrote: >>>> 3 days ago Guenter Milde wrote: >>> I suppose the problem are "implicit" unicode -> str conversions that >>> use the "ASCII, strict" encoding. > >> I thought that, too. But some tests on the command line showed this is >> not the case. It's really the `print` which causes the problem. >> Probably it's there where there is the conversion to ASCII which >> fails. > > With the new ErrorOutput class, error reporting should be failsafe now in > both, Python2 and Python3. Could you test? Sorry for the delay and thanks for the work. My initial case now works with r7032 :-) . Grüße Stefan |