Message223348
Minimal testcase of the problem situation is tokenising (with posix mode on):
''),
Specifically, an empty string, followed by a non-word character, followed by a non-space character. In this case, the token buffer is empty and due to a missing check for (self.posix and quoted), an extra token is consumed and returned in the wrong order:
>>> s = shlex.shlex("'')abc", posix=True)
>>> s.get_token()
'abc'
>>> s.get_token()
')'
>>> s.get_token()
>>>
I have patches to fix this issue in both default and 2.7. I've also checked there are no other occurrences of the same typo. |
|
Date |
User |
Action |
Args |
2014-07-17 16:37:00 | isoschiz | set | recipients:
+ isoschiz |
2014-07-17 16:37:00 | isoschiz | set | messageid: <1405615020.91.0.261812812224.issue21999@psf.upfronthosting.co.za> |
2014-07-17 16:37:00 | isoschiz | link | issue21999 messages |
2014-07-17 16:37:00 | isoschiz | create | |
|