prompt: You will be provided with a partial code base and an issue statement explaining a problem to resolve.
  <issue>
  "PEP numbers never change" verbiage is not in PEP 1
  ## Problem
  
  The introduction to PEP 0 references PEP 1 as a source for
  
  > PEP numbers are assigned by the PEP editors, and once assigned are never changed [1].
  
  But PEP 1 doesn't say anything about PEP numbers never changing.
  
  ## Research
  
  While skimming PEP 1, I found information about the PEP editor assigning a number:
  
  > Once the PEP is ready for the repository, a PEP editor will:
  Assign a PEP number (almost always just the next available number, but sometimes it's a special/joke number, like 666 or 3141). (Clarification: For Python 3, numbers in the 3000s were used for Py3k-specific proposals. But now that all new features go into Python 3 only, the process is back to using numbers in the 100s again. Remember that numbers below 100 are meta-PEPs.)
  
  and
  
  > The PEP editors are individuals responsible for managing the administrative and editorial aspects of the PEP workflow (e.g. assigning PEP numbers and changing their status). See PEP Editor Responsibilities & Workflow for details.
  
  But I didn't find any reference to that number never changing. 
  
  ## Proposal:
  
  Can we change PEP 0's introduction so that the reference is specific to assigning numbers?
  
  ```
  PEP numbers are assigned by the PEP editors[1], and once assigned are never changed.
  ```
  
  ## Link
  
  https://github.com/python/peps/blob/40ef5625b7d42655f49090ffd2c0860ecf8d1d9f/pep0/constants.py#L22-L27
  
  </issue>
  <code>
  [start of pep0/constants.py]
  1 # -*- coding: utf-8 -*-
  2 text_type = str
  3 title_length = 55
  4 author_length = 40
  5 table_separator = "== ====  " + "="*title_length + " " + "="*author_length
  6 column_format = (
  7     '%(type)1s%(status)1s %(number)4s  %(title)-{title_length}s %(authors)-s'
  8 ).format(title_length=title_length)
  9 
  10 header = """\
  11 PEP: 0
  12 Title: Index of Python Enhancement Proposals (PEPs)
  13 Version: N/A
  14 Last-Modified: %s
  15 Author: python-dev <python-dev@python.org>
  16 Status: Active
  17 Type: Informational
  18 Content-Type: text/x-rst
  19 Created: 13-Jul-2000
  20 """
  21 
  22 intro = """\
  23 This PEP contains the index of all Python Enhancement Proposals,
  24 known as PEPs.  PEP numbers are assigned by the PEP editors, and
  25 once assigned are never changed [1_].  The version control history [2_] of
  26 the PEP texts represent their historical record.
  27 """
  28 
  29 references = """\
  30 .. [1] PEP 1: PEP Purpose and Guidelines
  31 .. [2] View PEP history online: https://github.com/python/peps
  32 """
  33 
  34 footer = """\
  35 ..
  36    Local Variables:
  37    mode: indented-text
  38    indent-tabs-mode: nil
  39    sentence-end-double-space: t
  40    fill-column: 70
  41    coding: utf-8
  42    End:\
  43 """
  44
  [end of pep0/constants.py]
  </code>
  
  I need you to solve this issue by generating a single patch file that I can apply directly to this repository using git apply. Please respond with a single patch file in the following format.
  <patch>
  diff --git a/file.py b/file.py
  --- a/file.py
  +++ b/file.py
  @@ -1,27 +1,35 @@
   def euclidean(a, b):
  -    while b:
  -        a, b = b, a % b
  -    return a
  +    if b == 0:
  +        return a
  +    return euclidean(b, a % b)
   
   
   def bresenham(x0, y0, x1, y1):
       points = []
       dx = abs(x1 - x0)
       dy = abs(y1 - y0)
  -    sx = 1 if x0 < x1 else -1
  -    sy = 1 if y0 < y1 else -1
  -    err = dx - dy
  +    x, y = x0, y0
  +    sx = -1 if x0 > x1 else 1
  +    sy = -1 if y0 > y1 else 1
   
  -    while True:
  -        points.append((x0, y0))
  -        if x0 == x1 and y0 == y1:
  -            break
  -        e2 = 2 * err
  -        if e2 > -dy:
  -            err -= dy
  -            x0 += sx
  -        if e2 < dx:
  -            err += dx
  -            y0 += sy
  +    if dx > dy:
  +        err = dx / 2.0
  +        while x != x1:
  +            points.append((x, y))
  +            err -= dy
  +            if err < 0:
  +                y += sy
  +                err += dx
  +            x += sx
  +    else:
  +        err = dy / 2.0
  +        while y != y1:
  +            points.append((x, y))
  +            err -= dx
  +            if err < 0:
  +                x += sx
  +                err += dy
  +            y += sy
  +
  +    points.append((x, y))
       return points
  
  </patch>
golden_diff: diff --git a/pep0/constants.py b/pep0/constants.py
  --- a/pep0/constants.py
  +++ b/pep0/constants.py
  @@ -21,8 +21,8 @@
   
   intro = """\
   This PEP contains the index of all Python Enhancement Proposals,
  -known as PEPs.  PEP numbers are assigned by the PEP editors, and
  -once assigned are never changed [1_].  The version control history [2_] of
  +known as PEPs.  PEP numbers are assigned by the PEP editors[1_], and
  +once assigned are never changed.  The version control history [2_] of
   the PEP texts represent their historical record.
   """
  
verification_info: {"golden_diff": "diff --git a/pep0/constants.py b/pep0/constants.py\n--- a/pep0/constants.py\n+++ b/pep0/constants.py\n@@ -21,8 +21,8 @@\n \n intro = \"\"\"\\\n This PEP contains the index of all Python Enhancement Proposals,\n-known as PEPs.  PEP numbers are assigned by the PEP editors, and\n-once assigned are never changed [1_].  The version control history [2_] of\n+known as PEPs.  PEP numbers are assigned by the PEP editors[1_], and\n+once assigned are never changed.  The version control history [2_] of\n the PEP texts represent their historical record.\n \"\"\"\n", "issue": "\"PEP numbers never change\" verbiage is not in PEP 1\n## Problem\r\n\r\nThe introduction to PEP 0 references PEP 1 as a source for\r\n\r\n> PEP numbers are assigned by the PEP editors, and once assigned are never changed [1].\r\n\r\nBut PEP 1 doesn't say anything about PEP numbers never changing.\r\n\r\n## Research\r\n\r\nWhile skimming PEP 1, I found information about the PEP editor assigning a number:\r\n\r\n> Once the PEP is ready for the repository, a PEP editor will:\r\nAssign a PEP number (almost always just the next available number, but sometimes it's a special/joke number, like 666 or 3141). (Clarification: For Python 3, numbers in the 3000s were used for Py3k-specific proposals. But now that all new features go into Python 3 only, the process is back to using numbers in the 100s again. Remember that numbers below 100 are meta-PEPs.)\r\n\r\nand\r\n\r\n> The PEP editors are individuals responsible for managing the administrative and editorial aspects of the PEP workflow (e.g. assigning PEP numbers and changing their status). See PEP Editor Responsibilities & Workflow for details.\r\n\r\nBut I didn't find any reference to that number never changing. \r\n\r\n## Proposal:\r\n\r\nCan we change PEP 0's introduction so that the reference is specific to assigning numbers?\r\n\r\n```\r\nPEP numbers are assigned by the PEP editors[1], and once assigned are never changed.\r\n```\r\n\r\n## Link\r\n\r\nhttps://github.com/python/peps/blob/40ef5625b7d42655f49090ffd2c0860ecf8d1d9f/pep0/constants.py#L22-L27\n", "before_files": [{"content": "# -*- coding: utf-8 -*-\ntext_type = str\ntitle_length = 55\nauthor_length = 40\ntable_separator = \"== ====  \" + \"=\"*title_length + \" \" + \"=\"*author_length\ncolumn_format = (\n    '%(type)1s%(status)1s %(number)4s  %(title)-{title_length}s %(authors)-s'\n).format(title_length=title_length)\n\nheader = \"\"\"\\\nPEP: 0\nTitle: Index of Python Enhancement Proposals (PEPs)\nVersion: N/A\nLast-Modified: %s\nAuthor: python-dev <python-dev@python.org>\nStatus: Active\nType: Informational\nContent-Type: text/x-rst\nCreated: 13-Jul-2000\n\"\"\"\n\nintro = \"\"\"\\\nThis PEP contains the index of all Python Enhancement Proposals,\nknown as PEPs.  PEP numbers are assigned by the PEP editors, and\nonce assigned are never changed [1_].  The version control history [2_] of\nthe PEP texts represent their historical record.\n\"\"\"\n\nreferences = \"\"\"\\\n.. [1] PEP 1: PEP Purpose and Guidelines\n.. [2] View PEP history online: https://github.com/python/peps\n\"\"\"\n\nfooter = \"\"\"\f\\\n..\n   Local Variables:\n   mode: indented-text\n   indent-tabs-mode: nil\n   sentence-end-double-space: t\n   fill-column: 70\n   coding: utf-8\n   End:\\\n\"\"\"\n", "path": "pep0/constants.py"}]}