➜

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 ned.deily
Recipients Juuso Lehtivarjo, christian.heimes, docs@python, gregory.p.smith, ned.deily, serhiy.storchaka, vstinner, xtreak
Date 2018-10-07.19:08:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538939287.75.0.545547206417.issue33729@psf.upfronthosting.co.za>
In-reply-to
Content 
The question remains if Christian's and Victor's concern with 3.7 compatibility have been satisfied by Serihy's response in msg322798. While there is plenty of time to resolve concerns about what was merged into master by PR 8346, we shouldn't release the PR 8581 changes in 3.7.1 if there are still valid compatibility concerns.  Since PR 9657 for 3.6 hasn't been reviewed or merged, the only pressing issue for 3.6.7 is ensuring the segfault documented in Issue34922 is blocked, correct?  And PR 8581 prevents the segfault for 3.7 so we would only need a similar fix for it if the PR were reverted, correct?
History
Date User Action Args
2018-10-07 19:08:07ned.deilysetrecipients: + ned.deily, gregory.p.smith, vstinner, christian.heimes, docs@python, serhiy.storchaka, Juuso Lehtivarjo, xtreak
2018-10-07 19:08:07ned.deilysetmessageid: <1538939287.75.0.545547206417.issue33729@psf.upfronthosting.co.za>
2018-10-07 19:08:07ned.deilylinkissue33729 messages
2018-10-07 19:08:07ned.deilycreate