The python to c interface is a bit unstable, each release of the c extension library seems to require some quick corrections and depending on what level of instructions you read you will get undefined symbols. Finally I found an obscure comment that explained the latest last minute correction in python 3, and bingo, it works.
I am not worried, the python crew will get this interface stabilized. It is the best choice, I am will to suffer a bit of instability.
Linux programming tip:
Having trouble getting gcc, the environment, and installs to allagree on where the includes are? No problem, c can handle it with:
#include </usr/include/python3.6m/Python.h>
You go manually find the file using locate, after using updatedb , making sure you are not fooled by a bad index. Does it matter? One way or the other you will deal with chains of file directories, a c expanded filename works fine. I got lotta directories just sitting empoty chained to another directory, it is the fashion in linux.
No comments:
Post a Comment