C[omp]ute

From: andrew cooke <andrew@...>

Date: Sun, 3 Apr 2011 10:32:54 -0300

Python imports can go horribly wrong when module names conflict.

In Python 2 a projects like this:

   myproj/
   +- module.py
   +- json.py

in which module.py attempts to import from Python's json package will fail
(because the import will be pull in the local json.py instead).  I think.  Or
something similar.

Anyway, that's all in the past, because Python 3 makes local (relative) import
implicit (you have to do ugly things like "from .json".  And it can be
retro-fitted to Python 2 by using "from __future__ import absolute_import".

All well and good.  But you STILL get a problem in Python 3 if you try to
execute json.py as a script via "python myproj/json.py" (which you might want
to do if you have doctests, for example).

To avoid that, invoke the module like this: "python -m myproj.json".

Andrew