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 brett.cannon
Recipients barry, brett.cannon, eric.smith, jaraco
Date 2012-04-24.15:57:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335283037.77.0.193603849495.issue14660@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, having to pass in the name to load_module is silly. I'm seriously considering making it optional for some loaders when the name was passed in to the constructor.

One thing I would like to see is that PathFinder take a new, keyword-only argument of 'namespace_loader' or something that takes an object which is called with the module name and the list of paths to use for __path__ (and thus __path__[0] becomes __file__). That way it can be controlled by users if desired. I'm also fine with it having a default value of NamespaceLoader to start since I don't see people needing to comprehend what they are allowing in this case as I do for general file loaders.
History
Date User Action Args
2012-04-24 15:57:17brett.cannonsetrecipients: + brett.cannon, barry, jaraco, eric.smith
2012-04-24 15:57:17brett.cannonsetmessageid: <1335283037.77.0.193603849495.issue14660@psf.upfronthosting.co.za>
2012-04-24 15:57:16brett.cannonlinkissue14660 messages
2012-04-24 15:57:16brett.cannoncreate