iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

More explanation of feature requirements and mechanics of construction.

This commit is contained in:
Fred Drake 2000-07-25 20:48:58 +00:00
parent 86fcb76ff6
commit 1ffce41fee
1 changed files with 29 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
pep-0160.txt
View File

@ -1,19 +1,19 @@
PEP: 160 PEP: 160
Title: Python 1.6 Release Schedule Title: Python 1.6 Release Schedule
Version: $Revision$ Version: $Revision$
Owner: fdrake@beopen.com (Fred L. Drake, Jr.) Owner: Fred L. Drake, Jr. <fdrake@beopen.com>
Python-Version: 2.0 Python-Version: 1.6
Status: Incomplete Status: Incomplete
Introduction Introduction
This PEP describes the Python 1.6 release schedule, tracking the This PEP describes the Python 1.6 release schedule. The CVS
status and ownership of the major new features, summarizes revision history of this file contains the definitive historical
discussions held in mailing list forums, and provides URLs for record.
further information, patches, and other outstanding issues. The
CVS revision history of this file contains the definitive This release will be produced by BeOpen PythonLabs staff for the
historical record. Corporation for National Research Initiatives (CNRI).
Schedule Schedule
@ -31,13 +31,29 @@ Features
* Unicode support: The Unicode object defined for Python 2.0 must * Unicode support: The Unicode object defined for Python 2.0 must
be provided, including all methods and codec support. be provided, including all methods and codec support.
* SRE: Fredrik Lundh's new regular expression engine will be used
to provide support for both 8-bit strings and Unicode strings.
It must pass the regression test used for the pcre-based version
of the re module.
Mechanism
The release will be created as a branch from the development tree
rooted at CNRI's close of business on 16 May 2000. Patches
required from more recent checkins will be merged in by moving the
branch tag on individual files whenever possible in order to
reduce mailing list clutter and avoid divergent and incompatible
implementations.
Patches and features will be merged to the extent required to pass
regression tests in effect on 16 May 2000.
Copyright Copyright
This document has been placed in the public domain. This document has been placed in the public domain.
Local Variables: Local Variables:
mode: indented-text mode: indented-text