This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients orsenthil, vstinner, xtreak
Date 2019-07-01.22:50:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562021433.32.0.466419456415.issue37475@roundup.psfhosted.org>
In-reply-to
Content
Hi Victor and Karthikeyan,

Both your analysis are correct.

- This is a legacy interface, present purely for satisfying the old code, when urlretrieve was advertised as the first/easy to way to use urllib and download something.

- At this moment, I think, we should remove those legacy interfaces including urlcleanup. 

- I think, users can easily using urllib to write to the file using context manager and if desired urlretrieve can be modernized over it's use of urlcleanup.

+1 to deprecation and removal.
History
Date User Action Args
2019-07-01 22:50:33orsenthilsetrecipients: + orsenthil, vstinner, xtreak
2019-07-01 22:50:33orsenthilsetmessageid: <1562021433.32.0.466419456415.issue37475@roundup.psfhosted.org>
2019-07-01 22:50:33orsenthillinkissue37475 messages
2019-07-01 22:50:32orsenthilcreate