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 r.david.murray
Recipients Arek Bulski, JelleZijlstra, brett.cannon, ned.deily, njs, r.david.murray, vstinner
Date 2017-06-11.15:31:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1497195092.61.0.212255951728.issue30623@psf.upfronthosting.co.za>
In-reply-to
Content
There is a possible future in which the development style is based around continuous integration with third parties, where we apply our backward compatibility policy even to changes from one commit to the next within our development cycle.  I think that possible future is interesting, but is non-trivial to accomplish, and represents a cultural shift that we'd need to commit to.

If we go there then, as I believe was touched on at the language summit, actual python official releases would become less significant events :)
History
Date User Action Args
2017-06-11 15:31:32r.david.murraysetrecipients: + r.david.murray, brett.cannon, vstinner, ned.deily, njs, JelleZijlstra, Arek Bulski
2017-06-11 15:31:32r.david.murraysetmessageid: <1497195092.61.0.212255951728.issue30623@psf.upfronthosting.co.za>
2017-06-11 15:31:32r.david.murraylinkissue30623 messages
2017-06-11 15:31:32r.david.murraycreate