Am Samstag, 8. Juli 2006 20:55 schrieb Detlev Offenbach: > On Saturday 08 July 2006 20:04, Andreas Pakulat wrote: > > On 08.07.06 16:01:51, Detlev Offenbach wrote: > > > On Saturday 08 July 2006 13:49, Hans-Peter Jansen wrote: > > > > Sounds like it's i/o encoding related, and then yes, that could > > > > make a difference inside eric. If I remember correctly, eric > > > > sets a different default encoding compared to plain python. > > > > (see site-packages/sitecustomize.py) > > > > > > In the patched sitecustomize.py I only save the reference to the > > > sys.setdefaultencoding function. In the eric3 IDE the encoding is > > > set to whatever was configured by the user. In the debugger > > > client, the default encoding set to a value extracted from the > > > coding line of the script to be executed. I think, this explains > > > the difference. > > > > Found the get_coding() function and "disabled" it (i.e. returned > > latin1), this made it possible to debug my application and I found > > the error. > > > > Detlev do you see any gain in having an option to tell the > > debugclient to return the coding for LANG env variable if a > > checkbox in the configuration is checked? That way I could have > > done this without hacking eric's code, but if you think this is too > > seldom used, I'm not "demanding" such an option ;-) > > > > Andreas > > I'll add a configuration option to the debugger settings to not set > the encoding. In that case the debugger will work with whatever > sys.getdefaultencoding returns.
I'm +1 for this option. It's likely, that encoding problems appear more often in the future until everything settled in utf8 land... Pete _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
