I'm looking for the Multipack and cephes python modules by Travis Oliphant. The Multipack Home page link on numpy.sourceforge gives a 404... -- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
On Tue, 16 Jan 2001, Arne Keller wrote:
http://oliphant.netpedia.net/ http://oliphant.netpedia.net/multipack.html BTW, I've partly written a distutils script for this with the intention of making it easier to compile on windows (the setup.py works on linux but I need to change some things to make it set up the setup script according to the way the source has been set up). It seems distutils doesn't have explicit support for FORTRAN, so something 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 bits required to support FORTRAN for their system once this has been decided, mail me. John
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 http://cens.ioc.ee/cgi-bin/cvsweb/python/multipack/ and for instructions to get it out of cvs look at http://cens.ioc.ee/projects/pysymbolic/ HTH, __Janko John J. Lee writes:
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. Jim
I install the multipack-0.7 with my new installation of Python2.0 and I don't have any warning : maybe a problem with PYTHONPATH if your old Multipack under your old Pyhon1.5 is still present? Jim Boyle wrote:
-- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
Thanks to Arne and Paul I took the time to find out what was going on. It turns out that the CVS has multipack 0.8 and Travis added the cephes, numpyio and sigtools modules to multipack in going from 0.7 to 0.8. I did the usual things to account for a non-standard python location at the topmost level of Multipack as I had before with 0.7 but should have also tweaked the Makefiles in the cephes, numpyio and sigtools directories. The result was that these modules were built with Python 1.5 and all the others with 2.0 and I confused myself as to where the problem was. But when I tried to build the cephes module using Python 2.0 I got the following error: gcc -O2 -I/usr/local/include/python2.0 -c -o amos_wrappers.o amos_wrappers.c In file included from cephes/mconf.h:162, from amos_wrappers.h:12, from amos_wrappers.c:8: cephes/protos.h:67: parse error before `sizeof' cephes/protos.h:68: parse error before `sizeof' cephes/protos.h:69: parse error before `sizeof' make: *** [amos_wrappers.o] Error 1 the line: gcc -O2 -I/usr/local/include/python1.5 -c -o amos_wrappers.o amos_wrappers.c works fine. I have tried this on another machine with Python 2.0 and got the same error. The Python.h includes changed quite a bit in going from 1.5 to 2.0. Any ideas as to what is wrong would be welcome. Has anyone installed multipack 0.8 using Python 2.0? Jim
This would typically mean that you are importing the package into a different python than the one you used to build it. -----Original Message----- From: numpy-discussion-admin@lists.sourceforge.net [mailto:numpy-discussion-admin@lists.sourceforge.net]On Behalf Of Jim Boyle Sent: Thursday, January 18, 2001 12:03 PM To: numpy-discussion@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. Jim
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/numpy-discussion
"John J. Lee" wrote:
did you try these links? For me it returns the following message: Not Found The requested URL / was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to
-- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
On Tue, 16 Jan 2001, Arne Keller wrote:
http://oliphant.netpedia.net/ http://oliphant.netpedia.net/multipack.html BTW, I've partly written a distutils script for this with the intention of making it easier to compile on windows (the setup.py works on linux but I need to change some things to make it set up the setup script according to the way the source has been set up). It seems distutils doesn't have explicit support for FORTRAN, so something 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 bits required to support FORTRAN for their system once this has been decided, mail me. John
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 http://cens.ioc.ee/cgi-bin/cvsweb/python/multipack/ and for instructions to get it out of cvs look at http://cens.ioc.ee/projects/pysymbolic/ HTH, __Janko John J. Lee writes:
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. Jim
I install the multipack-0.7 with my new installation of Python2.0 and I don't have any warning : maybe a problem with PYTHONPATH if your old Multipack under your old Pyhon1.5 is still present? Jim Boyle wrote:
-- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
Thanks to Arne and Paul I took the time to find out what was going on. It turns out that the CVS has multipack 0.8 and Travis added the cephes, numpyio and sigtools modules to multipack in going from 0.7 to 0.8. I did the usual things to account for a non-standard python location at the topmost level of Multipack as I had before with 0.7 but should have also tweaked the Makefiles in the cephes, numpyio and sigtools directories. The result was that these modules were built with Python 1.5 and all the others with 2.0 and I confused myself as to where the problem was. But when I tried to build the cephes module using Python 2.0 I got the following error: gcc -O2 -I/usr/local/include/python2.0 -c -o amos_wrappers.o amos_wrappers.c In file included from cephes/mconf.h:162, from amos_wrappers.h:12, from amos_wrappers.c:8: cephes/protos.h:67: parse error before `sizeof' cephes/protos.h:68: parse error before `sizeof' cephes/protos.h:69: parse error before `sizeof' make: *** [amos_wrappers.o] Error 1 the line: gcc -O2 -I/usr/local/include/python1.5 -c -o amos_wrappers.o amos_wrappers.c works fine. I have tried this on another machine with Python 2.0 and got the same error. The Python.h includes changed quite a bit in going from 1.5 to 2.0. Any ideas as to what is wrong would be welcome. Has anyone installed multipack 0.8 using Python 2.0? Jim
This would typically mean that you are importing the package into a different python than the one you used to build it. -----Original Message----- From: numpy-discussion-admin@lists.sourceforge.net [mailto:numpy-discussion-admin@lists.sourceforge.net]On Behalf Of Jim Boyle Sent: Thursday, January 18, 2001 12:03 PM To: numpy-discussion@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. Jim
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/numpy-discussion
"John J. Lee" wrote:
did you try these links? For me it returns the following message: Not Found The requested URL / was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to
-- Arne Keller Laboratoire de Photophysique Moleculaire du CNRS, Bat. 213. Universite de Paris-Sud, 91405 Orsay Cedex, France. tel.: (33) 1 69 15 82 83 -- fax. : (33) 1 69 15 67 77
participants (6)
-
arne keller -
Arne Keller -
Janko Hauser -
Jim Boyle -
John J. Lee -
Paul F. Dubois