Hello All, A bit of background on this.
Some Linux distros use Python3.x as their default Python, where Debian, Ubuntu and friends, and many others, are still using Python2 as their default system Python. Here inlies the problem. Both will build Numpy 1.8+ v2, however, f2py would be the default output from building on either system "if" there is only one Python version installed on the system. You can test the version output with: f2py -v or f2py3 -v, both would yield: v2 but I've not found a way to test if f2py was built against Python3 or Python2. If built against Python2, the function calls, syntax and object struct lines have been changed in Python3, thus resulting in some of these strange error messages. WSPR (wspr.py) is using the Python3 convensions, so (w.so) needs to be built / structured with Python3 Shuttleworth stated in a corporate communication Python3 would "take center stage over the next two releases" meaning, Ubuntu was shifting to Python3 as the default system Python. That will yield a /usr/bin/f2py built against Python3, so hard coding f2py3 as the file name would fail, same as hard coding f2py as the file name on current systems. To get around this, there is an option include in the configure script, after running autogen.sh, (may need to clarify this in the INSTALL.txt file) to specify the location of f2py that was / is built against Python3: ./configure --with-f2py="/path/to/f2py" or ./configure --with-f2py="/path/to/f2py3" configure.ac simply checks if f2py or p2py3 renders a version number, but has not way of determining if it has been built against Python2 or Python3, thus the reason you see /usr/bin/f2py which indicates, at some point, python-numpy (on Debian / Ubuntu and friends) as opposed to python3-numpy was used to build or install Numpy (on Debian / Ubuntu and friends at least). This does not apply to those distro's that use Python3 as their default Python, as /usr/bin/f2py would be the correct f2py to use. So the solution is down to the distro package maintainers to resolve the correct Python version and the equal build of Numpy, which is Python3. 73's Greg, KI7MT On 06/22/2014 12:03 PM, RichardBown wrote: > On Sun, 22 Jun 2014 18:50:08 +0200 > Claude Frantz <claude.fra...@bayern-mail.de> wrote: > >> On 06/22/2014 06:07 PM, Graham wrote: >> >>> it seems it might have been related to python-numpy. >> I'm using Fedora 19 and the following packages are installed: >> >> python3-numpy-f2py >> python3-numpy >> >> When asking the information about python3-numpy-f2py, the response >> related to the description is: >> This package includes a version of f2py that works properly with >> NumPy. >> >> The Configuration Summary says that python3 and f2py will be used. >> But this will fail. When changing manually f2py to f2py3 in the >> Makefile, as has been recommended here by Chuck Forsberg WA7KGX, it >> runs OK. >> >> Thank you again, Chuck ! >> >> Best 88 de Claude >> >> >> > Hi Claude > Changing in the makefile to f2py3.4 also works, compiles and runs > > Maybe worth making a change to the autogen.sh to force the use of > f2py3, if that can be done. > > thanks for the hint ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
