I agree that wxPython's decision to require specialized handling of locale seems a little questionable, but they may have had good reasons (I didn't look into them). I used wx.LANGUAGE_DEFAULT because it is supposed to derive the OS' locale and at the time I was thinking this was what the code was trying to achieve - but of course variances can be added as needed. Storing the Locale object as an attribute of uiApp should avoid garbage collection issues, unless there is locale-dependent code after the App object is destroyed.
On February 4, 2015 10:03:45 AM PST, Paul McNett <[email protected]> wrote: >On 2/4/15 9:10 AM, john wrote: >> >> On 02/04/2015 07:57 AM, Paul McNett wrote: >>> One thing that may bite us is if the existing locale is garbage >>> collected but then the new language isn't supported, perhaps (not >sure >>> here) we should just use whatever the existing locale is instead of >>> defaulting to wx's default. >> But then wxPython still requires that it be setup???? > >Yeah I guess wxPython is taking the stand of 'if you use me, you deal >with locale issues the way I want you to'. > >So please continue. :) > >Paul > > >_______________________________________________ >Post Messages to: [email protected] >Subscription Maintenance: >http://mail.leafe.com/mailman/listinfo/dabo-users >Searchable Archives: http://leafe.com/archives/search/dabo-users >This message: >http://leafe.com/archives/byMID/[email protected] --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
