[python-win32] extension modules and msvc version

[Thomas Heller]

Am 20.02.2015 um 17:41 schrieb Zachary Turner:
> Does anyone understand the technical reasons why an extension module
> must be compiled with the same version of msvc as python itself? Are
> there any workarounds? It's really quite an inconvenience.
>
> If the reason is because python27.dll and the extension module free each
> others' memory, then it seems like this could be solved by having each
> supply the other with an alloc and free function pointer, and using the
> correct allocator on each side.
>
> Is the situation better in python 3 than it is in 2.7? And is anyone
> aware of any ways to get around this restriction so that i can write an
> extension module that will work with a binary release of python?

pep 384 solves this problem.