➜

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 ncoghlan
Recipients Robin.Schreiber, amaury.forgeotdarc, asvetlov, benjamin.peterson, brett.cannon, eric.snow, ezio.melotti, loewis, ncoghlan, ned.deily, pitrou, serhiy.storchaka, yselivanov
Date 2015-03-01.06:34:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425191677.59.0.789685270385.issue20204@psf.upfronthosting.co.za>
In-reply-to
Content 
ImportWarning is slightly different - it's aimed at issues that happen during the operation of the import machinery itself.

This isn't that - it's a warning related to the extension module actually initialising itself, so it's akin to a warning issued due to the behaviour of top level module source code, rather than by the import system.
History
Date User Action Args
2015-03-01 06:34:37ncoghlansetrecipients: + ncoghlan, loewis, brett.cannon, amaury.forgeotdarc, pitrou, benjamin.peterson, ned.deily, ezio.melotti, asvetlov, eric.snow, serhiy.storchaka, Robin.Schreiber, yselivanov
2015-03-01 06:34:37ncoghlansetmessageid: <1425191677.59.0.789685270385.issue20204@psf.upfronthosting.co.za>
2015-03-01 06:34:37ncoghlanlinkissue20204 messages
2015-03-01 06:34:37ncoghlancreate