[Python-Dev] 3.6 branch is now open for 3.6.1
OK, rc1 is now out the door. Thanks to everyone who helped resolve the remaining release blocker issues. As of now, the code base for 3.6.0 final is frozen. The 3.6 branch is now open for code that will be released in 3.6.1, the first 3.6 maintenance release. As usual, that means bug fixes, security fixes, and documentation updates. Refer to the Developer's Guide for more information on the development cycle. If you have any questions about whether a change is appropriate for a 3.6.x maintenance release, please ask. http://cpython-devguide.readthedocs.io/en/latest/devcycle.html#maintenance-branches During the period between rc1 and the final release (scheduled for 2016-12-16), please continue to test 3.6.0rc1 and encourage others to do so. Repeating what I wrote earlier: Should any emergency showstopper problems be discovered affecting 3.6.0rc1, please open an issue, mark it as "release blocker", if possible push a fix to the 3.6 branch for 3.6.1, and we will discuss what action to take for 3.6.0. As I've mentioned many times now, my goal is to have *no* code changes for 3.6.0 after rc1 so you will have to make a *really* strong case to add any code changes after rc1 and prior to the final release scheduled for 12-16. Should the need arise for such a change, it would be cherrypicked from the 3.6 branch. I am more willing to consider cherry-picking pure doc changes after rc1 but these will also need to be pushed to 3.6 and marked as "release blocker". Counting down the days to the final release! -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] List mutation in list_repr?
On Tue, Dec 6, 2016 at 5:32 PM, Random832 wrote: > It *shouldn't*, but it can't be enforced. It's one of those things where > if Python assumes all user code is sane (in this case, overridden > __repr__ not messing with the list) it can bite in a way that could > cause the interpreter to crash. I guess you are right. That makes sense. I didn’t think about the possibility that although the repr implementation is happening in native code where the user objects have no access to, the list object could still be referenced outside of the repr call. Thanks a lot for the explanation and your example! And also thank you Hrvoje Niksic! ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] List mutation in list_repr?
On 07.12.16 12:19, Patrick Westerhoff wrote: On Tue, Dec 6, 2016 at 5:32 PM, Random832 wrote: It *shouldn't*, but it can't be enforced. It's one of those things where if Python assumes all user code is sane (in this case, overridden __repr__ not messing with the list) it can bite in a way that could cause the interpreter to crash. I guess you are right. That makes sense. I didn’t think about the possibility that although the repr implementation is happening in native code where the user objects have no access to, the list object could still be referenced outside of the repr call. There is another reason. Executing Python code can release GIL. The list object can be modified in other thread. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 3.6 What's New document changes for 3.6.0 final
Since the question has already come up and there will likely be further changes, let's keep it simple: feel free to make changes in the 3.6 branch to Doc/whatsnew/3.6.rst for 3.6.0 and I will cherrypick those changes just prior to producing the 3.6.0 final. Likewise with Misc/NEWS. As stated before, any other potential changes require a 3.6 checkin and a "release blocker" issue in the tracker. Thanks! --Ned -- Ned Deily [email protected] -- [] ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
