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 benjamin.peterson, cgohlke, cstratak, hroncok, jhelmus, larry, mark.dickinson, ned.deily, njs, serhiy.storchaka, skrah, steve.dower
Date 2017-05-24.17:42:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495647736.5.0.409587683416.issue29943@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks everyone for the input on this issue.  We've had some discussions here at PyCon US and I think the consensus is that we all agree with Nathaniel's comment above that, for 3.6.x, that modules built on 3.6.2 (and later 3.6.x) should be importable on any 3.6.x (including 3.6.0), and 3.6.2 (and later 3.6.x) should be able to import modules built on any 3.6.x.  Steve Dower has suggested that it would be nice to provide a compile option so that users could compile an extension with the benefit of the 3.6.1 fix if they do not have the need for 3.6.0 compatibility.  I think that would be nice but not essential.  But we do need to ensure that 3.6.2 is fixed to be compatible as above prior to 3.6.2rc currently scheduled for 2017-06-26.  Serhiy, is that doable?

Otherwise, I believe no further changes are needed for the other branches, correct?
History
Date User Action Args
2017-05-24 17:42:16ned.deilysetrecipients: + ned.deily, mark.dickinson, larry, benjamin.peterson, njs, cgohlke, skrah, serhiy.storchaka, steve.dower, cstratak, hroncok, jhelmus
2017-05-24 17:42:16ned.deilysetmessageid: <1495647736.5.0.409587683416.issue29943@psf.upfronthosting.co.za>
2017-05-24 17:42:16ned.deilylinkissue29943 messages
2017-05-24 17:42:16ned.deilycreate