➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry-scott
Recipients barry-scott, ned.deily, r.david.murray, ronaldoussoren
Date 2015-03-29.11:00:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427626856.47.0.177290166635.issue23797@psf.upfronthosting.co.za>
In-reply-to
Content 
I should point out using Python2.7 with wxPython I do not see this issue.
This issue was exposed during my efforts to port pysvn from py2.7+wxPython to py3.4+wxpython-phoenix.

I do setup locale on the main thread very early before starting the background thread.
I have attached the initLocale() I use.

The background thread needs the locale setup and I use getlocale() to prove that it is setup.

I do not see this as a duplicate of Issue18378 as I can init the locale. 

The problem, and I could believe its an OSX bug, is that new threads do not return the expected locale from _locale.setlocale() for a period of time, approx 2s after starting up.
History
Date User Action Args
2015-03-29 11:00:56barry-scottsetrecipients: + barry-scott, ronaldoussoren, ned.deily, r.david.murray
2015-03-29 11:00:56barry-scottsetmessageid: <1427626856.47.0.177290166635.issue23797@psf.upfronthosting.co.za>
2015-03-29 11:00:56barry-scottlinkissue23797 messages
2015-03-29 11:00:56barry-scottcreate