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 | cfr |
|---|---|
| Recipients | cfr, loewis |
| Date | 2008年07月18日.12:31:56 |
| SpamBayes Score | 0.0014605124 |
| Marked as misclassified | No |
| Message-id | <1216384320.2.0.801541614521.issue3362@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
A work-around when using python from a shell environment (e.g. from a bash shell in Terminal) is to issue export __CF_USER_TEXT_ENCODING=0x1F5:0:0 before starting python. I haven't yet worked out how to apply this to GUI apps. I tried editing ~/.MacOSX/environment.plist and ~/.CFUserTextEncoding but neither strategy prevents the crash. I assume the fix works because it means one of the explicitly listed encodings matches so things never get as far as the code which triggers the error. Without the fix, my environment contained __CF_USER_TEXT_ENCODING=0x1F5:39:79 which does not, apparently, correspond to any of the encodings explicitly listed in _localemodule.c. - cfr |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月18日 12:32:01 | cfr | set | spambayes_score: 0.00146051 -> 0.0014605124 recipients: + cfr, loewis |
| 2008年07月18日 12:32:00 | cfr | set | spambayes_score: 0.00146051 -> 0.00146051 messageid: <1216384320.2.0.801541614521.issue3362@psf.upfronthosting.co.za> |
| 2008年07月18日 12:31:58 | cfr | link | issue3362 messages |
| 2008年07月18日 12:31:57 | cfr | create | |