Guido van Rossum wrote: > Jyrki's solution: use isprint(), which makes it locale-dependent. > I can live with this. >=20 > It needs a Py_CHARMASK() call but otherwise seems to be fine. >=20 > Anybody got an opinion on this? I'm +0. I would even be +0 on a > similar patch for unicode strings (once the ASCII proposal is > implemented). does ctype-related locale stuff really mix well with unicode? if yes, -0. if no, +0. (intuitively, I'd say no -- deprecate in 1.6, remove in 1.7) (btw, what about "eval(repr(s)) =3D=3D s" ?) </F>
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