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 eric.araujo
Recipients Santiago.Romero, belopolsky, benjamin.peterson, cgwalters, dexen, doughellmann, eric.araujo, ezio.melotti, fperez, loewis, mark.dickinson, mcepl, nwerneck, orsenthil, r.david.murray, rhettinger, vstinner
Date 2011-07-18.14:25:42
SpamBayes Score 0.0003949134
Marked as misclassified No
Message-id <>
We all recognize that ASCII is very much limited and that the real way to work with strings is Unicode.  However, here our hands are tied by our development process: shlex in 2.x does not support Unicode, adding that support would be a new feature, and 2.7 is closed to new features.  If shlex was supposed to support Unicode, then this would be a bug that could be fixed in 2.7, but it’s not.  All we can do is improve the 2.7 doc to show how to work around that (splitting on bytes and then decoding each chunk, for example).
Date User Action Args
2011-07-18 14:25:43eric.araujosetrecipients: + eric.araujo, loewis, rhettinger, mark.dickinson, belopolsky, orsenthil, vstinner, dexen, benjamin.peterson, cgwalters, mcepl, ezio.melotti, doughellmann, r.david.murray, nwerneck, fperez, Santiago.Romero
2011-07-18 14:25:43eric.araujosetmessageid: <>
2011-07-18 14:25:42eric.araujolinkissue1170 messages
2011-07-18 14:25:42eric.araujocreate