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 chaselton
Recipients chaselton, ethan.furman, freakboy3742, r.david.murray, refi64, skrah, vstinner
Date 2015-02-27.15:11:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425049861.74.0.748568639841.issue23496@psf.upfronthosting.co.za>
In-reply-to
Content
Given Stephan's comments regarding Android support I'm beginning to think that I may have bitten off more than I can chew. Is there an option between 'constant work' and 'zero contribution'?

I am not by any means an Android developer so the following is possibly riddled with miconceptions and errata, but, regarding locale support, I think there's a difference between 'regular' and 'native' development.  Native development involves using the NDK to port various bits of C-written utilities and libraries to Android...like python... and it is where the locale is broken, because of Android's limited libc.
History
Date User Action Args
2015-02-27 15:11:01chaseltonsetrecipients: + chaselton, vstinner, r.david.murray, skrah, freakboy3742, ethan.furman, refi64
2015-02-27 15:11:01chaseltonsetmessageid: <1425049861.74.0.748568639841.issue23496@psf.upfronthosting.co.za>
2015-02-27 15:11:01chaseltonlinkissue23496 messages
2015-02-27 15:11:01chaseltoncreate