Message166961
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. |
|
Date |
User |
Action |
Args |
2012-07-31 06:03:16 | eric.snow | set | recipients:
+ eric.snow, brett.cannon, georg.brandl, ncoghlan, eric.smith |
2012-07-31 06:03:16 | eric.snow | set | messageid: <1343714596.78.0.763148838526.issue15502@psf.upfronthosting.co.za> |
2012-07-31 06:03:16 | eric.snow | link | issue15502 messages |
2012-07-31 06:03:15 | eric.snow | create | |
|