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/131509.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 mojibakeGreg Ewing greg.ewing at canterbury.ac.nz
Tue Jan 14 09:20:27 CET 2014
Guido van Rossum wrote:
> I've now looked at asciistr. (Thanks Glenn and Ethan for the link.)
> 
> Now that I (hopefully) understand it, I'm worried that a text
> processing algorithm that uses asciistr might under hard-to-predict
> circumstances (such as when the arguments contain nothing of interest
> to the algorithm) might return an asciistr instance instead of a str
> or bytes instance,

It seems to me that any algorithm with that property
has a genuine ambiguity as to what it should return
in that case. Arguably, returning an asciistr would
be the *right* thing to do, because that would allow
it to be used as a component of a larger algorithm
that was polymorphic with respect to text/bytes.

-- 
Greg
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