From be94151aafd790294b4815dbf015130177e77347 Mon Sep 17 00:00:00 2001 From: Philippe Ombredanne Date: Fri, 16 Oct 2020 21:39:49 +0200 Subject: [PATCH] PEP 639: Minor typo fixes (#1656) --- pep-0639.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pep-0639.rst b/pep-0639.rst index 4153a411d..8b79e29a7 100644 --- a/pep-0639.rst +++ b/pep-0639.rst @@ -9,7 +9,7 @@ Discussions-To: https://discuss.python.org/t/2154 Status: Draft Type: Standards Track Content-Type: text/x-rst -Created: 15-Aug-2018 +Created: 15-Aug-2019 Python-Version: 3.x Post-History: Replaces: 566 @@ -441,13 +441,13 @@ are documented by adding an additional nesting level. A mapping would be needed as you cannot guarantee that all expressions (e.g. a GPL with an exception may be in a single file) or all the license keys have a single license file and that any expression does not have more than one. (e.g. -an Apache license ``LICENSE`` and its ``NOTICE`` file for instance are tow +an Apache license ``LICENSE`` and its ``NOTICE`` file for instance are two distinct file). Yet in most cases, there is a simpler `one license`, `one or more license files`. In the rarer and more complex cases where there are many licenses involved you can still use the proposed conventions at the cost of a slight loss of clarity by not specifying which text file is for which license -id, but you are not forcing the more complex data model (e.g. a mapping) on -everyone that may not need it. +identifier, but you are not forcing the more complex data model (e.g. a mapping) +on everyone that may not need it. We could of course have data field with multiple possible value types (it’s a string, it’s a list, it’s a mapping!) but this could be a source of confusion. @@ -642,7 +642,7 @@ globally once in a shared documentation directory (e.g. /usr/share/doc). - Fedora RPM packages [#fedora]_ specifies how to include ``License Texts`` [#fedoratext]_ and how use a ``License`` field [#fedoralic]_ that must be filled with an appropriate license Short License identifier(s) from an extensive list - of "Good Licenses" identifiers [#fedoralist]_. Fedora also defines ist own + of "Good Licenses" identifiers [#fedoralist]_. Fedora also defines its own license expression syntax very similar to the SDPX syntax. - OpenSuse RPMs packages [#opensuse]_ use SPDX license expressions with a