➜

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 pitrou
Recipients benjamin.peterson, gregory.p.smith, pitrou, siddhesh, skrah, steve.dower, vstinner
Date 2018-10-23.12:59:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540299564.26.0.788709270274.issue33015@psf.upfronthosting.co.za>
In-reply-to
Content 
Right, so one PR is a real fix, the other PR is a workaround (avoids the warning without fixing the underlying problem).

The underlying problem is: if a platform has incompatible ABIs for the two function types, casting one function type to another may produce bugs (memory corruptions, crashes, etc).  We can however decide to consider those platforms unlikely, as the current code has been working for years or decades.

It would be nice to have an opinion from C specialists.
History
Date User Action Args
2018-10-23 12:59:24pitrousetrecipients: + pitrou, gregory.p.smith, vstinner, benjamin.peterson, skrah, steve.dower, siddhesh
2018-10-23 12:59:24pitrousetmessageid: <1540299564.26.0.788709270274.issue33015@psf.upfronthosting.co.za>
2018-10-23 12:59:24pitroulinkissue33015 messages
2018-10-23 12:59:24pitroucreate