forked from gvanrossum/peps
-
Notifications
You must be signed in to change notification settings - Fork 0
/
pep-0217.txt
66 lines (51 loc) · 1.7 KB
/
pep-0217.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
PEP: 217
Title: Display Hook for Interactive Use
Version: $Revision$
Last-Modified: $Date$
Author: [email protected] (Moshe Zadka)
Status: Final
Type: Standards Track
Content-Type: text/x-rst
Created: 31-Jul-2000
Python-Version: 2.1
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.
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``.
Solution
========
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):
if o is None:
return
__builtin__._ = None
print `o`
__builtin__._ = o
Jython Issues
=============
The method ``Py.printResult`` will be similarly changed.
..
Local Variables:
mode: indented-text
indent-tabs-mode: nil
End: