226 lines
14 KiB
HTML
226 lines
14 KiB
HTML
|
||
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<meta name="color-scheme" content="light dark">
|
||
<title>PEP 226 – Python 2.1 Release Schedule | peps.python.org</title>
|
||
<link rel="shortcut icon" href="../_static/py.png">
|
||
<link rel="canonical" href="https://peps.python.org/pep-0226/">
|
||
<link rel="stylesheet" href="../_static/style.css" type="text/css">
|
||
<link rel="stylesheet" href="../_static/mq.css" type="text/css">
|
||
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" media="(prefers-color-scheme: light)" id="pyg-light">
|
||
<link rel="stylesheet" href="../_static/pygments_dark.css" type="text/css" media="(prefers-color-scheme: dark)" id="pyg-dark">
|
||
<link rel="alternate" type="application/rss+xml" title="Latest PEPs" href="https://peps.python.org/peps.rss">
|
||
<meta property="og:title" content='PEP 226 – Python 2.1 Release Schedule | peps.python.org'>
|
||
<meta property="og:description" content="This document describes the post Python 2.0 development and release schedule. According to this schedule, Python 2.1 will be released in April of 2001. The schedule primarily concerns itself with PEP-size items. Small bug fixes and changes will occur...">
|
||
<meta property="og:type" content="website">
|
||
<meta property="og:url" content="https://peps.python.org/pep-0226/">
|
||
<meta property="og:site_name" content="Python Enhancement Proposals (PEPs)">
|
||
<meta property="og:image" content="https://peps.python.org/_static/og-image.png">
|
||
<meta property="og:image:alt" content="Python PEPs">
|
||
<meta property="og:image:width" content="200">
|
||
<meta property="og:image:height" content="200">
|
||
<meta name="description" content="This document describes the post Python 2.0 development and release schedule. According to this schedule, Python 2.1 will be released in April of 2001. The schedule primarily concerns itself with PEP-size items. Small bug fixes and changes will occur...">
|
||
<meta name="theme-color" content="#3776ab">
|
||
</head>
|
||
<body>
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" style="display: none;">
|
||
<symbol id="svg-sun-half" viewBox="0 0 24 24" pointer-events="all">
|
||
<title>Following system colour scheme</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none"
|
||
stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
|
||
<circle cx="12" cy="12" r="9"></circle>
|
||
<path d="M12 3v18m0-12l4.65-4.65M12 14.3l7.37-7.37M12 19.6l8.85-8.85"></path>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-moon" viewBox="0 0 24 24" pointer-events="all">
|
||
<title>Selected dark colour scheme</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none"
|
||
stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
|
||
<path stroke="none" d="M0 0h24v24H0z" fill="none"></path>
|
||
<path d="M12 3c.132 0 .263 0 .393 0a7.5 7.5 0 0 0 7.92 12.446a9 9 0 1 1 -8.313 -12.454z"></path>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-sun" viewBox="0 0 24 24" pointer-events="all">
|
||
<title>Selected light colour scheme</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none"
|
||
stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">
|
||
<circle cx="12" cy="12" r="5"></circle>
|
||
<line x1="12" y1="1" x2="12" y2="3"></line>
|
||
<line x1="12" y1="21" x2="12" y2="23"></line>
|
||
<line x1="4.22" y1="4.22" x2="5.64" y2="5.64"></line>
|
||
<line x1="18.36" y1="18.36" x2="19.78" y2="19.78"></line>
|
||
<line x1="1" y1="12" x2="3" y2="12"></line>
|
||
<line x1="21" y1="12" x2="23" y2="12"></line>
|
||
<line x1="4.22" y1="19.78" x2="5.64" y2="18.36"></line>
|
||
<line x1="18.36" y1="5.64" x2="19.78" y2="4.22"></line>
|
||
</svg>
|
||
</symbol>
|
||
</svg>
|
||
<script>
|
||
|
||
document.documentElement.dataset.colour_scheme = localStorage.getItem("colour_scheme") || "auto"
|
||
</script>
|
||
<section id="pep-page-section">
|
||
<header>
|
||
<h1>Python Enhancement Proposals</h1>
|
||
<ul class="breadcrumbs">
|
||
<li><a href="https://www.python.org/" title="The Python Programming Language">Python</a> » </li>
|
||
<li><a href="../pep-0000/">PEP Index</a> » </li>
|
||
<li>PEP 226</li>
|
||
</ul>
|
||
<button id="colour-scheme-cycler" onClick="setColourScheme(nextColourScheme())">
|
||
<svg aria-hidden="true" class="colour-scheme-icon-when-auto"><use href="#svg-sun-half"></use></svg>
|
||
<svg aria-hidden="true" class="colour-scheme-icon-when-dark"><use href="#svg-moon"></use></svg>
|
||
<svg aria-hidden="true" class="colour-scheme-icon-when-light"><use href="#svg-sun"></use></svg>
|
||
<span class="visually-hidden">Toggle light / dark / auto colour theme</span>
|
||
</button>
|
||
</header>
|
||
<article>
|
||
<section id="pep-content">
|
||
<h1 class="page-title">PEP 226 – Python 2.1 Release Schedule</h1>
|
||
<dl class="rfc2822 field-list simple">
|
||
<dt class="field-odd">Author<span class="colon">:</span></dt>
|
||
<dd class="field-odd">Jeremy Hylton <jeremy at alum.mit.edu></dd>
|
||
<dt class="field-even">Status<span class="colon">:</span></dt>
|
||
<dd class="field-even"><abbr title="Accepted and implementation complete, or no longer active">Final</abbr></dd>
|
||
<dt class="field-odd">Type<span class="colon">:</span></dt>
|
||
<dd class="field-odd"><abbr title="Non-normative PEP containing background, guidelines or other information relevant to the Python ecosystem">Informational</abbr></dd>
|
||
<dt class="field-even">Topic<span class="colon">:</span></dt>
|
||
<dd class="field-even"><a class="reference external" href="../topic/release/">Release</a></dd>
|
||
<dt class="field-odd">Created<span class="colon">:</span></dt>
|
||
<dd class="field-odd">16-Oct-2000</dd>
|
||
<dt class="field-even">Python-Version<span class="colon">:</span></dt>
|
||
<dd class="field-even">2.1</dd>
|
||
<dt class="field-odd">Post-History<span class="colon">:</span></dt>
|
||
<dd class="field-odd"><p></p></dd>
|
||
</dl>
|
||
<hr class="docutils" />
|
||
<section id="contents">
|
||
<details><summary>Table of Contents</summary><ul class="simple">
|
||
<li><a class="reference internal" href="#abstract">Abstract</a></li>
|
||
<li><a class="reference internal" href="#release-schedule">Release Schedule</a></li>
|
||
<li><a class="reference internal" href="#open-issues-for-python-2-0-beta-2">Open issues for Python 2.0 beta 2</a></li>
|
||
<li><a class="reference internal" href="#guidelines-for-making-changes-for-python-2-1">Guidelines for making changes for Python 2.1</a></li>
|
||
<li><a class="reference internal" href="#general-guidelines-for-submitting-patches-and-making-changes">General guidelines for submitting patches and making changes</a></li>
|
||
</ul>
|
||
</details></section>
|
||
<section id="abstract">
|
||
<h2><a class="toc-backref" href="#abstract" role="doc-backlink">Abstract</a></h2>
|
||
<p>This document describes the post Python 2.0 development and
|
||
release schedule. According to this schedule, Python 2.1 will be
|
||
released in April of 2001. The schedule primarily concerns
|
||
itself with PEP-size items. Small bug fixes and changes will
|
||
occur up until the first beta release.</p>
|
||
</section>
|
||
<section id="release-schedule">
|
||
<h2><a class="toc-backref" href="#release-schedule" role="doc-backlink">Release Schedule</a></h2>
|
||
<p>Tentative future release dates</p>
|
||
<p>[bugfix release dates go here]</p>
|
||
<p>Past release dates:</p>
|
||
<ul class="simple">
|
||
<li>17-Apr-2001: 2.1 final release</li>
|
||
<li>15-Apr-2001: 2.1 release candidate 2</li>
|
||
<li>13-Apr-2001: 2.1 release candidate 1</li>
|
||
<li>23-Mar-2001: Python 2.1 beta 2 release</li>
|
||
<li>02-Mar-2001: First 2.1 beta release</li>
|
||
<li>02-Feb-2001: Python 2.1 alpha 2 release</li>
|
||
<li>22-Jan-2001: Python 2.1 alpha 1 release</li>
|
||
<li>16-Oct-2000: Python 2.0 final release</li>
|
||
</ul>
|
||
</section>
|
||
<section id="open-issues-for-python-2-0-beta-2">
|
||
<h2><a class="toc-backref" href="#open-issues-for-python-2-0-beta-2" role="doc-backlink">Open issues for Python 2.0 beta 2</a></h2>
|
||
<p>Add a default unit testing framework to the standard library.</p>
|
||
</section>
|
||
<section id="guidelines-for-making-changes-for-python-2-1">
|
||
<h2><a class="toc-backref" href="#guidelines-for-making-changes-for-python-2-1" role="doc-backlink">Guidelines for making changes for Python 2.1</a></h2>
|
||
<p>The guidelines and schedule will be revised based on discussion in
|
||
the <a class="reference external" href="mailto:python-dev%40python.org">python-dev<span>@</span>python<span>.</span>org</a> mailing list.</p>
|
||
<p>The PEP system was instituted late in the Python 2.0 development
|
||
cycle and many changes did not follow the process described in <a class="pep reference internal" href="../pep-0001/" title="PEP 1 – PEP Purpose and Guidelines">PEP 1</a>.
|
||
The development process for 2.1, however, will follow the PEP
|
||
process as documented.</p>
|
||
<p>The first eight weeks following 2.0 final will be the design and
|
||
review phase. By the end of this period, any PEP that is proposed
|
||
for 2.1 should be ready for review. This means that the PEP is
|
||
written and discussion has occurred on the <a class="reference external" href="mailto:python-dev%40python.org">python-dev<span>@</span>python<span>.</span>org</a>
|
||
and <a class="reference external" href="mailto:python-list%40python.org">python-list<span>@</span>python<span>.</span>org</a> mailing lists.</p>
|
||
<p>The next six weeks will be spent reviewing the PEPs and
|
||
implementing and testing the accepted PEPs. When this period
|
||
stops, we will end consideration of any incomplete PEPs. Near the
|
||
end of this period, there will be a feature freeze where any small
|
||
features not worthy of a PEP will not be accepted.</p>
|
||
<p>Before the final release, we will have six weeks of beta testing
|
||
and a release candidate or two.</p>
|
||
</section>
|
||
<section id="general-guidelines-for-submitting-patches-and-making-changes">
|
||
<h2><a class="toc-backref" href="#general-guidelines-for-submitting-patches-and-making-changes" role="doc-backlink">General guidelines for submitting patches and making changes</a></h2>
|
||
<p>Use good sense when committing changes. You should know what we
|
||
mean by good sense or we wouldn’t have given you commit privileges
|
||
<0.5 wink>. Some specific examples of good sense include:</p>
|
||
<ul class="simple">
|
||
<li>Do whatever the dictator tells you.</li>
|
||
<li>Discuss any controversial changes on python-dev first. If you
|
||
get a lot of +1 votes and no -1 votes, make the change. If you
|
||
get a some -1 votes, think twice; consider asking Guido what he
|
||
thinks.</li>
|
||
<li>If the change is to code you contributed, it probably makes
|
||
sense for you to fix it.</li>
|
||
<li>If the change affects code someone else wrote, it probably makes
|
||
sense to ask him or her first.</li>
|
||
<li>You can use the SourceForge (SF) Patch Manager to submit a patch
|
||
and assign it to someone for review.</li>
|
||
</ul>
|
||
<p>Any significant new feature must be described in a PEP and
|
||
approved before it is checked in.</p>
|
||
<p>Any significant code addition, such as a new module or large
|
||
patch, must include test cases for the regression test and
|
||
documentation. A patch should not be checked in until the tests
|
||
and documentation are ready.</p>
|
||
<p>If you fix a bug, you should write a test case that would have
|
||
caught the bug.</p>
|
||
<p>If you commit a patch from the SF Patch Manager or fix a bug from
|
||
the Jitterbug database, be sure to reference the patch/bug number
|
||
in the CVS log message. Also be sure to change the status in the
|
||
patch manager or bug database (if you have access to the bug
|
||
database).</p>
|
||
<p>It is not acceptable for any checked in code to cause the
|
||
regression test to fail. If a checkin causes a failure, it must
|
||
be fixed within 24 hours or it will be backed out.</p>
|
||
<p>All contributed C code must be ANSI C. If possible check it with
|
||
two different compilers, e.g. gcc and MSVC.</p>
|
||
<p>All contributed Python code must follow Guido’s Python style
|
||
guide. <a class="reference external" href="http://www.python.org/doc/essays/styleguide.html">http://www.python.org/doc/essays/styleguide.html</a></p>
|
||
<p>It is understood that any code contributed will be released under
|
||
an Open Source license. Do not contribute code if it can’t be
|
||
released this way.</p>
|
||
</section>
|
||
</section>
|
||
<hr class="docutils" />
|
||
<p>Source: <a class="reference external" href="https://github.com/python/peps/blob/main/peps/pep-0226.rst">https://github.com/python/peps/blob/main/peps/pep-0226.rst</a></p>
|
||
<p>Last modified: <a class="reference external" href="https://github.com/python/peps/commits/main/peps/pep-0226.rst">2023-09-09 17:39:29 GMT</a></p>
|
||
|
||
</article>
|
||
<nav id="pep-sidebar">
|
||
<h2>Contents</h2>
|
||
<ul>
|
||
<li><a class="reference internal" href="#abstract">Abstract</a></li>
|
||
<li><a class="reference internal" href="#release-schedule">Release Schedule</a></li>
|
||
<li><a class="reference internal" href="#open-issues-for-python-2-0-beta-2">Open issues for Python 2.0 beta 2</a></li>
|
||
<li><a class="reference internal" href="#guidelines-for-making-changes-for-python-2-1">Guidelines for making changes for Python 2.1</a></li>
|
||
<li><a class="reference internal" href="#general-guidelines-for-submitting-patches-and-making-changes">General guidelines for submitting patches and making changes</a></li>
|
||
</ul>
|
||
|
||
<br>
|
||
<a id="source" href="https://github.com/python/peps/blob/main/peps/pep-0226.rst">Page Source (GitHub)</a>
|
||
</nav>
|
||
</section>
|
||
<script src="../_static/colour_scheme.js"></script>
|
||
<script src="../_static/wrap_tables.js"></script>
|
||
<script src="../_static/sticky_banner.js"></script>
|
||
</body>
|
||
</html> |