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 eric.snow
Recipients brett.cannon, eric.smith, eric.snow, georg.brandl, ncoghlan
Date 2012-07-31.06:03:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343714596.78.0.763148838526.issue15502@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, but right now the API of importlib.abc.Finder is strictly find_module(name, path=None).  I would expect that to remain the same for MetaPathFinder (bikeshedding aside :).  So what would be left in importlib.abc.Finder if the ultimate plan is that PathEntryHandler would not implement find_module()?  Would it simply be an alias to MetaPathFinder?

I agree with the plan, but wonder if a common base class is warranted.  The connection to "finder" in PEP 302 is nice, but rather superfluous in a practical context.  Having a Finder class is necessary at this point for backward-compatibility, but I don't see how it is different from the more appropriately named MetaPathFinder.
History
Date User Action Args
2012-07-31 06:03:16eric.snowsetrecipients: + eric.snow, brett.cannon, georg.brandl, ncoghlan, eric.smith
2012-07-31 06:03:16eric.snowsetmessageid: <1343714596.78.0.763148838526.issue15502@psf.upfronthosting.co.za>
2012-07-31 06:03:16eric.snowlinkissue15502 messages
2012-07-31 06:03:15eric.snowcreate