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 christian.heimes
Recipients christian.heimes, gvanrossum, kbk
Date 2008-01-03.22:18:50
SpamBayes Score 0.04353063
Marked as misclassified No
Message-id <477D5F48.6000704@cheimes.de>
In-reply-to <1199383063.52.0.353941222409.issue1567@psf.upfronthosting.co.za>
Content
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.
History
Date User Action Args
2008-01-03 22:18:50christian.heimessetspambayes_score: 0.0435306 -> 0.04353063
recipients: + christian.heimes, gvanrossum, kbk
2008-01-03 22:18:50christian.heimeslinkissue1567 messages
2008-01-03 22:18:50christian.heimescreate