peps: ee26025e67f9 (original) (raw)

Mercurial > peps

changeset 46:ee26025e67f9

More explanation of feature requirements and mechanics of construction.

Fred Drake fdrake@acm.org
date	Tue, 25 Jul 2000 20:48:58 +0000
parents	be7150dbe20c
children	0be37909cd50
files	pep-0160.txt
diffstat	1 files changed, 29 insertions(+), 13 deletions(-)[+] [-] pep-0160.txt 42

line wrap: on

line diff

--- a/pep-0160.txt +++ b/pep-0160.txt @@ -1,19 +1,19 @@ -PEP: 160 -Title: Python 1.6 Release Schedule -Version: RevisionRevisionRevision -Owner: fdrake@beopen.com (Fred L. Drake, Jr.) -Python-Version: 2.0 -Status: Incomplete +PEP: 160 +Title: Python 1.6 Release Schedule +Version: RevisionRevisionRevision +Owner: Fred L. Drake, Jr. fdrake@beopen.com +Python-Version: 1.6 +Status: Incomplete Introduction

This PEP describes the Python 1.6 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.

This PEP describes the Python 1.6 release schedule. The CVS
revision history of this file contains the definitive historical
record.

This release will be produced by BeOpen PythonLabs staff for the
Corporation for National Research Initiatives (CNRI).

Schedule @@ -31,13 +31,29 @@ Features * Unicode support: The Unicode object defined for Python 2.0 must 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.[](#l1.40)

 It must pass the regression test used for the pcre-based version[](#l1.41)

```
 of the re module.[](#l1.42)
```

+ + +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.