[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric V. Smith added the comment: I'm closing this as "won't fix" for the negative indexing functionality. If someone wants to open an new documentation issue (and ideally provide a PR), that would be welcome. -- resolution: -> wont fix stage: needs patch -> resolved status: open ->

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Raymond Hettinger added the comment: I recommend not adding support for negative indexing to format() for accessing positional arguments. There is almost no reason to do this because it almost always makes the format string less readable, because the number of arguments is always known in a

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Irit Katriel added the comment: Reproduced on 3.11, and the error message is a little weirder now: >>> "{0[-1]}".format('fox') Traceback (most recent call last): File "", line 1, in TypeError: string indices must be integers, not 'str' -- nosy: +iritkatriel versions: +Python 3.11 -

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Ilya Kamenshchikov added the comment: Py3.6+ f-strings support any indexing as they actually evaluate python expressions. >>> a = ['Java', 'Python'] >>> var = f"Hello {a[-1]}" Hello Python -- nosy: +Ilya Kamenshchikov ___ Python tracker

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric V. Smith added the comment: I'm not sure where (or if) it's defined in the Python docs, but in PEP 3101 it's in https://www.python.org/dev/peps/pep-3101/#simple-and-compound-field-names: "It should be noted that the use of 'getitem' within a format string is much more limited than its

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Éric Araujo added the comment: A side question: where is it defined that in `{thing[0]}`, 0 will be parsed as an integer? The PEP shows `{thing[name]}` and mentions that this is not Python but a smaller mini-language, with `name` always a string, no quotes needed or permitted. -- _

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Marco Buttu added the comment: The error message is misleading: >>> s = '{names[-1]} loves {0[1]}' >>> s.format(('C', 'Python'), names=('Dennis', 'Guido')) Traceback (most recent call last): ... TypeError: tuple indices must be integers or slices, not str -- nosy: +marco.buttu

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Mark Lawrence added the comment: msg216038 suggests three options for the doc patch, does anybody have any preference or a better alternative? -- nosy: +BreamoreBoy ___ Python tracker __

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Terry J. Reedy added the comment: The doc bug is that the grammar block uses 'integer' (linked to https://docs.python.org/3/reference/lexical_analysis.html#grammar-token-integer) in arg_name ::= [identifier | integer] element_index ::= integer | index_string when it should us

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Terry J. Reedy : -- assignee: docs@python -> terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Eric V. Smith : -- assignee: eric.smith -> docs@python nosy: +docs@python ___ Python tracker ___ ___ Python-bugs-list mailin

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Terry J. Reedy added the comment: Either leading sign, '+' or '-', cause string interpretation, so I think 'unsigned integer' should be the term in the doc. >>> '{0[-1]}'.format({'-1': 'neg int key'}) 'neg int key' >>> '{0[+1]}'.format({'+1': 'neg int key'}) 'neg int key' >>> '{0[+1]}'.format([

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Mark Lawrence added the comment: Todd's patch strikes me as fine. If something more detailed is needed I think it would be better to raise a separate issue. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Todd Rovito added the comment: Here is a simple patch that simply explains negative indexes and negative slices are not supported for the string format documentation. Perhaps more documentation needs to be created else where to help explain why all collections do not need to support negative

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Todd Rovito : -- nosy: +Todd.Rovito ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Raymond Hettinger : -- components: +Documentation -Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Éric Araujo added the comment: Thank you for the detailed argument, Raymond. I’m +1 on turning this into a doc bug. -- ___ Python tracker ___ __

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Raymond Hettinger added the comment: After more thought, I'm -1 on this. "Consistency" is a weak argument in favor of this. We need to be more use case drivenm and it there is no evidence that this is needed. Also, there is a reasonable concern that using negative indices in a format strin

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Florent Xicluna : -- nosy: +flox ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: I agree with Kamil and Germán. I would've expected negative indexes for sequences to work. Negative indexes for fields is a different matter. -- ___ Python tracker __

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Raymond Hettinger added the comment: Fixing-up str formatting idiosyncracies does not fall under the moratorium and is helpful in getting 3.x to be usable. That being said, I'm not convinced that this is actually a helpful feature. Not all objects supporting __getitem__ offer support for neg

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Terry J. Reedy added the comment: I believe this is covered by the PEP3003 3.2 change moratorium. -- nosy: +terry.reedy versions: +Python 3.3 -Python 3.2 ___ Python tracker ___ _

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Germán L. Osella Massa added the comment: Well, using negative indexes for fields can be thought as a new feature with all the consequences mentioned before BUT negative indexes for accessing elements from a sequence, IMHO, is something that anyone would expected to work. That's why at first

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Kamil Kisiel added the comment: While I agree this functionality isn't strictly necessary I think it makes sense from a semantic point of view. I ran in to this issue today while writing some code and I simply expected the negative syntax to work, given that the format string syntax otherwise

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric Smith added the comment: I agree with Raymond. I'm not convinced it allows you to write any code that you can't currently write, and I'm fairly sure it violates the moratorium. Implementing this would clearly put a burden on other implementations. Marking as "after moratorium".

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Raymond Hettinger added the comment: Perhaps this ought to be discussed on python-ideas or python-dev for a bit. It is not entirely clear that this is a GoodThingToDo(tm) nor is it clear that we want other Python implementations to have to invest the same effort. The spirit of the language f

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Germán L. Osella Massa added the comment: I forgot to mention that I also made a patch against py3k (was the same code). -- ___ Python tracker ___ ___

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Germán L. Osella Massa : Added file: http://bugs.python.org/file17713/format_negative_indexes-3.2.diff ___ Python tracker ___ ___ Py

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Germán L. Osella Massa added the comment: I finally managed to get the time to finish the patch that allows negative indexes inside square brackets so now they work with the same semantics as in a python expression: >>> '{0[-1]}'.format(['abc', 'def']) 'def' >>> '{0[-2]}'.format(['abc', 'def'

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: Your original: "{0[-1]}".format('fox') is a worse gotcha than: "{-1}".format('fox') because you're much less likely to want to do the latter. It's one of those things that it would be nice to have fixed, or we could just add a warning to the docum

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric Smith added the comment: I can see the point of allowing negative indices for a consistency point, but is there really any practical problem that's currently causing people hardship that this would solve? As for the rest of it, I think it's just not worth the additional burden on CPytho

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: That's a good question. :-) Possibly just an optional sign followed by one or more digits. Another possibility that occurs to me is for it to default to positional if it looks like an integer, but allow quoting to force it to be a key: >>> "{0}".format("foo

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Mark Dickinson added the comment: Matthew: would that include allowing whitespace, then? >>> int('\t\n+56') 56 -- ___ Python tracker ___ ___

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: Re: msg107776. If it looks like an integer (ie, can be converted to an integer by 'int') then it's positional, otherwise it's a key. An optimisation is to perform a quick check upfront to see whether it starts like an integer. -- __

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric Smith added the comment: Addressing just the last part of Mark's message right now: The PEP goes on to say: Implementation note: The implementation of this proposal is not required to enforce the rule about a simple or dotted name being a valid Python identifier. ... I rely o

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Mark Dickinson added the comment: I (reluctantly) agree it's surprising that "{0[-1]}".format(args) fails. And I suppose that if it were allowed then it would also make sense to consider "{-1}".format(*args) as well, in order to preserve the equivalence between "{n}".format(*args) and "{0[n]

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Eric Smith : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Eric Smith added the comment: Closed issue 8985 as a duplicate of this; merging nosy lists. -- nosy: +gosella, mark.dickinson, merwok ___ Python tracker ___ _

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Changes by Eric Smith : -- versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

Matthew Barnett added the comment: On a related note, this doesn't work either: >>> "{-1}".format("x", "y", "z") Traceback (most recent call last): File "", line 1, in "{-1}".format("x", "y", "z") KeyError: '-1' It could return "z". It also rejects a leading '+', but that would be opti

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?

New submission from Eric Smith : It surprised me that this doesn't work: >>> "{0[-1]}".format('fox') Traceback (most recent call last): File "", line 1, in TypeError: string indices must be integers I was expecting it to be equivalent to: >>> "{0[2]}".format('fox') 'x' I don't think there's