Error compiling with Python 3

bdefleurian

To be honest I am not completely sure. The point is that when I migrated to Python3, the installation of python-dev (and hence the location of Python.h) decided that I needed the m version of this new Python. So I added those lines as I expect that this was a standard thing. So I supose that on your 3.8 your Python.h does not reside in python3.8m but in python3.8?
So short answer is that It worked for me without the m in 2.x versions and broke in 3.x. I will look into it to make a wiser test.

weiji14

bdefleurian

bdefleurian So I supose that on your 3.8 your Python.h does not reside in python3.8m but in python3.8?

Ok, I think that the 'm' is deprecated just for Python 3.8 and above. See https://docs.python.org/3/whatsnew/3.8.html#build-and-c-api-changes. For Python 3.7 and below, the configure script works.

harronmarsh

If you write print() function in a program and someone using Python 2.x tries to run it, they will get an error. To avoid this, it is a good practice to import print function :

from __future__ import print_function

The from future import print_function ; to bring the print function from Python 3 into Python 2.x. Now your code works on both Python 2.x and Python 3.x . The future statements need to be near the top of the file because they change fundamental things about the language, and so the compiler needs to know about them from the beginning.

justinquinn

harronmarsh Hi, I am not experiencing this issue,

$ python
...
>>> import sys
>>> sys.version_info
sys.version_info(major=2, minor=7, micro=16, releaselevel='final', serial=0)
>>> print "Hello, World!"
Hello, World!
>>> print("Hello, World!")
Hello, World!
>>> msg = "Hello, World!"
>>> print msg
Hello, World!
>>> print(msg)
Hello, World!

berkninan

weiji14 checking for python header file Python.h... configure: error: Python.h not found, locate this file and contact ISSM developers

Most of the time these are dependency-issues. Python.h is used by GNU Compiler Collection (gcc) to build applications. You need to install a package called python-dev for building Python modules, extending the Python interpreter or embedding Python in applications. You encounter "Python.h: No such file or directory" error while trying to build a shared library using the file extension of another language ( e.g. 'C' ). If you are trying to build a shared library using the file extension of another language, you need to install the correct development version of Python.

Reason for this error:

You haven't properly installed the header files and static libraries for python dev.
Also, sometimes include files might not be default in the include path.

How to solve this error:

Install the missing files and libraries.
Include Path and Library.
Finally, Compile it.

« Previous Page