On Mon, Jul 19, 2010 at 05:28, Vincent Schut <sc...@sarvision.nl> wrote: > > Well, you might want to read up on some beginners guide for python? It's > up to you, of course, but usually before starting with numpy (which > extends python), it is advised to have at least some basic python > understanding... Googling will give you plenty of good resources, if > you'd like to.
I'm not a python beginner. Why did you assume I was? > Then, for the sake of helping you further anyway: > you'll have to mind the significance of paths (=directories or folders > in windows speak I think). The folder you're currently in, will restrict > what you find when typing commands. If you need to reference something > from a different folder, you'll need to explicitly specify that. Yes, I have that understanding. > To build numpy, you'll need to be in the numpy source folder (the numpy > you extracted from svn). But if you're there, simply typing 'python' or > 'python.exe' will probably not work because 'python.exe' is in a > different folder (c:\Python31). You could go into that folder, but then > you would not be able to find numpy's setup.py script. Best way to solve > that: make sure you're in the numpy folder, and type something like: > 'c:\Python31\python.exe setup.py build'. That should get you started at > least. > > However, if I'm allowed to give you some unaskedfor advice: this might > become lots easier if you make sure you're at least a bit comfortable > with 1) the windows command prompt, 2) python, and 3) building python > stuff from svn source checkouts. No offence meant. But you sound as you > feel a lot more comfortable with pre-built packages compared to building > yourself from source on windows... No, I fail your number 3. > Good luck anyway! > Vincent Schut. Thanks, Vincent. And I am more comfortable with pre-built packages. Dick _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
