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 jewett-aij
Recipients Santiago.Romero, belopolsky, benjamin.peterson, cgwalters, dexen, doughellmann, eric.araujo, ezio.melotti, fperez, jewett-aij, loewis, mark.dickinson, mcepl, nwerneck, orsenthil, r.david.murray, rhettinger, vstinner, wombat
Date 2021-09-29.07:16:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The error messages may have gone away, but the underlying unicode limitations I mentioned remain:

Suppose you wanted to use shlex to build a parser for Chinese text.  Would you have to set "wordchars" to a string containing every possible Chinese character?

I myself wrote a parser for a crude language where words can contain any character except for whitespace and parenthesis.  I needed a way to specify the characters which cannot belong to a word.  (That's how I solved the problem.  I modified and added a "wordterminators" member.  If "wordterminators" was left blank, then "wordchars" were used instead.  This was a trivial change to "" and it added a lot of functionality.)

I would like to suggest making this change (or something similar) to the official version of "".  Would sending an email to "" be a good place to make this proposal?
Date User Action Args
2021-09-29 07:16:49jewett-aijsetrecipients: + jewett-aij, loewis, rhettinger, mark.dickinson, belopolsky, orsenthil, vstinner, dexen, benjamin.peterson, cgwalters, mcepl, ezio.melotti, eric.araujo, doughellmann, r.david.murray, nwerneck, fperez, Santiago.Romero, wombat
2021-09-29 07:16:49jewett-aijsetmessageid: <>
2021-09-29 07:16:49jewett-aijlinkissue1170 messages
2021-09-29 07:16:49jewett-aijcreate