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 terry.reedy
Recipients kbk, martin.panter, roger.serwy, serhiy.storchaka, terry.reedy
Date 2016-05-15.18:16:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463336172.78.0.660263977304.issue25747@psf.upfronthosting.co.za>
In-reply-to
Content
In msg255485 'copied replacements' should be 'copied with replacements'.  But 'import idlever' is not a reliable replacement for "# trigger a warning".

I wonder whether 'import_fresh_module' really executes the module twice, which seems foolish, or mere displays one warning twice.

It doesn't really matter here.  I have decided to remove the test.  We don't know if *anyone* imports idlever, and 3.6 will break nearly all external imports, not just that one, so this particular warning and test are not worth the time already spent on them.
History
Date User Action Args
2016-05-15 18:16:12terry.reedysetrecipients: + terry.reedy, kbk, roger.serwy, martin.panter, serhiy.storchaka
2016-05-15 18:16:12terry.reedysetmessageid: <1463336172.78.0.660263977304.issue25747@psf.upfronthosting.co.za>
2016-05-15 18:16:12terry.reedylinkissue25747 messages
2016-05-15 18:16:12terry.reedycreate