This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Arfrever, Joshua.J.Cogliati,, gustavotemple, jrincayc, lbianc, python-dev, vstinner
Date 2015-03-17.21:57:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"With the pystate_cplusplus.patch I was able to compile both min_example.tar.gz and my actual extension.  So I with your patch, it does work.  Thank you."

Cool! I applied this simple patch instead of trying to write an ugly glue in pyatomic.h between C and C++.

C and C++ simply look to be incompatible for handling atomic types :-/ The good news is that we don't them atomic types for Python extensions, only to compile Python core.

Thanks for the report. I prefer to detect such annoying issue before a ".0" release (3.5.0). FYI it's a regression introduced by the issue #22038 which started to use <stdatomic.h> (but it's now fixed).
Date User Action Args
2015-03-17 21:57:57vstinnersetrecipients: + vstinner, Arfrever, jrincayc, python-dev, Joshua.J.Cogliati,, gustavotemple, lbianc
2015-03-17 21:57:57vstinnersetmessageid: <>
2015-03-17 21:57:57vstinnerlinkissue23644 messages
2015-03-17 21:57:57vstinnercreate