New submission from ekorn <jono...@gmail.com>:
It seems shlex fails on processing strings ending in space, causing this bug
that I reported for IPython:
https://github.com/ipython/ipython/issues/1109
Fernando Perez made a minimal example of the problem, quoted below. As he
points out, it would be best to fix this at the source, namely the shlex module.
Python 2.7.2 |EPD 7.1-1 (32-bit)| (default, Jul 3 2011, 15:13:59) [MSC v.1500
32 bit (Intel)] on win32
>>> import shlex
>>> lex = shlex.shlex(' ("a ")', posix=False)
>>> lex.whitespace_split = True
>>> list(lex)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Python27\lib\shlex.py", line 269, in next
token = self.get_token()
File "C:\Python27\lib\shlex.py", line 96, in get_token
raw = self.read_token()
File "C:\Python27\lib\shlex.py", line 172, in read_token
raise ValueError, "No closing quotation"
ValueError: No closing quotation
----------
components: Library (Lib)
messages: 148941
nosy: ekorn
priority: normal
severity: normal
status: open
title: shlex with string ending in space gives "ValueError: No closing
quotation"
type: behavior
versions: Python 2.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue13543>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
