A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-February/116869.html below:

[Python-Dev] [Python-checkins] cpython (3.2): Issue #14123: Explicitly mention that old style % string formatting has caveats

[Python-Dev] [Python-checkins] cpython (3.2): Issue #14123: Explicitly mention that old style % string formatting has caveats [Python-Dev] [Python-checkins] cpython (3.2): Issue #14123: Explicitly mention that old style % string formatting has caveatsEli Bendersky eliben at gmail.com
Sun Feb 26 14:05:45 CET 2012
>
> -   The formatting operations described here are obsolete and may go away
> in future
> -   versions of Python.  Use the new :ref:`string-formatting` in new code.
> +   The formatting operations described here are modelled on C's printf()
> +   syntax.  They only support formatting of certain builtin types.  The
> +   use of a binary operator means that care may be needed in order to
> +   format tuples and dictionaries correctly.  As the new
> +   :ref:`string-formatting` syntax is more flexible and handles tuples and
> +   dictionaries naturally, it is recommended for new code.  However, there
> +   are no current plans to deprecate printf-style formatting.
>

Please consider just deleting the last sentence. Documentation is meant for
users (often new users) and not core devs. As such, I just don't see what
it adds. If the aim to to document this intent somewhere, a PEP would be a
better place than the formal documentation.

Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120226/e3ff20de/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4