StarMirror
/
peps
mirror of https://github.com/python/peps
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
peps/pep-0200/index.html

477 lines
28 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters!

This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.

<!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 200 – Python 2.0 Release Schedule | peps.python.org</title>
<link rel="shortcut icon" href="../_static/py.png">
<link rel="canonical" href="https://peps.python.org/pep-0200/">
<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 200 – Python 2.0 Release Schedule | peps.python.org'>
<meta property="og:type" content="website">
<meta property="og:url" content="https://peps.python.org/pep-0200/">
<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="Python Enhancement Proposals (PEPs)">
<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> &raquo; </li>
<li><a href="../pep-0000/">PEP Index</a> &raquo; </li>
<li>PEP 200</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 200 – Python 2.0 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 &lt;jeremy&#32;&#97;t&#32;alum.mit.edu&gt;</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">12-Jul-2000</dd>
<dt class="field-even">Python-Version<span class="colon">:</span></dt>
<dd class="field-even">2.0</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="#introduction">Introduction</a></li>
<li><a class="reference internal" href="#release-schedule">Release Schedule</a></li>
<li><a class="reference internal" href="#previous-milestones">Previous milestones</a></li>
<li><a class="reference internal" href="#what-is-release-candidate-1">What is release candidate 1?</a></li>
<li><a class="reference internal" href="#guidelines-for-submitting-patches-and-making-changes">Guidelines for submitting patches and making changes</a></li>
<li><a class="reference internal" href="#failing-test-cases-need-to-get-fixed">Failing test cases need to get fixed</a></li>
<li><a class="reference internal" href="#open-items-need-to-be-resolved-before-2-0-final-release">Open items – Need to be resolved before 2.0 final release</a></li>
<li><a class="reference internal" href="#accepted-and-in-progress">Accepted and in progress</a></li>
<li><a class="reference internal" href="#open-proposed-but-not-accepted-or-rejected">Open: proposed but not accepted or rejected</a></li>
<li><a class="reference internal" href="#previously-failing-test-cases">Previously failing test cases</a></li>
<li><a class="reference internal" href="#open-items-completed-fixed">Open items – completed/fixed</a></li>
<li><a class="reference internal" href="#accepted-and-completed">Accepted and completed</a></li>
<li><a class="reference internal" href="#postponed">Postponed</a></li>
<li><a class="reference internal" href="#rejected">Rejected</a></li>
</ul>
</details></section>
<section id="introduction">
<h2><a class="toc-backref" href="#introduction" role="doc-backlink">Introduction</a></h2>
<p>This PEP describes the Python 2.0 release schedule, tracking the
status and ownership of the major new features, summarizes discussions
held in mailing list forums, and provides URLs for further
information, patches, and other outstanding issues. The CVS revision
history of this file contains the definitive historical record.</p>
</section>
<section id="release-schedule">
<h2><a class="toc-backref" href="#release-schedule" role="doc-backlink">Release Schedule</a></h2>
<p>[revised 5 Oct 2000]</p>
<ul class="simple">
<li>26-Sep-2000: 2.0 beta 2</li>
<li>9-Oct-2000: 2.0 release candidate 1 (2.0c1)</li>
<li>16-Oct-2000: 2.0 final</li>
</ul>
</section>
<section id="previous-milestones">
<h2><a class="toc-backref" href="#previous-milestones" role="doc-backlink">Previous milestones</a></h2>
<ul class="simple">
<li>14-Aug-2000: All 2.0 PEPs finished / feature freeze</li>
<li>5-Sep-2000: 2.0 beta 1</li>
</ul>
</section>
<section id="what-is-release-candidate-1">
<h2><a class="toc-backref" href="#what-is-release-candidate-1" role="doc-backlink">What is release candidate 1?</a></h2>
<p>We believe that release candidate 1 will fix all known bugs that we
intend to fix for the 2.0 final release. This release should be a bit
more stable than the previous betas. We would like to see even more
widespread testing before the final release, so we are producing this
release candidate. The final release will be exactly the same unless
any show-stopping (or brown bag) bugs are found by testers of the
release candidate.</p>
</section>
<section id="guidelines-for-submitting-patches-and-making-changes">
<h2><a class="toc-backref" href="#guidelines-for-submitting-patches-and-making-changes" role="doc-backlink">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 &lt;0.5
wink&gt;. 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 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 id="failing-test-cases-need-to-get-fixed">
<h2><a class="toc-backref" href="#failing-test-cases-need-to-get-fixed" role="doc-backlink">Failing test cases need to get fixed</a></h2>
<p>We need to resolve errors in the regression test suite quickly.
Changes should not be committed to the CVS tree unless the regression
test runs cleanly with the changes applied. If it fails, there may be
bugs lurking in the code. (There may be bugs anyway, but that’s
another matter.) If the test cases are known to fail, they serve no
useful purpose.</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">test</span> <span class="n">case</span> <span class="n">platform</span> <span class="n">date</span> <span class="n">reported</span>
<span class="o">---------</span> <span class="o">--------</span> <span class="o">-------------</span>
<span class="n">test_mmap</span> <span class="n">Win</span> <span class="n">ME</span> <span class="mi">03</span><span class="o">-</span><span class="n">Sep</span><span class="o">-</span><span class="mi">2000</span> <span class="n">Windows</span> <span class="mi">2</span><span class="n">b1p2</span> <span class="n">prelease</span>
<span class="p">[</span><span class="mi">04</span><span class="o">-</span><span class="n">Sep</span><span class="o">-</span><span class="mi">2000</span> <span class="n">tim</span>
<span class="n">reported</span> <span class="n">by</span> <span class="n">Audun</span> <span class="n">S</span><span class="o">.</span> <span class="n">Runde</span> <span class="n">mailto</span><span class="p">:</span><span class="n">audun</span><span class="nd">@mindspring</span><span class="o">.</span><span class="n">com</span>
<span class="n">the</span> <span class="n">mmap</span> <span class="n">constructor</span> <span class="n">fails</span> <span class="n">w</span><span class="o">/</span>
<span class="ne">WindowsError</span><span class="p">:</span> <span class="p">[</span><span class="n">Errno</span> <span class="mi">6</span><span class="p">]</span> <span class="n">The</span> <span class="n">handle</span> <span class="ow">is</span> <span class="n">invalid</span>
<span class="n">since</span> <span class="n">there</span> <span class="n">are</span> <span class="n">no</span> <span class="n">reports</span> <span class="n">of</span> <span class="n">this</span> <span class="n">failing</span> <span class="n">on</span> <span class="n">other</span>
<span class="n">flavors</span> <span class="n">of</span> <span class="n">Windows</span><span class="p">,</span> <span class="n">this</span> <span class="n">looks</span> <span class="n">like</span> <span class="n">to</span> <span class="n">be</span> <span class="n">an</span> <span class="n">ME</span> <span class="n">bug</span>
<span class="p">]</span>
</pre></div>
</div>
</section>
<section id="open-items-need-to-be-resolved-before-2-0-final-release">
<h2><a class="toc-backref" href="#open-items-need-to-be-resolved-before-2-0-final-release" role="doc-backlink">Open items – Need to be resolved before 2.0 final release</a></h2>
<p>Decide whether cycle-gc should be enabled by default.</p>
<p>Resolve compatibility issues between core xml package and the XML-SIG
XML package.</p>
<p>Update Tools/compiler so that it is compatible with list
comprehensions, import as, and any other new language features.</p>
<p>Improve code coverage of test suite.</p>
<p>Finish writing the PEPs for the features that went out with 2.0b1(!
sad, but realistic – we’ll get better with practice).</p>
<p>Major effort to whittle the bug database down to size. I’ve (tim)
seen this before: if you can keep all the open bugs fitting on one
screen, people will generally keep it that way. But let it slobber
over a screen for a month, &amp; it just goes to hell (no “visible
progress” indeed!).</p>
</section>
<section id="accepted-and-in-progress">
<h2><a class="toc-backref" href="#accepted-and-in-progress" role="doc-backlink">Accepted and in progress</a></h2>
<ul class="simple">
<li>Currently none left. [4-Sep-2000 guido]</li>
</ul>
</section>
<section id="open-proposed-but-not-accepted-or-rejected">
<h2><a class="toc-backref" href="#open-proposed-but-not-accepted-or-rejected" role="doc-backlink">Open: proposed but not accepted or rejected</a></h2>
<ul class="simple">
<li>There are a number of open patches again. We need to clear these
out soon.</li>
</ul>
</section>
<section id="previously-failing-test-cases">
<h2><a class="toc-backref" href="#previously-failing-test-cases" role="doc-backlink">Previously failing test cases</a></h2>
<p>If you find a test bouncing between this section and the previous one,
the code it’s testing is in trouble!</p>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>test case platform date reported
--------- -------- -------------
test_fork1 Linux 26-Jul-2000
[28-aug-2000 fixed by cgw; solution is to create copies of
lock in child process]
[19-Aug-2000 tim
Charles Waldman whipped up a patch to give child processes a new
&quot;global lock&quot;:
http://sourceforge.net/patch/?func=detailpatch&amp;patch_id=101226&amp;group_id=5470
While this doesn&#39;t appear to address the symptoms we *saw*, it
*does* so far appear to be fixing the failing cases anyway
]
test_parser all 22-Aug-2000
test_posixpath all 22-Aug-2000
test_popen2 Win32 26-Jul-2000
[31-Aug-2000 tim
This died again, but for an entirely different reason: it uses a
dict to map file pointers to process handles, and calls a dict
access function during popen.close(). But .close releases threads,
which left the internal popen code accessing the dict without a
valid thread state. The dict implementation changed so that&#39;s no
longer accepted. Fixed by creating a temporary thread state in the
guts of popen&#39;s close routine, and grabbing the global lock with
it for the duration]
[20-Aug-2000 tim
changed the popen2.py _test function to use the &quot;more&quot; cmd
when os.name == &quot;nt&quot;. This makes test_popen2 pass under
Win98SE.
HOWEVER, the Win98 &quot;more&quot; invents a leading newline out
of thin air, and I&#39;m not sure that the other Windows flavors
of &quot;more&quot; also do that.
So, somebody please try under other Windows flavors!
]
[still fails 15-Aug-2000 for me, on Win98 - tim
test test_popen2 crashed -- exceptions.AssertionError :
The problem is that the test uses &quot;cat&quot;, but there is
no such thing under Windows (unless you install it).
So it&#39;s the test that&#39;s broken here, not (necessarily)
the code.
]
test_winreg Win32 26-Jul-2000
[works 15-Aug-2000 for me, on Win98 - tim]
test_mmap Win32 26-Jul-2000
[believe that was fixed by Mark H.]
[works 15-Aug-2000 for me, on Win98 - tim]
test_longexp Win98+? 15-Aug-2000
[fails in release build,
passes in release build under verbose mode but doesn&#39;t
look like it should pass,
passes in debug build,
passes in debug build under verbose mode and looks like
it should pass
]
[18-Aug-2000, tim: can&#39;t reproduce, and nobody else
saw it. I believe there *is* a subtle bug in
regrtest.py when using -v, and I&#39;ll pursue that,
but can&#39;t provoke anything wrong with test_longexp
anymore; eyeballing Fred&#39;s changes didn&#39;t turn up
a suspect either
19-Aug-2000, tim: the &quot;subtle bug&quot; in regrtest.py -v is
actually a feature: -v masks *some* kinds of failures,
since it doesn&#39;t compare test output with the canned
output; this is what makes it say &quot;test passed&quot; even
in some cases where the test fails without -v
]
test_winreg2 Win32 26-Jul-2000
[20-Aug-2000 tim - the test has been removed from the project]
[19-Aug-2000 tim
This test will never work on Win98, because it&#39;s looking for
a part of registry that doesn&#39;t exist under W98.
The module (winreg.py) and this test case will be removed
before 2.0 for other reasons, though.
]
[still fails 15-Aug-2000 for me, on Win98 - tim
test test_winreg2 failed -- Writing: &#39;Test Failed: testHives&#39;,
expected: &#39;HKEY_PERFORMANCE_DATA\012&#39;
]
</pre></div>
</div>
</section>
<section id="open-items-completed-fixed">
<h2><a class="toc-backref" href="#open-items-completed-fixed" role="doc-backlink">Open items – completed/fixed</a></h2>
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span>[4-Sep-2000 guido: Fredrik finished this on 1-Sep]
* PyErr_Format - Fredrik Lundh
Make this function safe from buffer overflows.
[4-Sep-2000 guido: Fred has added popen2, popen3 on 28-Sep]
Add popen2 support for Linux -- Fred Drake
[4-Sep-2000 guido: done on 1-Sep]
Deal with buffering problem with SocketServer
[04-Sep-2000 tim: done; installer runs; w9xpopen not an issue]
[01-Sep-2000 tim: make a prerelease available]
Windows ME: Don&#39;t know anything about it. Will the installer
even run? Does it need the w9xpopen hack?
[04-Sep-2000 tim: done; tested on several Windows flavors now]
[01-Sep-2000 tim: completed but untested except on Win98SE]
Windows installer: If HKLM isn&#39;t writable, back off to HKCU (so
Python can be installed on NT &amp; 2000 without admin privileges).
[01-Sep-200 tim - as Guido said, runtime code in posixmodule.c doesn&#39;t
call this on NT/2000, so no need to avoid installing it everywhere.
Added code to the installer *to* install it, though.]
Windows installer: Install w9xpopen.exe only under Win95/98.
[23-Aug-2000 jeremy - tim reports &quot;completed recently&quot;]
Windows: Look for registry info in HKCU before HKLM - Mark
Hammond.
[20-Aug-2000 tim - done]
Remove winreg.py and test_winreg2.py. Paul Prescod (the author)
now wants to make a registry API more like the MS .NET API. Unclear
whether that can be done in time for 2.0, but, regardless, if we
let winreg.py out the door we&#39;ll be stuck with it forever, and not
even Paul wants it anymore.
[24-Aug-2000 tim+guido - done]
Win98 Guido: popen is hanging on Guido, and even freezing the
whole machine. Was caused by Norton Antivirus 2000 (6.10.20) on
Windows 9x. Resolution: disable virus protection.
</pre></div>
</div>
</section>
<section id="accepted-and-completed">
<h2><a class="toc-backref" href="#accepted-and-completed" role="doc-backlink">Accepted and completed</a></h2>
<ul class="simple">
<li>Change meaning of x escapes - <a class="pep reference internal" href="../pep-0223/" title="PEP 223 – Change the Meaning of \x Escapes">PEP 223</a> - Fredrik Lundh</li>
<li>Add U1234678 escapes in u”” strings - Fredrik Lundh</li>
<li>Support for opcode arguments &gt; <code class="docutils literal notranslate"><span class="pre">2**16</span></code> - Charles Waldman SF Patch
100893</li>
<li>“import as” - Thomas Wouters Extend the ‘import’ and ‘from …
import’ mechanism to enable importing a symbol as another name.
(Without adding a new keyword.)</li>
<li>List comprehensions - Skip Montanaro Tim Peters still needs to do
PEP.</li>
<li>Restore old os.path.commonprefix behavior Do we have test cases that
work on all platforms?</li>
<li>Tim O’Malley’s cookie module with good license</li>
<li>Lockstep iteration (“zip” function) - Barry Warsaw</li>
<li>SRE - Fredrik Lundh [at least I <strong>think</strong> it’s done, as of
15-Aug-2000 - tim]</li>
<li>Fix xrange printing behavior - Fred Drake Remove the tp_print
handler for the xrange type; it produced a list display instead of
‘xrange(…)’. The new code produces a minimal call to xrange(),
enclosed in (<code class="docutils literal notranslate"><span class="pre">...</span> <span class="pre">*</span> <span class="pre">N</span></code>) when N != 1. This makes the repr() more
human readable while making it do what reprs are advertised as
doing. It also makes the xrange objects obvious when working in the
interactive interpreter.</li>
<li>Extended print statement - Barry Warsaw <a class="pep reference internal" href="../pep-0214/" title="PEP 214 – Extended Print Statement">PEP 214</a>
SF Patch #100970
<a class="reference external" href="http://sourceforge.net/patch/?func=detailpatch&amp;patch_id=100970&amp;group_id=5470">http://sourceforge.net/patch/?func=detailpatch&amp;patch_id=100970&amp;group_id=5470</a></li>
<li>interface to poll system call - Andrew Kuchling SF Patch 100852</li>
<li>Augmented assignment - Thomas Wouters Add += and family, plus Python
and C hooks, and API functions.</li>
<li>gettext.py module - Barry Warsaw</li>
</ul>
</section>
<section id="postponed">
<h2><a class="toc-backref" href="#postponed" role="doc-backlink">Postponed</a></h2>
<ul>
<li>Extended slicing on lists - Michael Hudson Make lists (and other
builtin types) handle extended slices.</li>
<li>Compression of Unicode database - Fredrik Lundh SF Patch 100899 At
least for 2.0b1. May be included in 2.0 as a bug fix.</li>
<li>Range literals - Thomas Wouters SF Patch 100902 We ended up having a
lot of doubt about the proposal.</li>
<li>Eliminated SET_LINENO opcode - Vladimir Marangozov Small
optimization achieved by using the code object’s lnotab instead of
the SET_LINENO instruction. Uses code rewriting technique (that
Guido’s frowns on) to support debugger, which uses SET_LINENO.<p><a class="reference external" href="http://starship.python.net/~vlad/lineno/">http://starship.python.net/~vlad/lineno/</a> for (working at the time)
patches</p>
<p>Discussions on python-dev:</p>
<ul class="simple">
<li><a class="reference external" href="http://www.python.org/pipermail/python-dev/2000-April/subject.html">http://www.python.org/pipermail/python-dev/2000-April/subject.html</a>
Subject: “Why do we need Traceback Objects?”</li>
<li><a class="reference external" href="http://www.python.org/pipermail/python-dev/1999-August/002252.html">http://www.python.org/pipermail/python-dev/1999-August/002252.html</a></li>
</ul>
</li>
<li>test harness for C code - Trent Mick</li>
</ul>
</section>
<section id="rejected">
<h2><a class="toc-backref" href="#rejected" role="doc-backlink">Rejected</a></h2>
<ul class="simple">
<li>‘indexing-for’ - Thomas Wouters Special syntax to give Python code
access to the loop-counter in ‘for’ loops. (Without adding a new
keyword.)</li>
</ul>
</section>
</section>
<hr class="docutils" />
<p>Source: <a class="reference external" href="https://github.com/python/peps/blob/main/peps/pep-0200.rst">https://github.com/python/peps/blob/main/peps/pep-0200.rst</a></p>
<p>Last modified: <a class="reference external" href="https://github.com/python/peps/commits/main/peps/pep-0200.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="#introduction">Introduction</a></li>
<li><a class="reference internal" href="#release-schedule">Release Schedule</a></li>
<li><a class="reference internal" href="#previous-milestones">Previous milestones</a></li>
<li><a class="reference internal" href="#what-is-release-candidate-1">What is release candidate 1?</a></li>
<li><a class="reference internal" href="#guidelines-for-submitting-patches-and-making-changes">Guidelines for submitting patches and making changes</a></li>
<li><a class="reference internal" href="#failing-test-cases-need-to-get-fixed">Failing test cases need to get fixed</a></li>
<li><a class="reference internal" href="#open-items-need-to-be-resolved-before-2-0-final-release">Open items – Need to be resolved before 2.0 final release</a></li>
<li><a class="reference internal" href="#accepted-and-in-progress">Accepted and in progress</a></li>
<li><a class="reference internal" href="#open-proposed-but-not-accepted-or-rejected">Open: proposed but not accepted or rejected</a></li>
<li><a class="reference internal" href="#previously-failing-test-cases">Previously failing test cases</a></li>
<li><a class="reference internal" href="#open-items-completed-fixed">Open items – completed/fixed</a></li>
<li><a class="reference internal" href="#accepted-and-completed">Accepted and completed</a></li>
<li><a class="reference internal" href="#postponed">Postponed</a></li>
<li><a class="reference internal" href="#rejected">Rejected</a></li>
</ul>
<br>
<a id="source" href="https://github.com/python/peps/blob/main/peps/pep-0200.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>
Reference in New Issue View Git Blame Copy Permalink