From 6c7fa9746f961897b3b6f651671fd7e1a1318d31 Mon Sep 17 00:00:00 2001 From: CAM Gerlach Date: Thu, 20 Jan 2022 02:04:25 -0600 Subject: [PATCH] PEP 639: Update PEP delegate, post history and CODEOWNERS (GH-2228) --- .github/CODEOWNERS | 2 +- pep-0639.rst | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index c6809c133..17485f508 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -507,7 +507,7 @@ pep-0635.rst @brandtbucher @gvanrossum pep-0636.rst @brandtbucher @gvanrossum pep-0637.rst @stevendaprano pep-0638.rst @markshannon -pep-0639.rst @pfmoore +pep-0639.rst @pfmoore @CAM-Gerlach pep-0640.rst @Yhg1s pep-0641.rst @zooba @warsaw @brettcannon pep-0642.rst @ncoghlan diff --git a/pep-0639.rst b/pep-0639.rst index d628e43af..9c7e8b15c 100644 --- a/pep-0639.rst +++ b/pep-0639.rst @@ -5,13 +5,13 @@ Last-Modified: $Date$ Author: Philippe Ombredanne , C.A.M. Gerlach Sponsor: Paul Moore -PEP-Delegate: Paul Moore +PEP-Delegate: Brett Cannon Discussions-To: https://discuss.python.org/t/12622 Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 15-Aug-2019 -Post-History: +Post-History: 15-Aug-2019, 17-Dec-2021 Resolution: @@ -1396,7 +1396,7 @@ but re-using the ``license`` key for the license expression, either by defining it as the (previously reserved) string value for the ``license`` key, retaining the ``expression`` subkey in the ``license`` table, or allowing both. Indeed, this would seem to have been envisioned by PEP 621 -itself with this PEP in mind, in particular the first approach:: +itself with this PEP in mind, in particular the first approach: A practical string value for the license key has been purposefully left out to allow for a future PEP to specify support for SPDX expressions