Building Numpy under Python 1.6, Windows
I have recently upgraded to Python 1.6 (final). Now I can't figure out how to build Numpy with lapack_lite under windows. There is not a makefile for lapack_lite for MSVC and the instructions in README don't really help. All that setup.py will do is complain that lapack_lite is not installed. Specifically, are there specific compiler flags that I need to use to compile lapack lite? Should I just emulate the unix version and do cl -c *.c lib -out:blas.lib blas_lite.obj lib -out:lapack.lib dlapack_lite.obj f2c_lite.obj zlapack_lite.obj I tried doing this, but when I try to run the NumTut examples, I get the following error: D:\Programming\python\Numerical\Demo>python Python 1.6 (#0, Sep 5 2000, 08:16:13) [MSC 32 bit (Intel)] on win32 Copyright (c) 1995-2000 Corporation for National Research Initiatives. All Rights Reserved. Copyright (c) 1991-1995 Stichting Mathematisch Centrum, Amsterdam. All Rights Reserved.
import NumTut Traceback (most recent call last): File "<stdin>", line 1, in ? File "NumTut\__init__.py", line 14, in ? greece = pickle.load(open(os.path.join(_dir, 'greece.pik'), 'rb')) / 256.0 File "D:\Programming\python\Python 1.6\lib\pickle.py", line 855, in load return Unpickler(file).load() File "D:\Programming\python\Python 1.6\lib\pickle.py", line 515, in load dispatch[key](self) File "D:\Programming\python\Python 1.6\lib\pickle.py", line 688, in load_globa l klass = self.find_class(module, name) File "D:\Programming\python\Python 1.6\lib\pickle.py", line 698, in find_class
raise SystemError, \ from module Numericto import class array_constructor
FWIW, I am using the versions from :pserver:anonymous@cvs.numpy.sourceforge.net:/cvsroot/numpy, module Numerical, checked out as of Sept. 14. I didn't see any tags defined in the repository corresponding to release 16.x. Did I miss something? Should the releases not be getting tagged in the CVS repository? Thanks for any pointers, Jonathan
I have solved my problem building numpy under Python 1.6, windows. The problem was that Demos/NumTut/greece.pik was improperly checked into the CVS repository as a text file, when it should have been binary. Jonathan
Would you try syncing up to the repository and try again? I redid this stuff over the weekend because so many people are having trouble. The thing should build in lapack by default and it is in an optional package to boot. I didn't announce this because I wanted some of my fellow developers to suffer first, but they don't seem to be in a suffering mood today. Do cvs update -d -P to get the new structure. We haven't been doing cvs tags. I suppose if I could remember how to do them I would do them when I am the one cutting the release (CVS is not my usual source control system).
-----Original Message----- From: numpy-discussion-admin@lists.sourceforge.net [mailto:numpy-discussion-admin@lists.sourceforge.net]On Behalf Of Jonathan M. Gilligan Sent: Monday, September 18, 2000 2:34 PM To: numpy-discussion@lists.sourceforge.net Cc: Jonathan M. Gilligan Subject: [Numpy-discussion] Building Numpy under Python 1.6, Windows
I have recently upgraded to Python 1.6 (final). Now I can't figure out how to build Numpy with lapack_lite under windows. There is not a makefile for lapack_lite for MSVC and the instructions in README don't really help. All that setup.py will do is complain that lapack_lite is not installed.
To tag the version you currently have checked out, go into the root directory of the module (e.g., Numeric) and AFTER CHECKING IN ALL MODIFICATIONS do cvs tag [-c] <symbolic-tag> where <symbolic-tag> is the tag name. This will apply <symbolic-tag> to the current revision of each file that you have checked out. It is important to note that the tag is applied to the repository so it is essential that you check in all modified files and resolve conflicts BEFORE tagging the repository. The -c flag tells cvs to check that all files in the local directory are unmodified and warns you if they are not. The restrictions on the tag name are not well-documented, but if they match the regular expression ^[A-Za-z][A-Za-z_0-9-]+$ they will work (i.e., matching this regex is a sufficient but perhaps not necessary condition). Tags that begin with [0-9] or that contain [ \t.,;:] will not work. If you want to go back and tag old releases without checking them out, then if there is a target date that you can use to identify the version (e.g., a release date), you can run cvs rtag -D <date> <symbolic-tag> <module> Where <date> is the date. For format, the following excerpt from the Cederqvist manual may help:
A wide variety of date formats are supported by CVS. The most standard ones are ISO8601 (from the International Standards Organization) and the Internet e-mail standard (specified in RFC822 as amended by RFC1123).
ISO8601 dates have many variants but a few examples are:
1972-09-24 1972-09-24 20:05
This command will tag all files in <module> at the latest revision on or before <date> with tag <symbolic-tag>. I hope this is helpful to you. At 05:29 PM 9/18/2000, Paul F. Dubois wrote:
We haven't been doing cvs tags. I suppose if I could remember how to do them I would do them when I am the one cutting the release (CVS is not my usual source control system).
Best regards, Jonathan
participants (2)
-
Jonathan M. Gilligan -
Paul F. Dubois