[issue13543] shlex with string ending in space gives ValueError: No closing quotation
ekorn jono...@gmail.com added the comment: https://github.com/ipython/ipython/issues/1109#issuecomment-3072571 It seems this was an IPython bug due to slight abuse of the shlex module. Closing as invalid; thanks for your help. -- resolution: - invalid status: open - closed ___ 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
[issue13543] shlex with string ending in space gives ValueError: No closing quotation
R. David Murray rdmur...@bitdance.com added the comment: And just for your information, as far as I know *no one* knows what standard (or model) non-posix mode shlex is based on. -- ___ 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
[issue13543] shlex with string ending in space gives ValueError: No closing quotation
ekorn jono...@gmail.com added the comment:
FYI, Min RK commented on the IPython issue:
https://github.com/ipython/ipython/issues/1109#issuecomment-3071470
In short,
shlex.shlex('blob f( )', posix=False)
fails, whereas
shlex.shlex('blob f( )', posix=False)
The problem appears to be that Python source obviously doesn't sit well with
non-posix whitespace-split shlex. [...] if you lead all your open-quotes with
whitespace, you should be fine (works for all given examples, at least). [...]
I have no idea whether this is a Python bug or not, since I don't know what the
reference standard is, but this is definitely an IPython bug. We should not be
trying to use shlex to parse Python code as if it were command-line arguments.
--
___
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
[issue13543] shlex with string ending in space gives ValueError: No closing quotation
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
[issue13543] shlex with string ending in space gives ValueError: No closing quotation
Changes by Meador Inge mead...@gmail.com: -- nosy: +meador.inge stage: - needs patch ___ 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
