PYBIND11_MODULE MSVC 2017 python 3.6 issue: Python Version mismatch

[microsoft]

PYBIND11_MODULE MSVC 2017 python 3.6 issue: Python Version mismatch

[kraigb]

Thanks for the report. I'll look into it when I have a chance (but that might be a little while given a relatively short time I have before the holidays).

[kraigb]

Having (finally) reviewed this all, I see that Py_LIMITED_API shouldn't be included when using PyBind11. This is correct in the sample: the superfastcode2 project, which is oriented around PyBind11, doesn't include that preprocessor definition (the superfastcode project using CPython, does).

Clearly, then, the only fix needed here is to clarify the documentation to use Py_LIMITED_API with only CPython.

Thanks for pointing it out!

[Mjang714]

Thanks. I wanted to give you a quick update. I tried building the package with the python setup script in your example, and ran the script to create the python module and it worked fine with python 3.7. I am beginning to think that this specific issue with the way visual studio is set up on my PC. I am using the community edition is there any additional setup that I may be missing?

[kraigb]

I'm not sure...I've been using the Community edition as well. Offhand, I'm thinking that it's perhaps a mismatch of the selected interpreter for the project in VS.

You said you built successfully on the command line, yes? If you just run "python --version", that reports 3.7, correct? And what's the output from "where python.exe"? (To see which installation you're running.)

In VS, then, in Solution Explorer, expand the "CppAndPython" project, then expand "Python Environments". What environment is shown there? If it doesn't match the Python 3.7 that you successfully built with, right-click Python Environments, select "Add/Remove Python Environments", and set the box for the same 3.7 interpreter. Then try the build again. (The Python Environments window, which is a peer to Solution Explorer, is where you can look at the details of each of the interpreters.)

[Mjang714]

when running "python --version" I did indeed get Python 3.7.1. When running the python command from the terminal I get
Python 3.7.1 (v3.7.1:260ec2c36a, Oct 20 2018, 14:05:16) [MSC v.1915 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

I did however figure out what the issue was though. The Preprocessor Py_LIMITED_API; prevented the macro for Py_Buffer from being defined, and also prevented python version retrieval I guess. I am not sure why this would be a problem from 2.7.11 to 3.X. I think the authors of Python 3.X choose to deprecate some of the functionalities of Py_LIMITED_API for some reason, again I am not certain why. Have anyone else ever run into an issue with Py_LIMITED_API being defined in the Preprocessors? Thanks again for all your help!!! HAPPY HOLIDAYS!!!!

[Mjang714]

Thanks!!!!