Suggestion for improved ImportError message

Lie Lie.1296 at
Fri Aug 15 12:23:16 CEST 2008

On Aug 14, 5:10 pm, Wojtek Walczak
<gmin... at> wrote:
> On Thu, 14 Aug 2008 01:35:44 +0000 (UTC), Kent Tenney wrote:
> >> > Then go for it  You can prepare a patch and ask on python-dev
> >> > if the developers are interested.
> > hehe, I'll get a C level patch accepted right after I
> > out-swim Mike Phelps.
> It's really not that hard. The only hard thing (harder than
> writing the code) might be to win the acceptance of the core
> developers that this change is really needed ;-)

I think the acceptance for this wouldn't be that hard since there is
no real issue for regression (the only one I could think of is for
doctest module, although I'm not sure there are any reason to test for
failed import in doctest)

> >> > I was never hacking the import things on C level before,
> >> > but a hint: you have to modify import_from function from
> >> > Python/ceval.c
> > Am I correct in thinking that PyPy would mean low level
> > stuff like this will be Python instead of C?
> > That would be nice.
> I don't know PyPy, but I guess you're right here.
> --
> Regards,
> Wojtek Walczak,

More information about the Python-list mailing list