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 arekm, axh, benjamin.peterson, brett.cannon, gul916, pitrou, python-dev, scoder, vstinner
Date 2018-07-18.08:08:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1531901323.55.0.56676864532.issue25150@psf.upfronthosting.co.za>
In-reply-to
Content
(Ah, Benjamin restarted the discussion, so I reopen this issue.)

> I understand the desire to compile Python with OpenMP.

I'm not sure that I understood the use case. Do you want to only compile Python core ("python3" binary") or just stdlib C extensions, or both?

> But the resolution here is hiding _Py_atomic symbols all the time, even when OpenMP isn't involved, and even when building a standard extension module.

Sorry, but I don't understand the problem. Why is it an issue to hide _Py_atomic symbols?
History
Date User Action Args
2018-07-18 08:08:43vstinnersetrecipients: + vstinner, brett.cannon, arekm, pitrou, scoder, benjamin.peterson, python-dev, axh, gul916
2018-07-18 08:08:43vstinnersetmessageid: <1531901323.55.0.56676864532.issue25150@psf.upfronthosting.co.za>
2018-07-18 08:08:43vstinnerlinkissue25150 messages
2018-07-18 08:08:43vstinnercreate