➜

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 erykoff
Recipients erykoff, ned.deily, ronaldoussoren
Date 2020-12-20.20:43:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1608497030.78.0.117741888642.issue42688@roundup.psfhosted.org>
In-reply-to
Content 
Thanks for your quick feedback!  I signed the CLA after submitting the PR, but I think it takes a bit of time to percolate through the system.

As for the "why", until 3.9.1 conda-forge had been successfully using an external ffi (with 3.9.0 + osx-arm64 patches) and then suddenly it broke.  For the time being conda-forge is using the system ffi, which does have other advantages as well, having all the latest patches.  However, I was curious as to _why_ it broke, and that led me to discover this bug, and it seemed straightforward to fix.  When/if conda-forge will switch back to external ffi is TBD, but if that decision is made this issue (at least) will be taken care of.
History
Date User Action Args
2020-12-20 20:43:50erykoffsetrecipients: + erykoff, ronaldoussoren, ned.deily
2020-12-20 20:43:50erykoffsetmessageid: <1608497030.78.0.117741888642.issue42688@roundup.psfhosted.org>
2020-12-20 20:43:50erykofflinkissue42688 messages
2020-12-20 20:43:50erykoffcreate