CINXE.COM

<!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 283 – Python 2.3 Release Schedule | peps.python.org</title> <link rel="shortcut icon" href="../_static/py.png"> <link rel="canonical" href="https://peps.python.org/pep-0283/"> <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 283 – Python 2.3 Release Schedule | peps.python.org'> <meta property="og:description" content="This document describes the development and release schedule for Python 2.3. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the final release."> <meta property="og:type" content="website"> <meta property="og:url" content="https://peps.python.org/pep-0283/"> <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 development and release schedule for Python 2.3. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the final release."> <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 283</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 283 – Python 2.3 Release Schedule</h1> <dl class="rfc2822 field-list simple"> <dt class="field-odd">Author<span class="colon">:</span></dt> <dd class="field-odd">Guido van Rossum</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">27-Feb-2002</dd> <dt class="field-even">Python-Version<span class="colon">:</span></dt> <dd class="field-even">2.3</dd> <dt class="field-odd">Post-History<span class="colon">:</span></dt> <dd class="field-odd">27-Feb-2002</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-manager">Release Manager</a></li> <li><a class="reference internal" href="#completed-features-for-2-3">Completed features for 2.3</a></li> <li><a class="reference internal" href="#planned-features-for-2-3">Planned features for 2.3</a></li> <li><a class="reference internal" href="#ongoing-tasks">Ongoing tasks</a></li> <li><a class="reference internal" href="#open-issues">Open issues</a></li> <li><a class="reference internal" href="#features-that-did-not-make-it-into-python-2-3">Features that did not make it into Python 2.3</a></li> <li><a class="reference internal" href="#copyright">Copyright</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 development and release schedule for Python 2.3. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the final release.</p> <p>There will be at least two alpha releases, two beta releases, and one release candidate. Alpha and beta releases will be spaced at least 4 weeks apart (except if an emergency release must be made to correct a blunder in the previous release; then the blunder release does not count). Release candidates will be spaced at least one week apart (excepting again blunder corrections).</p> <table class="docutils align-default"> <tbody> <tr class="row-odd"><td>alpha 1</td> <td>31 Dec 2002</td> </tr> <tr class="row-even"><td>alpha 2</td> <td>19 Feb 2003</td> </tr> <tr class="row-odd"><td>beta 1</td> <td>25 Apr 2003</td> </tr> <tr class="row-even"><td>beta 2</td> <td>29 Jun 2003</td> </tr> <tr class="row-odd"><td>candidate 1</td> <td>18 Jul 2003</td> </tr> <tr class="row-even"><td>candidate 2</td> <td>24 Jul 2003</td> </tr> <tr class="row-odd"><td>final</td> <td>29 Jul 2003</td> </tr> </tbody> </table> </section> <section id="release-manager"> <h2><a class="toc-backref" href="#release-manager" role="doc-backlink">Release Manager</a></h2> <p>Barry Warsaw, Jeremy Hylton, Tim Peters</p> </section> <section id="completed-features-for-2-3"> <h2><a class="toc-backref" href="#completed-features-for-2-3" role="doc-backlink">Completed features for 2.3</a></h2> <p>This list is not complete. See <code class="docutils literal notranslate"><span class="pre">Doc/whatsnew/whatsnew23.tex</span></code> in CVS for more, and of course <code class="docutils literal notranslate"><span class="pre">Misc/NEWS</span></code> for the full list.</p> <ul> <li>Tk 8.4 update.</li> <li>The <code class="docutils literal notranslate"><span class="pre">bool</span></code> type and its constants, <code class="docutils literal notranslate"><span class="pre">True</span></code> and <code class="docutils literal notranslate"><span class="pre">False</span></code> (<a class="pep reference internal" href="../pep-0285/" title="PEP 285 – Adding a bool type">PEP 285</a>).</li> <li><code class="docutils literal notranslate"><span class="pre">PyMalloc</span></code> was greatly enhanced and is enabled by default.</li> <li>Universal newline support (<a class="pep reference internal" href="../pep-0278/" title="PEP 278 – Universal Newline Support">PEP 278</a>).</li> <li><a class="pep reference internal" href="../pep-0263/" title="PEP 263 – Defining Python Source Code Encodings">PEP 263</a> Defining Python Source Code Encodings, Lemburg<p>Implemented (at least phase 1, which is all that’s planned for 2.3).</p> </li> <li>Extended slice notation for all built-in sequences. The patch by Michael Hudson is now all checked in.</li> <li>Speed up list iterations by filling <code class="docutils literal notranslate"><span class="pre">tp_iter</span></code> and other tweaks. See <a class="reference external" href="https://bugs.python.org/issue560736">https://bugs.python.org/issue560736</a>; also done for <code class="docutils literal notranslate"><span class="pre">xrange</span></code> and tuples.</li> <li>Timeout sockets. <a class="reference external" href="https://bugs.python.org/issue555085">https://bugs.python.org/issue555085</a></li> <li>Stage B0 of the <code class="docutils literal notranslate"><span class="pre">int</span></code>/<code class="docutils literal notranslate"><span class="pre">long</span></code> integration (<a class="pep reference internal" href="../pep-0237/" title="PEP 237 – Unifying Long Integers and Integers">PEP 237</a>). This means issuing a <code class="docutils literal notranslate"><span class="pre">FutureWarning</span></code> about situations where <code class="docutils literal notranslate"><span class="pre">hex</span></code> or <code class="docutils literal notranslate"><span class="pre">oct</span></code> conversions or left shifts returns a different value for an <code class="docutils literal notranslate"><span class="pre">int</span></code> than for a <code class="docutils literal notranslate"><span class="pre">long</span></code> with the same value. The semantics do <em>not</em> change in Python 2.3; that will happen in Python 2.4.</li> <li>Nuke <code class="docutils literal notranslate"><span class="pre">SET_LINENO</span></code> from all code objects (providing a different way to set debugger breakpoints). This can boost <code class="docutils literal notranslate"><span class="pre">pystone</span></code> by >5%. <a class="reference external" href="https://bugs.python.org/issue587993">https://bugs.python.org/issue587993</a>, now checked in. (Unfortunately the <code class="docutils literal notranslate"><span class="pre">pystone</span></code> boost didn’t happen. What happened?)</li> <li>Write a <code class="docutils literal notranslate"><span class="pre">pymemcompat.h</span></code> that people can bundle with their extensions and then use the 2.3 memory interface with all Pythons in the range 1.5.2 to 2.3. (Michael Hudson checked in <code class="docutils literal notranslate"><span class="pre">Misc/pymemcompat.h</span></code>.)</li> <li>Add a new concept, “pending deprecation”, with associated warning <code class="docutils literal notranslate"><span class="pre">PendingDeprecationWarning</span></code>. This warning is normally suppressed, but can be enabled by a suitable <code class="docutils literal notranslate"><span class="pre">-W</span></code> option. Only a few things use this at this time.</li> <li>Warn when an extension type’s <code class="docutils literal notranslate"><span class="pre">tp_compare</span></code> returns anything except -1, 0 or 1. <a class="reference external" href="https://bugs.python.org/issue472523">https://bugs.python.org/issue472523</a></li> <li>Warn for assignment to <code class="docutils literal notranslate"><span class="pre">None</span></code> (in various forms).</li> <li><a class="pep reference internal" href="../pep-0218/" title="PEP 218 – Adding a Built-In Set Object Type">PEP 218</a> Adding a Built-In Set Object Type, Wilson<p>Alex Martelli contributed a new version of Greg Wilson’s prototype, and I’ve reworked that quite a bit. It’s in the standard library now as the module <code class="docutils literal notranslate"><span class="pre">sets</span></code>, although some details may still change until the first beta release. (There are no plans to make this a built-in type, for now.)</p> </li> <li><a class="pep reference internal" href="../pep-0293/" title="PEP 293 – Codec Error Handling Callbacks">PEP 293</a> Codec error handling callbacks, Dörwald<p>Fully implemented. Error handling in <code class="docutils literal notranslate"><span class="pre">unicode.encode</span></code> or <code class="docutils literal notranslate"><span class="pre">str.decode</span></code> can now be customized.</p> </li> <li><a class="pep reference internal" href="../pep-0282/" title="PEP 282 – A Logging System">PEP 282</a> A Logging System, Mick<p>Vinay Sajip’s implementation has been packagized and imported. (Documentation and unit tests still pending.) <a class="reference external" href="https://bugs.python.org/issue578494">https://bugs.python.org/issue578494</a></p> </li> <li>A modified MRO (Method Resolution Order) algorithm. Consensus is that we should adopt C3. Samuele Pedroni has contributed a draft implementation in C, see <a class="reference external" href="https://bugs.python.org/issue619475">https://bugs.python.org/issue619475</a> This has now been checked in.</li> <li>A new command line option parser. Greg Ward’s Optik package (<a class="reference external" href="http://optik.sf.net">http://optik.sf.net</a>) has been adopted, converted to a single module named <code class="docutils literal notranslate"><span class="pre">optparse</span></code>. See also <a class="reference external" href="http://www.python.org/sigs/getopt-sig/">http://www.python.org/sigs/getopt-sig/</a></li> <li>A standard <code class="docutils literal notranslate"><span class="pre">datetime</span></code> type. This started as a wiki: <a class="reference external" href="http://www.zope.org/Members/fdrake/DateTimeWiki/FrontPage">http://www.zope.org/Members/fdrake/DateTimeWiki/FrontPage</a>. A prototype was coded in <code class="docutils literal notranslate"><span class="pre">nondist/sandbox/datetime/</span></code>. Tim Peters has finished the C implementation and checked it in.</li> <li><a class="pep reference internal" href="../pep-0273/" title="PEP 273 – Import Modules from Zip Archives">PEP 273</a> Import Modules from Zip Archives, Ahlstrom<p>Implemented as a part of the <a class="pep reference internal" href="../pep-0302/" title="PEP 302 – New Import Hooks">PEP 302</a> implementation work.</p> </li> <li><a class="pep reference internal" href="../pep-0302/" title="PEP 302 – New Import Hooks">PEP 302</a> New Import Hooks, JvR<p>Implemented (though the 2.3a1 release contained some bugs that have been fixed post-release).</p> </li> <li>A new pickling protocol. See <a class="pep reference internal" href="../pep-0307/" title="PEP 307 – Extensions to the pickle protocol">PEP 307</a>.</li> <li><a class="pep reference internal" href="../pep-0305/" title="PEP 305 – CSV File API">PEP 305</a> (CSV File API, by Skip Montanaro et al.) is in; this is the csv module.</li> <li>Raymond Hettinger’s <code class="docutils literal notranslate"><span class="pre">itertools</span></code> module is in.</li> <li><a class="pep reference internal" href="../pep-0311/" title="PEP 311 – Simplified Global Interpreter Lock Acquisition for Extensions">PEP 311</a> (Simplified GIL Acquisition for Extensions, by Mark Hammond) has been included in beta 1.</li> <li>Two new <code class="docutils literal notranslate"><span class="pre">PyArg_Parse*()</span></code> format codes, ‘k’ returns an unsigned C long int that receives the lower <code class="docutils literal notranslate"><span class="pre">LONG_BIT</span></code> bits of the Python argument, truncating without range checking. ‘K’ returns an unsigned C long long int that receives the lower <code class="docutils literal notranslate"><span class="pre">LONG_LONG_BIT</span></code> bits, truncating without range checking. (SF 595026; Thomas Heller did this work.)</li> <li>A new version of IDLE was imported from the IDLEfork project (<a class="reference external" href="http://idlefork.sf.net">http://idlefork.sf.net</a>). The code now lives in the <code class="docutils literal notranslate"><span class="pre">idlelib</span></code> package in the standard library and the <code class="docutils literal notranslate"><span class="pre">idle</span></code> script is installed by <code class="docutils literal notranslate"><span class="pre">setup.py</span></code>.</li> </ul> </section> <section id="planned-features-for-2-3"> <h2><a class="toc-backref" href="#planned-features-for-2-3" role="doc-backlink">Planned features for 2.3</a></h2> <p>Too late for anything more to get done here.</p> </section> <section id="ongoing-tasks"> <h2><a class="toc-backref" href="#ongoing-tasks" role="doc-backlink">Ongoing tasks</a></h2> <p>The following are ongoing TO-DO items which we should attempt to work on without hoping for completion by any particular date.</p> <ul class="simple"> <li>Documentation: complete the distribution and installation manuals.</li> <li>Documentation: complete the documentation for new-style classes.</li> <li>Look over the <code class="docutils literal notranslate"><span class="pre">Demos/</span></code> directory and update where required (Andrew Kuchling has done a lot of this)</li> <li>New tests.</li> <li>Fix doc bugs on SF.</li> <li>Remove use of deprecated features in the core.</li> <li>Document deprecated features appropriately.</li> <li>Mark deprecated C APIs with <code class="docutils literal notranslate"><span class="pre">Py_DEPRECATED</span></code>.</li> <li>Deprecate modules which are unmaintained, or perhaps make a new category for modules ‘Unmaintained’</li> <li>In general, lots of cleanup so it is easier to move forward.</li> </ul> </section> <section id="open-issues"> <h2><a class="toc-backref" href="#open-issues" role="doc-backlink">Open issues</a></h2> <p>There are some issues that may need more work and/or thought before the final release (and preferably before the first beta release): No issues remaining.</p> </section> <section id="features-that-did-not-make-it-into-python-2-3"> <h2><a class="toc-backref" href="#features-that-did-not-make-it-into-python-2-3" role="doc-backlink">Features that did not make it into Python 2.3</a></h2> <ul> <li>The import lock could use some redesign. (SF 683658.)</li> <li>Set API issues; is the sets module perfect?<p>I expect it’s good enough to stop polishing it until we’ve had more widespread user experience.</p> </li> <li>A nicer API to open text files, replacing the ugly (in some people’s eyes) “U” mode flag. There’s a proposal out there to have a new built-in type <code class="docutils literal notranslate"><span class="pre">textfile(filename,</span> <span class="pre">mode,</span> <span class="pre">encoding)</span></code>. (Shouldn’t it have a <em>bufsize</em> argument too?)<p>Ditto.</p> </li> <li>New widgets for Tkinter???<p>Has anyone gotten the time for this? <em>Are</em> there any new widgets in Tk 8.4? Note that we’ve got better Tix support already (though not on Windows yet).</p> </li> <li>Fredrik Lundh’s basetime proposal:<p><a class="reference external" href="http://effbot.org/ideas/time-type.htm">http://effbot.org/ideas/time-type.htm</a></p> <p>I believe this is dead now.</p> </li> <li><a class="pep reference internal" href="../pep-0304/" title="PEP 304 – Controlling Generation of Bytecode Files">PEP 304</a> (Controlling Generation of Bytecode Files by Montanaro) seems to have lost steam.</li> <li>For a class defined inside another class, the <code class="docutils literal notranslate"><span class="pre">__name__</span></code> should be <code class="docutils literal notranslate"><span class="pre">"outer.inner"</span></code>, and pickling should work. (SF 633930. I’m no longer certain this is easy or even right.)</li> <li>reST is going to be used a lot in Zope3. Maybe it could become a standard library module? (Since reST’s author thinks it’s too unstable, I’m inclined not to do this.)</li> <li>Decide on a clearer deprecation policy (especially for modules) and act on it. For a start, see this message from Neal Norwitz: <a class="reference external" href="https://mail.python.org/pipermail/python-dev/2002-April/023165.html">https://mail.python.org/pipermail/python-dev/2002-April/023165.html</a> There seems insufficient interest in moving this further in an organized fashion, and it’s not particularly important.</li> <li>Provide alternatives for common uses of the <code class="docutils literal notranslate"><span class="pre">types</span></code> module;<p>Skip Montanaro has posted a proto-PEP for this idea: <a class="reference external" href="https://mail.python.org/pipermail/python-dev/2002-May/024346.html">https://mail.python.org/pipermail/python-dev/2002-May/024346.html</a></p> <p>There hasn’t been any progress on this, AFAICT.</p> </li> <li>Use pending deprecation for the <code class="docutils literal notranslate"><span class="pre">types</span></code> and <code class="docutils literal notranslate"><span class="pre">string</span></code> modules. This requires providing alternatives for the parts that aren’t covered yet (e.g. <code class="docutils literal notranslate"><span class="pre">string.whitespace</span></code> and <code class="docutils literal notranslate"><span class="pre">types.TracebackType</span></code>). It seems we can’t get consensus on this.</li> <li>Deprecate the <code class="docutils literal notranslate"><span class="pre">buffer</span></code> object.<ul class="simple"> <li><a class="reference external" href="https://mail.python.org/pipermail/python-dev/2002-July/026388.html">https://mail.python.org/pipermail/python-dev/2002-July/026388.html</a></li> <li><a class="reference external" href="https://mail.python.org/pipermail/python-dev/2002-July/026408.html">https://mail.python.org/pipermail/python-dev/2002-July/026408.html</a></li> </ul> <p>It seems that this is never going to be resolved.</p> </li> <li><a class="pep reference internal" href="../pep-0269/" title="PEP 269 – Pgen Module for Python">PEP 269</a> Pgen Module for Python, Riehl<p>(Some necessary changes are in; the <code class="docutils literal notranslate"><span class="pre">pgen</span></code> module itself needs to mature more.)</p> </li> <li>Add support for the long-awaited Python catalog. Kapil Thangavelu has a Zope-based implementation that he demoed at OSCON 2002. Now all we need is a place to host it and a person to champion it. (Some changes to distutils to support this are in, at least.)</li> <li><a class="pep reference internal" href="../pep-0266/" title="PEP 266 – Optimizing Global Variable/Attribute Access">PEP 266</a> Optimizing Global Variable/Attribute Access, Montanaro<p><a class="pep reference internal" href="../pep-0267/" title="PEP 267 – Optimized Access to Module Namespaces">PEP 267</a> Optimized Access to Module Namespaces, Hylton</p> <p><a class="pep reference internal" href="../pep-0280/" title="PEP 280 – Optimizing access to globals">PEP 280</a> Optimizing access to globals, van Rossum</p> <p>These are basically three friendly competing proposals. Jeremy has made a little progress with a new compiler, but it’s going slow and the compiler is only the first step. Maybe we’ll be able to refactor the compiler in this release. I’m tempted to say we won’t hold our breath. In the meantime, Oren Tirosh has a much simpler idea that may give a serious boost to the performance of accessing globals and built-ins, by optimizing and inlining the dict access: <a class="reference external" href="http://tothink.com/python/fastnames/">http://tothink.com/python/fastnames/</a></p> </li> <li>Lazily tracking tuples?<ul class="simple"> <li><a class="reference external" href="https://mail.python.org/pipermail/python-dev/2002-May/023926.html">https://mail.python.org/pipermail/python-dev/2002-May/023926.html</a></li> <li><a class="reference external" href="https://bugs.python.org/issue558745">https://bugs.python.org/issue558745</a></li> </ul> <p>Not much enthusiasm I believe.</p> </li> <li><a class="pep reference internal" href="../pep-0286/" title="PEP 286 – Enhanced Argument Tuples">PEP 286</a> Enhanced Argument Tuples, von Loewis<p>I haven’t had the time to review this thoroughly. It seems a deep optimization hack (also makes better correctness guarantees though).</p> </li> <li>Make ‘as’ a keyword. It has been a pseudo-keyword long enough. Too much effort to bother.</li> </ul> </section> <section id="copyright"> <h2><a class="toc-backref" href="#copyright" role="doc-backlink">Copyright</a></h2> <p>This document has been placed in the public domain.</p> </section> </section> <hr class="docutils" /> <p>Source: <a class="reference external" href="https://github.com/python/peps/blob/main/peps/pep-0283.rst">https://github.com/python/peps/blob/main/peps/pep-0283.rst</a></p> <p>Last modified: <a class="reference external" href="https://github.com/python/peps/commits/main/peps/pep-0283.rst">2025-02-01 08:59:27 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-manager">Release Manager</a></li> <li><a class="reference internal" href="#completed-features-for-2-3">Completed features for 2.3</a></li> <li><a class="reference internal" href="#planned-features-for-2-3">Planned features for 2.3</a></li> <li><a class="reference internal" href="#ongoing-tasks">Ongoing tasks</a></li> <li><a class="reference internal" href="#open-issues">Open issues</a></li> <li><a class="reference internal" href="#features-that-did-not-make-it-into-python-2-3">Features that did not make it into Python 2.3</a></li> <li><a class="reference internal" href="#copyright">Copyright</a></li> </ul> <br> <a id="source" href="https://github.com/python/peps/blob/main/peps/pep-0283.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>