|
6 | 6 |
|
7 | 7 | idle_name = "idle" |
8 | 8 |
|
9 | | -# IDLE not being imported as a package by its script. It is now being |
10 | | -# installed as a collection of modules in a directory in .../site-packages/, |
11 | | -# with a .pth file which will add IDLE to sys.path |
12 | | - |
13 | 9 | # Name of 'package' to be installed in site-packages: |
14 | 10 | pkgname = idle_name + "lib" |
15 | 11 |
|
|
28 | 24 | raise SystemExit |
29 | 25 |
|
30 | 26 | # the normal build_py would not incorporate anything but .py files |
31 | | -txt_files = ['extend.txt', 'help.txt', 'CREDITS.txt', 'LICENSE.txt', |
32 | | - 'README.txt'] |
| 27 | +txt_files = ['extend.txt', 'help.txt', 'CREDITS.txt', 'HISTORY.txt', |
| 28 | + 'INSTALL.txt', 'LICENSE.txt', 'NEWS.txt', 'README.txt'] |
33 | 29 | txt_files += ['config-extensions.def', 'config-highlight.def', |
34 | 30 | 'config-keys.def', 'config-main.def'] |
35 | 31 | txt_files += [idle_name + '.bat', idle_name + '.pyw'] |
@@ -101,7 +97,7 @@ def _bytecode_filenames(self, files): |
101 | 97 | things, as well as a Python shell window and a debugger. |
102 | 98 |
|
103 | 99 | IDLEfork is a separate line of development which was initiated by |
104 | | -D. Scherer at CMU as part of Visual Python. It features execution in a |
| 100 | +David Scherer at CMU as part of VPython. It features execution in a |
105 | 101 | separate process which is newly initiated for each run. At version 0.9 |
106 | 102 | the RPC was changed to incorporate code by GvR, which supports the |
107 | 103 | debugger. IDLEfork also incorporates a GUI configuration utilility. |
|
0 commit comments