Message131490
| Author |
orsenthil |
| Recipients |
eric.araujo, jhylton, mcjeff, nadeem.vawda, orsenthil, pitrou |
| Date |
2011年03月20日.12:51:40 |
| SpamBayes Score |
0.00029084578 |
| Marked as misclassified |
No |
| Message-id |
<20110320125132.GA27783@kevin> |
| In-reply-to |
<1300623010.3481.4.camel@localhost.localdomain> |
| Content |
Antoine Pitrou wrote:
> Can you clarify the issue?
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?
My thought is, in Python 3.x these may not be in use, but still if we
remove without DeprecationWarning, it could raise concerns with some
folks (given some discussion about this recently when people trying to
upgrade from 2.x to 3.x).
At the moment, urlretrieve function is calling URLopener.retrieve internally.
But this patch addresses urlretrive function at much higher level and leaves
the URLopener.retrieve in a hanging state. So, I was thinking how to
handle this scenario.
Change URLopener.retrieve also with the cleaner and modern code, but
and add a DeprecationWarning in those. |
|