[PYTHON MATRIX-SIG] Final matrix object renaming and packaging

Jim Fulton, U.S. Geological Survey jfulton@usgs.gov
Tue, 16 Jan 1996 13:00:45 -0500

On Jan 16, 12:17pm, Hinsen Konrad wrote:
> Subject: Re: [PYTHON MATRIX-SIG] Final matrix object renaming and packagin
>    I feel strongly that the Matrix module should export it's C interface
>    using CObjects so that modules using matrices to not require that any
>    of the matrix software be statically linked.  In my distribution of
> I agree in principle, but that doesn't have to happen in the
> first beta release.

Perhaps not.  I'll put this together myself when I get the next alpha

>    Are these imported by Numeric, or would the user be importing these?
>    Is the current built-in array module going away?  If not, then there
>    is a name conflict on case-insensitive file systems.  I like the idea
> Why? The current "array" in a C module, so "import Array" will
> never load it, independent of the file name conventions. Which
> means that "import Array" will always obtain an external module,
> and as long as ours is the only one, it hardly matters if it
> is called "Array.py" or "array.py".

Actually, at least in 1.2, if a C module and a Python module are in the same
directory, the C module gets loaded first.  But this will be most likely a
function of what order libraries appear in sys.path.  I just think that it
would be best to avoid this problem altogther by using a different name.


MATRIX-SIG  - SIG on Matrix Math for Python

send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org