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 benjamin.peterson, cgwalters, cvrebert, dexen, eric.araujo, mark.dickinson, mcepl, nwerneck, r.david.murray
Date 2010-07-05.03:38:59
SpamBayes Score 0.0075368863
Marked as misclassified No
Message-id <1278301141.13.0.207178490487.issue1170@psf.upfronthosting.co.za>
In-reply-to
Content
shlex may use unicode in py3k, but since the file still starts with a latin-1 coding cookie and the posix logic hasn't been changed, I suspect that it does not work correctly (ie: does not correctly identify word characters, per msg55969).

It's too late for 2.7 I think, but it seems there is work still to do in py3k.
History
Date User Action Args
2010-07-05 03:39:01r.david.murraysetrecipients: + r.david.murray, mark.dickinson, dexen, benjamin.peterson, cgwalters, mcepl, eric.araujo, nwerneck, cvrebert
2010-07-05 03:39:01r.david.murraysetmessageid: <1278301141.13.0.207178490487.issue1170@psf.upfronthosting.co.za>
2010-07-05 03:38:59r.david.murraylinkissue1170 messages
2010-07-05 03:38:59r.david.murraycreate