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 skrah
Recipients BTaskaya, Michael.Felt, mark.dickinson, miss-islington, ned.deily, pablogsal, skrah, tim.peters, veky, vstinner
Date 2020-04-03.18:04:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585937052.4.0.646503875863.issue39576@roundup.psfhosted.org>
In-reply-to
Content
Has anything emerged xlc-wise? Traceback, does it work --without-pymalloc?

I have the feeling that (in many OSS projects) the more complex xlc
issues never get resolved after the initial report.

So I'm contemplating to do the same as 

   https://devhub.vr.rwth-aachen.de/soehrl/arbor/commit/775fe80796c717da4ed61e1cb7ace27268afc965

and disable the xlc build for _decimal.
History
Date User Action Args
2020-04-03 18:04:12skrahsetrecipients: + skrah, tim.peters, mark.dickinson, vstinner, ned.deily, veky, Michael.Felt, pablogsal, miss-islington, BTaskaya
2020-04-03 18:04:12skrahsetmessageid: <1585937052.4.0.646503875863.issue39576@roundup.psfhosted.org>
2020-04-03 18:04:12skrahlinkissue39576 messages
2020-04-03 18:04:12skrahcreate