funny behaviour gtk+python

[Jean Piché]

Victor,

This seriously look slike a bug we had about a month ago in TamTam. I  
cannot recall the number but hopefully someone else can remeber.

It has to do with the LOCALE env variable and the int/float  
separating character. It was fixed in our pythin code but specifying:

locale.setlocale(locale.LC_NUMERIC, 'C')



_________________________________
http://jeanpiche.com

On 4-Oct-07, at 9:49 AM, Victor Lazzarini wrote:

> Yes setting LANG=C at the console solves the problem. Would
> you care to explain why?
>
> Victor
>
> At 13:15 04/10/2007, Marco Pesenti Gritti wrote:
>> On 10/4/07, Victor Lazzarini <Victor.Lazzarini at nuim.ie> wrote:
>>> (OLPC build 602)
>>> I have been trying a few things here and I stumbled
>>> across a funny problem (this is quite specialised, so
>>> I suppose only a few of you would know):
>>>
>>> 1. With Python, if I do
>>>
>>> import gtk
>>> import csnd
>>>
>>> cs = csnd.Csound()
>>> cs.Compile("myexample.csd")
>>>
>>> the csound compilation will fail with very unusual
>>> syntax errors (which are not syntax errors at all)
>>> (eg: "error: numeric syntax "11.1", line ...")
>>>
>>> 2. If I don't do
>>>
>>> import gtk
>>>
>>> Csound will happily compile my code.
>>>
>>> Now this seems so weird that I can't understand
>>> why it is happening.
>>>
>>> Any clues why "import gtk" is causing this
>>> behaviour?
>>
>> Does running it with LANG=C help?
>>
>> Marco
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20071004/bec0fa8f/attachment.html>