- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message282971
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 | ncoghlan |
|---|---|
| Recipients | Jan Niklas Hasse, abarry, ezio.melotti, methane, ncoghlan, r.david.murray, vstinner |
| Date | 2016-12-12.08:10:29 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1481530230.01.0.696935180359.issue28180@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
From CPython's point of view, glibc behaves the same way (i.e. reporting `ascii` as the preferred encoding for operating system interfaces) regardless of whether the cause is the locale not being set at all, or due to it being explicitly set to the legacy POSIX locale via `LANG=C`. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2016-12-12 08:10:30 | ncoghlan | set | recipients: + ncoghlan, vstinner, ezio.melotti, r.david.murray, methane, abarry, Jan Niklas Hasse |
| 2016-12-12 08:10:30 | ncoghlan | set | messageid: <1481530230.01.0.696935180359.issue28180@psf.upfronthosting.co.za> |
| 2016-12-12 08:10:30 | ncoghlan | link | issue28180 messages |
| 2016-12-12 08:10:29 | ncoghlan | create | |

