Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
versions: +Python 3.3 -Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7594
___
Mark Hammond mhamm...@users.sourceforge.net added the comment:
I tried to use this in place of shlex for parsing IMAP responses for the
'imapclient' package. A couple of things struck me.
* The class no longer has a next() method but probably should be added for b/w
compat.
* The class no
New submission from Brian Harring ferri...@gmail.com:
Currently, shlex.shlex's internal read_token is a bit of a nasty mess to
follow and pretty poorly performant.
The refactoring I'll be attaching essentially inverts the state machine
approach read_token uses- instead, converting it over to a
Ezio Melotti ezio.melo...@gmail.com added the comment:
Thanks for the patch.
Three minor things:
1) the source contains non-ASCII chars and an encoding declaration at
the beginning of the file. PEP8 says that using \x, \u or \U escapes is
the preferred way to include non-ASCII data in string
