On 2013-10-18 04:25-0000 Arjen Markus wrote: > Hi Alan,
> on my machine Python 2.7.5 is installed with Numpy 1.7 in a location c:\Python27\Lib\site-packages\numpy\core\include as reported by numpy.get_include(). So I think it is all correct. This installation came with the territory so to say - it was all packed together. > From the include files themselves I see that there is a new API and I guess that that is where the trouble is coming from. I will try and see if I can find a solution. Possibly I need to reinstall Python, using 2.7.3 and 1.5.1 instead. Hi Arjen: My guess is the integrated python+numpy package version you have installed on your computer combines so much from different versions of python and numpy that they are interfering with each other. So I would advise you only install what you need for PLplot and no more which is the latest release in the python-2.7.x series, and the subpackage of the latest release of numpy that is compatible with that. My research indicates those minimal but latest pieces are python-2.7.5.msi which you should download from http://www.python.org/ftp/python/2.7.5/ and numpy-1.7.1-win32-superpack-python2.7.exe which you should download from http://sourceforge.net/projects/numpy/files/NumPy/1.7.1/. (There are later numpy releases, but they are betas and release candidates but nothing final yet.) I am virtually positive those should work if you follow my instructions for the install GUI's below. However, I haven't tried them myself. What I did the other day because I was being lazy was combine python-2.7.3.msi that I downloaded some time ago from http://www.python.org/ftp/python/2.7.3 with numpy-1.5.1-win32-superpack-python2.7.exe I downloaded some time ago from http://sourceforge.net/projects/numpy/files/NumPy/1.5.1/ So that successful build and install was done quite recently, but it was based on old downloads. You can use those old versions as well if you want to exactly replicate the versions I used, but the above latest downloads should work as well, and in any case I am about to shift to those myself since I am now aware of them (due to the research for this e-mail) and later patch versions are almost always better in the Python world. Anyhow, when you try this again, please include all the relevant cmake output results for PLplot that I showed below for my own MinGW/MSYS platform. It is those results that should tell the tale of whether your Python installation and your setup of PATH, CMAKE_INCLUDE_PATH, and CMAKE_LIBRARY_PATH is suitable for a PLplot build. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
