mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-08-01 07:33:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

fix markup

Browse source
This commit is contained in:
Benjamin Peterson 2009-04-11 20:27:15 +00:00
parent e753abdec7
commit aa0a0b9007
1 changed files with 9 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

19
Doc/whatsnew/2.7.rst
View file

@ -88,22 +88,21 @@ Other Language Changes
Some smaller changes made to the core Python language are:
* The string :method:`format` method now supports automatic numbering
of the replacement fields. This makes using :meth:`format`
more closely resemble using ``%s`` formatting::
* :meth:`str.format` method now supports automatic numbering of the replacement
fields. This makes using :meth:`str.format` more closely resemble using
``%s`` formatting::
>>> '{}:{}:{}'.format(2009, 04, 'Sunday')
'2009:4:Sunday'
>>> '{}:{}:{day}'.format(2009, 4, day='Sunday')
'2009:4:Sunday'
The auto-numbering takes the fields from left to right, so the first
``{...}`` specifier will use the first argument to :meth:`format`,
the next specifier will use the next argument, and so on. You can't
mix auto-numbering and explicit numbering -- either number all of
your specifier fields or none of them -- but you can mix
auto-numbering and named fields, as in the second example above.
(Contributed by XXX; :issue`5237`.)
The auto-numbering takes the fields from left to right, so the first ``{...}``
specifier will use the first argument to :meth:`str.format`, the next
specifier will use the next argument, and so on. You can't mix auto-numbering
and explicit numbering -- either number all of your specifier fields or none
of them -- but you can mix auto-numbering and named fields, as in the second
example above. (Contributed by XXX; :issue`5237`.)
* The :func:`int` and :func:`long` types gained a ``bit_length``
method that returns the number of bits necessary to represent