Message76582
| Author |
steven.daprano |
| Recipients |
georg.brandl, steven.daprano |
| Date |
2008年11月29日.04:40:51 |
| SpamBayes Score |
2.2720584e-05 |
| Marked as misclassified |
No |
| Message-id |
<1227933654.59.0.602366149216.issue4457@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The documentation for __import__ says that it primarily exists "so that
you can replace it with another function that has a compatible
interface, in order to change the semantics of the import statement".
http://docs.python.org/library/functions.html
That is no longer the case. The recommended way to do that is with the
new import hooks, and the docs should reflect that.
A common use for __import__ is for when you don't know the module name
until runtime. That too should be mentioned. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2008年11月29日 04:40:55 | steven.daprano | set | recipients:
+ steven.daprano, georg.brandl |
| 2008年11月29日 04:40:54 | steven.daprano | set | messageid: <1227933654.59.0.602366149216.issue4457@psf.upfronthosting.co.za> |
| 2008年11月29日 04:40:53 | steven.daprano | link | issue4457 messages |
| 2008年11月29日 04:40:52 | steven.daprano | create |
|