Message158956
I believe Dan meant that the behaviour of shlex.split() now is different from what it was when he first raised the issue (in July 2006). Looking at the default branch of CPython, this is what I see:
Python 3.3.0a2+ (default:ff6593aa8376, Apr 22 2012, 12:39:08)
[GCC 4.3.3] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import shlex
>>> list(shlex.shlex('e;'))
['e', ';']
>>> list(shlex.shlex(">'abc';"))
['>', "'abc'", ';']
Likewise, on the 2.6 branch:
Python 2.6.8+ (unknown, Apr 22 2012, 12:44:43)
[GCC 4.3.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import shlex
>>> list(shlex.shlex('e;'))
['e', ';']
>>> list(shlex.shlex(">'abc';"))
['>', "'abc'", ';']
So from what Dan is saying, it would seem that he is saying that shlex behaviour (before my patch being applied) is different now to how he remembers it - not that the patch introduces any incompatibility.
Still, another set of eyeballs on the patch would be good. |
|
Date |
User |
Action |
Args |
2012-04-22 11:50:46 | vinay.sajip | set | recipients:
+ vinay.sajip, eric.smith, robodan, eric.araujo, r.david.murray |
2012-04-22 11:50:46 | vinay.sajip | set | messageid: <1335095446.4.0.646093883638.issue1521950@psf.upfronthosting.co.za> |
2012-04-22 11:50:45 | vinay.sajip | link | issue1521950 messages |
2012-04-22 11:50:45 | vinay.sajip | create | |
|