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 gregory.p.smith
Recipients doko, gregory.p.smith, python-dev, serhiy.storchaka, skrah, tshepang
Date 2014-01-22.00:19:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390349966.71.0.0423485421567.issue19936@psf.upfronthosting.co.za>
In-reply-to
Content
For those four libffi files in msg208964, do what you want with them.  I ignored executable bits entirely (didn't set or unset) when importing the code as there is zero need to execute any of them.

IMNSHO, I think executable bits should _not_ be set on most files in the Python source tree.  *Especially* not on things under Lib and Lib/test/.  Afterall, any #! on those is *guaranteed* to not refer to the Python interpreter the source tree represents.
History
Date User Action Args
2014-01-22 00:19:26gregory.p.smithsetrecipients: + gregory.p.smith, doko, skrah, tshepang, python-dev, serhiy.storchaka
2014-01-22 00:19:26gregory.p.smithsetmessageid: <1390349966.71.0.0423485421567.issue19936@psf.upfronthosting.co.za>
2014-01-22 00:19:26gregory.p.smithlinkissue19936 messages
2014-01-22 00:19:26gregory.p.smithcreate