[Python-Dev] Trickery with moving urllib (original) (raw)
Alexandre Vassalotti alexandre at peadrop.com
Sun May 11 08:58:26 CEST 2008
- Previous message: [Python-Dev] Trickery with moving urllib
- Next message: [Python-Dev] Trickery with moving urllib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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).
-- Alexandre
- Previous message: [Python-Dev] Trickery with moving urllib
- Next message: [Python-Dev] Trickery with moving urllib
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]