RetroSearch Browse

Tue Sep 21 18:13:38 CEST 2010 · http://mail.python.org/pipermail/python-dev/2010-September/103881.html

On Tue, 2010-09-21 at 23:38 +1000, Nick Coghlan wrote:
> And if this turns out to be a disaster in practice:
> a) on my head be it; and
> b) we still have the option of the DeprecationWarning dance for bytes
> inputs to the existing functions and moving to a parallel API

In the case of urllib.parse, it's entirely safe.  If someone beats you
up over it later, you can tell them to bother "straddlers" in Web-SIG,
as we're the folks who most want the polymorphism in that particular
API.

- C

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2010-September/103881.html below:

[Python-Dev] Supporting raw bytes data in urllib.parse.* (was Re: Polymorphic best practices)