On 27 Jun 2006, at 13:03, Nick Coghlan wrote:
> ...
> It occurred to me that a slight modification to PEP 338 might solve
> the
> problem fairly cleanly: instead of simply setting __name__ to
> '__main__' for a
> module in a package, the -m switch could prepend the package name
> so that
> relative imports can work correctly.
>
> Inside the module, the test for "am I the main module" would need
> to be
> "__name__.endswith('__main__')" instead of "__name__ ==
> '__main__'", but other
> than that, there should be very little impact.
Hum... other than effecting more or less every runnable python module
around it should be very little impact. That sounds like quite a bit
of impact to me!
Nicko
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
