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 ncoghlan
Recipients Arfrever, amaury.forgeotdarc, asvetlov, brett.cannon, docs@python, eric.snow, eudoxos, ncoghlan, r.david.murray
Date 2012-11-29.15:08:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354201732.21.0.85005329657.issue16194@psf.upfronthosting.co.za>
In-reply-to
Content
The behaviour won't change in 2.7, but the docs at http://docs.python.org/2/library/imp.html#imp.load_dynamic still need to be clarified.

e.g. add a note like:

Note: the import internals identify extension modules by filename, so doing ``foo = load_dynamic("foo", "mod.so")`` and ``bar = load_dynamic("bar", "mod.so")`` will result in both foo and bar referring to the same module, regardless of whether or not ``mod.so`` exports an ``initbar`` function. On systems which support them, symlinks can be used to import multiple modules from the same shared library, as each reference to the module will use a different file name.

(probably flagged as a CPython implementation detail, since it's really an accident of the implementation rather than a deliberately considered language feature)
History
Date User Action Args
2012-11-29 15:08:52ncoghlansetrecipients: + ncoghlan, brett.cannon, amaury.forgeotdarc, Arfrever, r.david.murray, asvetlov, docs@python, eric.snow, eudoxos
2012-11-29 15:08:52ncoghlansetmessageid: <1354201732.21.0.85005329657.issue16194@psf.upfronthosting.co.za>
2012-11-29 15:08:52ncoghlanlinkissue16194 messages
2012-11-29 15:08:51ncoghlancreate