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 rbcollins
Recipients michael.foord, r.david.murray, rbcollins, vstinner
Date 2014-09-23.00:29:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I can certainly write the reporter glue to work with either a string or a full reference. Note that the existing late-reporting glue captures the import error into a string, and then raises an exception containing that string - so what I've done is consistent with that.

As for why the original code is like that - well I've had plenty of bad experiences with memory loops due to objects held in stack frames of exceptions, I don't like to keep long lived references to them, and I wager Michael has had the same experience.
Date User Action Args
2014-09-23 00:29:05rbcollinssetrecipients: + rbcollins, vstinner, r.david.murray, michael.foord
2014-09-23 00:29:05rbcollinssetmessageid: <>
2014-09-23 00:29:05rbcollinslinkissue19746 messages
2014-09-23 00:29:04rbcollinscreate