[issue9377] socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names

[Martin v. Löwis]

Martin v. Löwis <martin at v.loewis.de> added the comment:

> That would be an improvement.  The idea of the patches I posted
> is to combine this with the existing surrogateescape mechanism,
> which handles situations like this perfectly well.

The surrogateescape mechanism is a very hackish approach, and
violates the principle that errors should never pass silently.
However, it solves a real problem - people do run into the problem
with file names every day. With this problem, I'd say "if it hurts,
don't do it, then".

----------
title: socket, PEP 383: Mishandling of non-ASCII bytes in host/domain names -> socket,	PEP 383: Mishandling of non-ASCII bytes in host/domain names

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9377>
_______________________________________