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 r.david.murray
Recipients Santiago.Romero, belopolsky, benjamin.peterson, cgwalters, cvrebert, dexen, doughellmann, eric.araujo, ezio.melotti, fperez, loewis, mark.dickinson, mcepl, nwerneck, r.david.murray, rhettinger, vstinner
Date 2011-07-13.11:15:42
SpamBayes Score 1.0085e-05
Marked as misclassified No
Message-id <1310555742.98.0.14701689927.issue1170@psf.upfronthosting.co.za>
In-reply-to
Content
This isn't going to get fixed in 2.x (shlex doesn't support unicode in 2.x, and doing so would be a new feature).  In 3.x all strings are unicode, so the problem you are seeing doesn't exist.  This issue is about the broader problem of what counts as a word character when more than ASCII is involved.
History
Date User Action Args
2011-07-13 11:15:43r.david.murraysetrecipients: + r.david.murray, loewis, rhettinger, mark.dickinson, belopolsky, vstinner, dexen, benjamin.peterson, cgwalters, mcepl, ezio.melotti, eric.araujo, doughellmann, nwerneck, cvrebert, fperez, Santiago.Romero
2011-07-13 11:15:42r.david.murraysetmessageid: <1310555742.98.0.14701689927.issue1170@psf.upfronthosting.co.za>
2011-07-13 11:15:42r.david.murraylinkissue1170 messages
2011-07-13 11:15:42r.david.murraycreate