Skip to content

reSTify 10 PEPs #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 7, 2017
Merged

reSTify 10 PEPs #174

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
82 changes: 44 additions & 38 deletions pep-0160.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,73 +5,79 @@ Last-Modified: $Date$
Author: Fred L. Drake, Jr. <fdrake@acm.org>
Status: Final
Type: Informational
Content-Type: text/x-rst
Created: 25-Jul-2000
Python-Version: 1.6
Post-History:


Introduction
============

This PEP describes the Python 1.6 release schedule. 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).
This release will be produced by BeOpen PythonLabs staff for the
Corporation for National Research Initiatives (CNRI).


Schedule
========

August 1 1.6 beta 1 release (planned).
August 3 1.6 beta 1 release (actual).
August 15 1.6 final release (planned).
September 5 1.6 final release (actual).
* August 1: 1.6 beta 1 release (planned).
* August 3: 1.6 beta 1 release (actual).
* August 15: 1.6 final release (planned).
* September 5: 1.6 final release (actual).


Features
========

A number of features are required for Python 1.6 in order to
fulfill the various promises that have been made. The following
are required to be fully operational, documented, and forward
compatible with the plans for Python 2.0:
A number of features are required for Python 1.6 in order to
fulfill the various promises that have been made. The following
are required to be fully operational, documented, and forward
compatible with the plans for Python 2.0:

* Unicode support: The Unicode object defined for Python 2.0 must
be provided, including all methods and codec support.
* 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.
It must pass the regression test used for the pcre-based version
of the re module.
* 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.

* The curses module was in the middle of a transformation to a
package, so the final form was adopted.
* The curses module was in the middle of a transformation to a package, so the
final form was adopted.


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

The branch tag is "cnri-16-start".
The branch tag is "cnri-16-start".

Patches and features will be merged to the extent required to pass
regression tests in effect on 16 May 2000.
Patches and features will be merged to the extent required to pass
regression tests in effect on 16 May 2000.

The beta release is tagged "r16b1" in the CVS repository, and the
final Python 1.6 release is tagged "release16" in the repository.
The beta release is tagged "r16b1" in the CVS repository, and the
final Python 1.6 release is tagged "release16" in the repository.


Copyright
=========

This document has been placed in the public domain.
This document has been placed in the public domain.



Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:

..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:
12 changes: 7 additions & 5 deletions pep-0210.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,15 @@ Last-Modified: $Date$
Author: davida@activestate.com (David Ascher)
Status: Rejected
Type: Standards Track
Content-Type: text/x-rst
Created: 15-Jul-2000
Python-Version: 2.1
Post-History:



Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:

..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:
63 changes: 36 additions & 27 deletions pep-0217.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,38 +5,44 @@ Last-Modified: $Date$
Author: moshez@zadka.site.co.il (Moshe Zadka)
Status: Final
Type: Standards Track
Content-Type: text/x-rst
Created: 31-Jul-2000
Python-Version: 2.1
Post-History:
Post-History:


Abstract
========

Python's interactive mode is one of the implementation's great
strengths -- being able to write expressions on the command line
and get back a meaningful output. However, the output function
cannot be all things to all people, and the current output
function too often falls short of this goal. This PEP describes a
way to provides alternatives to the built-in display function in
Python, so users will have control over the output from the
interactive interpreter.

Python's interactive mode is one of the implementation's great
strengths -- being able to write expressions on the command line
and get back a meaningful output. However, the output function
cannot be all things to all people, and the current output
function too often falls short of this goal. This PEP describes a
way to provides alternatives to the built-in display function in
Python, so users will have control over the output from the
interactive interpreter.

Interface
=========

The current Python solution has worked for many users, and this
should not break it. Therefore, in the default configuration,
nothing will change in the REPL loop. To change the way the
interpreter prints interactively entered expressions, users
will have to rebind ``sys.displayhook`` to a callable object.
The result of calling this object with the result of the
interactively entered expression should be print-able,
and this is what will be printed on ``sys.stdout``.

The current Python solution has worked for many users, and this
should not break it. Therefore, in the default configuration,
nothing will change in the REPL loop. To change the way the
interpreter prints interactively entered expressions, users
will have to rebind sys.displayhook to a callable object.
The result of calling this object with the result of the
interactively entered expression should be print-able,
and this is what will be printed on sys.stdout.

Solution
========

The bytecode PRINT_EXPR will call sys.displayhook(POP())
A displayhook() will be added to the sys builtin module, which is
equivalent to
The bytecode ``PRINT_EXPR`` will call ``sys.displayhook(POP())``.
A ``displayhook()`` will be added to the sys builtin module, which is
equivalent to::

import __builtin__
def displayhook(o):
Expand All @@ -45,13 +51,16 @@ Solution
__builtin__._ = None
print `o`
__builtin__._ = o



Jython Issues
=============

The method ``Py.printResult`` will be similarly changed.

The method Py.printResult will be similarly changed.

Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:
..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:
27 changes: 15 additions & 12 deletions pep-0220.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,23 +5,26 @@ Last-Modified: $Date$
Author: gmcm@hypernet.com (Gordon McMillan)
Status: Rejected
Type: Informational
Content-Type: text/x-rst
Created: 14-Aug-2000
Post-History:


Abstract
========

Demonstrates why the changes described in the stackless PEP are
desirable. A low-level continuations module exists. With it,
coroutines and generators and "green" threads can be written. A
higher level module that makes coroutines and generators easy to
create is desirable (and being worked on). The focus of this PEP
is on showing how coroutines, generators, and green threads can
simplify common programming problems.
Demonstrates why the changes described in the stackless PEP are
desirable. A low-level continuations module exists. With it,
coroutines and generators and "green" threads can be written. A
higher level module that makes coroutines and generators easy to
create is desirable (and being worked on). The focus of this PEP
is on showing how coroutines, generators, and green threads can
simplify common programming problems.



Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:

..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End:
Loading