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/2014-January/131254.html below:

[Python-Dev] PEP 460: allowing %d and %f and mojibake

[Python-Dev] PEP 460: allowing %d and %f and mojibake [Python-Dev] PEP 460: allowing %d and %f and mojibakeKristján Valur Jónsson kristjan at ccpgames.com
Sun Jan 12 03:11:23 CET 2014
No, I don't think it is.
The purpose is to make it easier to work with bytes objects.  There can be no python 2 compatibility when it comes to bytes/unicode conversion.

________________________________________
From: Python-Dev [python-dev-bounces+kristjan=ccpgames.com at python.org] on behalf of Serhiy Storchaka [storchaka at gmail.com]
Sent: Saturday, January 11, 2014 21:01
To: python-dev at python.org
Subject: Re: [Python-Dev] PEP 460: allowing %d and %f and mojibake

11.01.14 21:40, Kristján Valur Jónsson написав(ла):
> How about a compromise?
> Personally, I think adding the full complement of integer/float formatting to bytes is a bit over the top.
> How about just supporting two format specifiers?
> %b : interpolate a bytes object.  If it doesn't have the buffer interface, error.
> %s : interpolate a str object, encoded to ASCII using 'strict' conversion.

%b is not supported in Python 2.7. And compatibility with Python 2.7 is
only the purpose of this feature.
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