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 doughellmann
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:36:32
SpamBayes Score 0.00034424267
Marked as misclassified No
Message-id <1310999793.41.0.927326823907.issue1170@psf.upfronthosting.co.za>
In-reply-to
Content
Is unicode supported by shlex in 3.x already? It's curious that unicode support is considered a new feature, rather than a bug. I understand wanting to allocate development resources carefully, though. If someone were to prepare a patch, would it even have a chance of being accepted in 2.7?
History
Date User Action Args
2011-07-18 14:36:33doughellmannsetrecipients: + doughellmann, loewis, rhettinger, mark.dickinson, belopolsky, orsenthil, vstinner, dexen, benjamin.peterson, cgwalters, mcepl, ezio.melotti, eric.araujo, r.david.murray, nwerneck, fperez, Santiago.Romero
2011-07-18 14:36:33doughellmannsetmessageid: <1310999793.41.0.927326823907.issue1170@psf.upfronthosting.co.za>
2011-07-18 14:36:32doughellmannlinkissue1170 messages
2011-07-18 14:36:32doughellmanncreate