[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Raymond Hettinger : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Francisco Couzo added the comment: I just made the pull request, I totally forgot I mentioned I was going to work on this, sorry! -- ___ Python tracker ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Francisco Couzo : -- pull_requests: +12602 stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Joannah Nanjekye added the comment: @franciscouzo any status on this? Do you need any help on this? -- ___ Python tracker ___ ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Manuel Cerón : -- nosy: -ceronman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Francisco Couzo added the comment: I'm preparing the PR myself -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Joannah Nanjekye added the comment: @dmzz, You can convert the patch into a PR on github or Open a PR with your own implementation. If working with this same patch, the next step would be to test the patch if it is still in good shape now before opening a PR. -- nosy:

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Carlos Damázio added the comment: Ops, someone already patched it! Sorry guys. -- ___ Python tracker ___ ___ Python-bugs-list

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Carlos Damázio added the comment: I've noticed this issue is quite not active, but I'm up on participating in it if anyone is doing it already. Since then, this issue still persists: >>> '{1}'.format() Traceback (most recent call last): File "", line 1, in IndexError: tuple index out of

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Change by Manuel Cerón : -- nosy: +ceronman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Mariatta Wijaya : -- nosy: +Mariatta ___ Python tracker ___ ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Eric V. Smith : -- assignee: -> eric.smith versions: +Python 3.6 -Python 3.5 ___ Python tracker ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Francisco Couzo : -- nosy: +franciscouzo ___ Python tracker ___ ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Francisco Couzo : -- keywords: +patch Added file: http://bugs.python.org/file44490/format.patch ___ Python tracker ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Tshepang Lekhonkhobe tshep...@gmail.com: -- nosy: +tshepang ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21879 ___ ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Tshepang Lekhonkhobe added the comment: @terry would a change like this be accepted in 2.7 and 3.4? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21879 ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Eric V. Smith added the comment: I don't think we can change the exception type in a bugfix release, if ever. I don't see much point in changing the exception type: it's just churn. I'm +1 for a better error message. I'm -0 on changing the error message in a bugfix release. --

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Terry J. Reedy added the comment: After reading Eric's comments and checking the signature of .format and rereading the Format String Syntax section, I have changed my mind. The signature of .format is S.format(*args, **kwargs) - str and args is a tuple. So the user asks for creation of a

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Changes by Ezio Melotti ezio.melo...@gmail.com: -- components: +Library (Lib) keywords: +easy nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21879 ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

New submission from Roy Smith: https://mail.python.org/pipermail/python-list/2014-June/674188.html -- messages: 221846 nosy: roysmith priority: normal severity: normal status: open title: str.format() gives poor diagnostic on placeholder mismatch ___

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Roy Smith added the comment: (ugh, hit return too soon) '{1}'.format() Traceback (most recent call last): File stdin, line 1, in module IndexError: tuple index out of range This is a confusing error message. The user hasn't written any tuples, so a message about a tuple index out of range

[issue21879] str.format() gives poor diagnostic on placeholder mismatch

Terry J. Reedy added the comment: IndexError should be caught and replaced with something like ValueError('format string requests argument not passed') or TypeError('arguments do not match format string') or more specific TypeError('format string requests at least %d positional arguments, only