[Python-Dev] Trickery with moving urllib (original) (raw)

Brett C. bcannon at gmail.com
Sun May 11 19:42:37 CEST 2008

-Brett [from his iPod touch]

On 10-May-08, at 23:58, "Alexandre Vassalotti" <alexandre at peadrop.com>
wrote:

On Sat, May 10, 2008 at 11:38 PM, Brett Cannon <brett at python.org> wrote:

I see three solutions for dealing with this.

1. Have stubs for the entire urllib API in urllib.init that raise a DeprecationWarning either specifying the new name or saying the function/class is deprecated. 2. Rename urllib to urllib.fetch or urllib.oldrequest to get people to move over to urllib.request (aka urllib2) at some point. I am probably missing something, because I don't see how this solution would solve the problem. The warning in urllib.init will still be issued when people will import urllib.fetch (or urllib.fetch).

No, you are probably right. My brain is mush at the moment.

-brett

-- Alexandre

More information about the Python-Dev mailing list