Re: [Python-Dev] PEP 544 status (forked off "Petr Viktorin as BDFL-Delegate for PEP 580")
On Sat, 6 Oct 2018 at 07:57, Brett Cannon wrote: > > I think whatever governance we end up with would have named you BDFL-delegate > anyway, Guido, so I think you're just taking the time machine for a spin > again. ;) I was going to suggest that Guido list himself as BDFL-Delegate as then it could follow the same caretaker model we're suggesting for the fast C calling API. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ 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] PEP 544 status (forked off "Petr Viktorin as BDFL-Delegate for PEP 580")
OK, then maybe someone (not me) can merge https://github.com/python/peps/pull/799 for me. On Sat, Oct 6, 2018 at 7:54 AM Nick Coghlan wrote: > On Sat, 6 Oct 2018 at 07:57, Brett Cannon wrote: > > > > I think whatever governance we end up with would have named you > BDFL-delegate anyway, Guido, so I think you're just taking the time machine > for a spin again. ;) > > I was going to suggest that Guido list himself as BDFL-Delegate as > then it could follow the same caretaker model we're suggesting for the > fast C calling API. > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > -- --Guido van Rossum (python.org/~guido) ___ 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] PEP 544 status (forked off "Petr Viktorin as BDFL-Delegate for PEP 580")
On Sun, Oct 7, 2018 at 7:55 AM Guido van Rossum wrote: > > OK, then maybe someone (not me) can merge > https://github.com/python/peps/pull/799 for me. > Per discussion, merged. ChrisA ___ 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.7.1 and 3.6.7 Release Update
[duplicated from https://discuss.python.org/c/committers] We issued the 3.7.1rc1 and 3.6.7rc1 release candidates a little over 11 days ago with the plan to have final releases for each available by today, assuming no new issues arose since the rc1 cutoffs. While the good news is that, to the best of my knowledge, no regressions have been reported for the release candidates (or remain unfixed), several critical and security-related issues have identified during the rc phase. Most of these have already been addressed (thanks for the quick responses!) but there remain a couple that still need to be finalized. Since there is a non-zero amount of fixes going in after rc1, I think we need to do another set of release candidates once everything is resolved. Because a number of core developers are right now attending various Python-related events, I am going to aim for tagging 3.7.1rc2 and 3.6.7rc2 after 2018-10-09 23:59 AoE, if at all possible, with final releases targeted for about 10 days later. I will send out an update as we approach that time. Just a reminder to core developers: as always please try to get fixes merged in to all relevant branches as soon as you feel they are ready. There is no need to hold off during a release candidate phase. Release managers will cherry pick as necessary appropriate fixes from the release branches into subsequent release candidates or final releases. The sooner changes are merged, the sooner they will get buildbot exposure and potential exposure in the wider community. Thanks! -- 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
