➜

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 Vladimír Čunát
Recipients Vladimír Čunát, christian.heimes, larry, ncoghlan, python-dev, serhiy.storchaka, vstinner, xiang.zhang
Date 2017-02-21.12:49:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487681396.65.0.849544896066.issue29157@psf.upfronthosting.co.za>
In-reply-to
Content 
Why was there no backporting e.g. to 3.4 branch?  I thought you implied that 3.3 and 3.4 are unaffected, but our build farm says otherwise, getting a segfault in bin/python3.4m (3.4.6) and printing "Fatal Python error: getentropy() failed"
History
Date User Action Args
2017-02-21 12:49:56Vladimír Čunátsetrecipients: + Vladimír Čunát, ncoghlan, vstinner, larry, christian.heimes, python-dev, serhiy.storchaka, xiang.zhang
2017-02-21 12:49:56Vladimír Čunátsetmessageid: <1487681396.65.0.849544896066.issue29157@psf.upfronthosting.co.za>
2017-02-21 12:49:56Vladimír Čunátlinkissue29157 messages
2017-02-21 12:49:56Vladimír Čunátcreate