Message402821
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 shlex.py and added a "wordterminators" member. If "wordterminators" was left blank, then "wordchars" were used instead. This was a trivial change to "shlex.py" and it added a lot of functionality.)
I would like to suggest making this change (or something similar) to the official version of "shlex.py". Would sending an email to "python-ideas@python.org" be a good place to make this proposal? |
|
Date |
User |
Action |
Args |
2021-09-29 07:16:49 | jewett-aij | set | recipients:
+ 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:49 | jewett-aij | set | messageid: <1632899809.51.0.290118555849.issue1170@roundup.psfhosted.org> |
2021-09-29 07:16:49 | jewett-aij | link | issue1170 messages |
2021-09-29 07:16:49 | jewett-aij | create | |
|