On Sat, 29 Nov 2008 01:56:00 pm Nick Coghlan wrote: > Steven D'Aprano wrote: > > Should this be reported as a documentation bug? Given the new > > import hooks, would it be fair to say that the main reason for > > __import__ is to use it to import a module whose name is only known > > at runtime? > > Only known at runtime, and for some reason you want an actual module > object rather than just the module's global namespace (since you can > use runpy.run_module() if you only need the latter). > > At the very least, the __import__ docs should probably be updated to > point to run_module() as an alternative approach, so a doc issue is > probably a good idea.
Bug report is here: http://bugs.python.org/issue4457 Based on Guido's comments, I haven't mentioned run_module(). -- Steven _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
