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 pitrou
Recipients brett.cannon, docs@python, eric.snow, ncoghlan, pitrou, xmorel
Date 2017-06-02.11:36:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <cb1d9ceb-5d75-b2d7-19f7-c662f858b960@free.fr>
In-reply-to <1496402504.94.0.589128231866.issue30535@psf.upfronthosting.co.za>
Content
Le 02/06/2017 à 13:21, Xavier Morel a écrit :
> 
> I spent a few hours trying to understand why our import hooks did not work correctly anymore in 3.5, and I never even considered printing sys.meta_path in an open interpreter, I realised the behavioural change because I ended up printing meta_path after the addition of our custom hooks to make sure they were actually there.

Fair enough. So we can just add a sentence informing readers that
`meta_path`, by default, holds entries to handle the standard kinds of
modules (.py files, extension modules...).
History
Date User Action Args
2017-06-02 11:36:02pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, xmorel, docs@python, eric.snow
2017-06-02 11:36:02pitroulinkissue30535 messages
2017-06-02 11:36:02pitroucreate