[Python-checkins] r71501 - in python/branches/py3k: Doc/whatsnew/2.7.rst
benjamin.peterson
python-checkins at python.org
Sat Apr 11 22:58:12 CEST 2009
Author: benjamin.peterson
Date: Sat Apr 11 22:58:12 2009
New Revision: 71501
Log:
Merged revisions 71498 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/trunk
........
r71498 | benjamin.peterson | 2009-04-11 15:27:15 -0500 (Sat, 11 Apr 2009) | 1 line
fix markup
........
Modified:
python/branches/py3k/ (props changed)
python/branches/py3k/Doc/whatsnew/2.7.rst
Modified: python/branches/py3k/Doc/whatsnew/2.7.rst
==============================================================================
--- python/branches/py3k/Doc/whatsnew/2.7.rst (original)
+++ python/branches/py3k/Doc/whatsnew/2.7.rst Sat Apr 11 22:58:12 2009
@@ -88,22 +88,21 @@
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
More information about the Python-checkins
mailing list