Paul F. Dubois
paul at pfdubois.com
Thu Jan 18 16:30:03 CST 2001
This would typically mean that you are importing the package into a
different python than the one you used to build it.
From: numpy-discussion-admin at lists.sourceforge.net
[mailto:numpy-discussion-admin at lists.sourceforge.net]On Behalf Of Jim
Sent: Thursday, January 18, 2001 12:03 PM
To: numpy-discussion at lists.sourceforge.net
Subject: Re: [Numpy-discussion] multipack
I pulled the multipack code from the CVS server and built it for my
new installation of Python 2.0.
When I import Multipack I get:
WARNING: Python C API version mismatch for module cephes:
This Python has API version 1009, module cephes has version 1007
this warning occurs for the numpyio and sigtools modules.
Have I done something screwy in the installation, or do the modules
have to be updated?
If the latter is there any guidance on what to fix? What are the
routines/procedures that changed in going from version 1007 to 1009?
So far everything appears to provide the correct answers, so the API
mismatch is not crippling. However, from past experience I know that
ignoring warnings often ends in tears.
>These pages are depreciated, as Travis has moved. I could not find the
>announcement for the new pages. Menawhile you can check out these
>packages from the public cvs server of Pearu Peterson.
>For an overview of the cvs content look at
>and for instructions to get it out of cvs look at
>John J. Lee writes:
> > On Tue, 16 Jan 2001, Arne Keller wrote:
> > > I'm looking for the Multipack and cephes python modules by Travis
> > > Oliphant.
> > >
> > > The Multipack Home page link on numpy.sourceforge gives a 404...
> > http://oliphant.netpedia.net/
> > http://oliphant.netpedia.net/multipack.html
> > BTW, I've partly written a distutils script for this with the intention
> > making it easier to compile on windows (the setup.py works on linux but
> > need to change some things to make it set up the setup script according
> > the way the source has been set up).
> > It seems distutils doesn't have explicit support for FORTRAN, so
> > needs changing there for it to work cross-platform. I haven't got any
> > feedback yet from the Distutils people on how best to do this, but if
> > anyone reading this who is practiced at compiling FORTRAN and C
> > (especially on windows compilers) and wouldn't mind adding the little
> > required to support FORTRAN for their system once this has been
> > mail me.
Numpy-discussion mailing list
Numpy-discussion at lists.sourceforge.net
More information about the Numpy-discussion