[issue1567] Patch for new API method _PyImport_ImportModuleNoLock(char *name)

Christian Heimes report at bugs.python.org
Thu Jan 3 23:18:50 CET 2008


Christian Heimes added the comment:

Guido van Rossum wrote:
> The only thing that really worries me here is the possibility of
> relative import.  I'm thinking that relative import is really never
> meant to be when called from C, so perhaps it would be sufficient to
> modify the call to __import__ at the end of PyImport_Import() to add a
> 5th parameter, zero, to always force absolute import.  A quick concept
> test shows that this doesn't break anything, though it is worth checking
> the docs.

Committed in r59678
I've changed PyImport_Import to always use absolute imports as
requested. The docs didn't promise relative imports. It's probably a
mistake to allow relative imports in the first place.

I've also updated the docs and NEWS.

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1567>
__________________________________


More information about the Python-bugs-list mailing list