Author steve.dower
Recipients brett.cannon, eric.snow, izbyshev, ncoghlan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-12-07.17:25:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481131502.44.0.682797748087.issue28896@psf.upfronthosting.co.za>
In-reply-to
Content
It's not intentional, but we clearly haven't done anything to prevent it.

Arguably this finder should be omitted when you run in isolated mode, and I'm on the fence about deprecating it entirely. Adding the importlib experts in case they have opinions (relevant ones, ideally).

A one line workaround that can be added to any code base is:

>>> sys.meta_path[:] = [m for m in sys.meta_path if m.__name__ != 'WindowsRegistryFinder']

But it would also be good to close off this hole. Thoughts on the best option? (-I, move to site.py and -S, something new...)
History
Date User Action Args
2016-12-07 17:25:02steve.dowersetrecipients: + steve.dower, brett.cannon, paul.moore, ncoghlan, tim.golden, eric.snow, zach.ware, izbyshev
2016-12-07 17:25:02steve.dowersetmessageid: <1481131502.44.0.682797748087.issue28896@psf.upfronthosting.co.za>
2016-12-07 17:25:02steve.dowerlinkissue28896 messages
2016-12-07 17:25:02steve.dowercreate