Guido van Rossum wrote:
> def spam(a):
> r = asciistr('(')
> if a: r += a.strip()
> r += asciistr(')')
> return r
>
> The general fix would be to add
>
> else: r += a[:0]
The awkwardness might be reducable if asciistr let
you write something like
r = asciistr('(', a)
meaning "give me either a string or bytes containing
the value '(', depending on the type of a".
But taking a step back, how bad would it really be
if an asciistr were returned in this case? Is it
just that asciistr doesn't behave exactly like a str
in all situations, so it might break something?
If so, would it help if asciistr were a built-in
type, so that other things could be made aware of
it?
--
Greg
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