[Python-3000] It's a statement! It's a function! It's BOTH!

Talin talin at acm.org
Sun Apr 2 23:19:22 CEST 2006

Guido van Rossum <guido <at> python.org> writes:

> Based on my experience with past wild proposals, you're probably going
> to counter by proposing that the Python interpreter somehow follows
> imports at compile time; I could then object that it's totally
> reasonable that the module to be imported is unavailable to the parser
> (either due to import hooks to be installed later, or simple separate
> compilation as done by compileall.py). You could then counter by
> proposing an alternative syntax for compile-time imports import
> foo that must be followed and interpreted by the parser. And I
> could call that ugly, hard to implement, etc.

No worries. My purpose here is to "think the unthinkable", not to
argue that I'm right. I often throw out wild ideas at my work;
occasionally I hit a bullseye. In the mean time, criticism is
welcome and enjoyed :)

And thanks for the explanation.

-- Talin

More information about the Python-3000 mailing list