[issue2338] Backport reload() moving to imp.reload()

Brett Cannon <[EMAIL PROTECTED]> added the comment: Done in r65563. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2338] Backport reload() moving to imp.reload()

Brett Cannon <[EMAIL PROTECTED]> added the comment: A fixer is not going to work for this since it might require an import to work. Instead reload() just needs to be added as imp.reload() and the current warning stays. -- assignee: collinwinter -> brett.cannon components: +Extension Modu

[issue2338] Backport reload() moving to imp.reload()

Changes by Collin Winter <[EMAIL PROTECTED]>: -- components: +2to3 (2.x to 3.0 conversion tool) __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bug

[issue2338] Backport reload() moving to imp.reload()

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- priority: immediate -> urgent __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing lis

[issue2338] Backport reload() moving to imp.reload()

Changes by Brett Cannon <[EMAIL PROTECTED]>: -- components: +Interpreter Core -2to3 (2.x to 3.0 conversion tool) __ Tracker <[EMAIL PROTECTED]> __ _

[issue2338] Backport reload() moving to imp.reload()

New submission from Brett Cannon <[EMAIL PROTECTED]>: A fixer to change calls from reload() to imp.reload() needs to happen. Plus imp.reload() should come into existence. -- assignee: collinwinter components: 2to3 (2.x to 3.0 conversion tool) keywords: 26backport messages: 63697 nosy: br