[issue29244] Python 3.6 unnecessarily requires inttypes.h

rdb added the comment: As far as I know, there should not be any ABI issues. We've been building extension modules with non-matching MSVC versions for years without issues. I find it hard to think of downsides to such a trivial fix. It is somewhat frustrating that we will have to resort to

[issue29244] Python 3.6 unnecessarily requires inttypes.h

Brett Cannon added the comment: Everything Zach said is accurate, so closing as "wont fix". -- nosy: +brett.cannon resolution: -> wont fix status: open -> closed ___ Python tracker

[issue29244] Python 3.6 unnecessarily requires inttypes.h

Zachary Ware added the comment: VS 2010 is not a supported compiler version for 3.6 (or 3.5) and VS 2012 is not a supported compiler for any version of Python. Extension modules built by those versions for use with Python 3.6 as supplied by python.org will only work in very particular

[issue29244] Python 3.6 unnecessarily requires inttypes.h

Changes by Serhiy Storchaka : -- components: +Build -Extension Modules nosy: +benjamin.peterson type: -> compile error versions: +Python 3.7 ___ Python tracker

[issue29244] Python 3.6 unnecessarily requires inttypes.h

New submission from rdb: Python 3.6 now requires inttypes.h on all platforms. However, this is not provided by MSVC 2010 and 2012, which is still used by some people who build extension modules for Python. MSVC 2010 does provide stdint.h, and replacing the inttypes.h include with an include