[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

[Fred L. Drake, Jr.]

Fred L. Drake, Jr.  added the comment:

The 3.X docs generally don't refer to the 2.X series.

What that comment is pointing out is that leaving the field identifier out (the 
number inside the {...} placeholder syntax) was not in the 3.0, but added in 
3.1.

Unfortunately, I don't have a 3.0 interpreter available to show the exception 
that's raised.

No change is required.

--
nosy: +fdrake
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

[Mitchell L Model]

Change by Mitchell L Model :


--
assignee:  -> docs@python
components: +Documentation
nosy: +docs@python

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue35831] Format Spec example says limited to 3.1+ but works in 2.7

[Mitchell L Model]

New submission from Mitchell L Model :

https://docs.python.org/3/library/string.html#format-examples includes this 
line:

'{}, {}, {}'.format('a', 'b', 'c')  # 3.1+ only

This does in fact work in 2.7. I don't see anything special about this -- seems 
an entirely straightforward format.

--
messages: 334385
nosy: mlm
priority: normal
severity: normal
status: open
title: Format Spec example says limited to 3.1+ but works in 2.7
versions: Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com