Antoine Pitrou <pit...@free.fr> added the comment: > URLopener which is an old class from the merge of urllib and urllib2 > and it can be slowly and safely removed. If we go this line, then I > assume it has to have a DeprecationWarning before we remove it. Should > we or not?
Yes, we should. > Change URLopener.retrieve also with the cleaner and modern code, but > and add a DeprecationWarning in those. Sounds overkill and of questionable interest. Honestly, I don't think URLopener.retrieve() has much point anyway. Perhaps it would have if the whole caching thing had been implemented. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10050> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
