mat puts unqualified module with common name in system path

[doclist]

mat puts a module named "lib" in dist-packages. importing "lib" will therefore refer to this module provided by mat.

The name "lib" is so common that it is likely to conflict with other python modules. A local python package that also contains a module named "lib" will mysteriously fail if the system package appears first in sys.path (which I believe is default).
The name "lib" is so generic as to provide no indication as to the fact that it comes from mat.

The module name should be qualified as a submodule of mat.

[Sascha Steinbiss (satta)]

This is apparently no longer the case, it's "libmat" in recent versions. I guess this can be closed.

[Sascha Steinbiss (satta)]

Closed as the described behaviour is no longer observed in recent versions.