[issue11626] Py_LIMITED_API on windows: unresolved symbol __imp___PyArg_ParseTuple_SizeT

[Martin v. Löwis]

Martin v. Löwis <martin at v.loewis.de> added the comment:

> I fear I don't understand exactly what is meant here. For me it was enough to get the linker error telling me it is not working.

Suppose 3.2.1 adds this function, which then means that your extension
builds fine. However, it won't run on 3.2.0, so you might complain that
the ABI isn't really "stable". Therefore, I wonder whether you would
have liked to continue receiving compile-time indications that you are
using parts of the ABI which had not been around in 3.2.0.

Now that you know, you *personally* probably don't need this
notification anymore. I just wonder about people in similar situations.

----------
title: Py_LIMITED_API on windows: unresolved symbol __imp___PyArg_ParseTuple_SizeT -> Py_LIMITED_API on windows: unresolved symbol	__imp___PyArg_ParseTuple_SizeT

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11626>
_______________________________________