Rewrote sections on GNU readline (now that I'm using 2.0), ftp, and
mailing list / newsgroup.
This commit is contained in:
parent
9bb4fd6061
commit
03d8f745e6
83
README
83
README
@ -142,24 +142,37 @@ exec_prefix=DIRECTORY) overrides the prefix set at configuration time;
|
|||||||
this may be more convenient than re-running the configure script if
|
this may be more convenient than re-running the configure script if
|
||||||
you change your mind about the install prefix...
|
you change your mind about the install prefix...
|
||||||
|
|
||||||
- You can use the GNU readline library to improve the interactive
|
- You can use the GNU readline library to improve the interactive user
|
||||||
user interface: this gives you line editing and command history when
|
interface: this gives you line editing and command history when
|
||||||
calling python interactively. You need to build the GNU readline
|
calling python interactively. You need to configure build the GNU
|
||||||
library before running the configure script. Its sources are
|
readline library before running the configure script. Its sources are
|
||||||
distributed with Python. This may involve some editing of the
|
no longer distributed with Python; you can ftp them from any GNU
|
||||||
Makefile there -- I'm sorry, but I don't feel responsible for making
|
mirror site, or from its home site:
|
||||||
it more portable or adapting it to autoconf... Pass the configure
|
ftp://slc2.ins.cwru.edu/pub/dist/readline-2.0.tar.gz (or a higher
|
||||||
script the option --with-readline=DIRECTORY where DIRECTORY is the
|
version number -- using version 1.x is not recommended). Pass the
|
||||||
absolute pathname of the directory where you've built the readline
|
Python configure script the option --with-readline=DIRECTORY where
|
||||||
library. A known problem with the readline library is that it
|
DIRECTORY is the absolute pathname of the directory where you've built
|
||||||
contains entry points which cause conflicts with the STDWIN and SGI GL
|
the readline library. Some hints on building and using the readline
|
||||||
libraries. The stdwin conflict can be solved (and will be, in some
|
library:
|
||||||
future release of stdwin) by adding a line saying '#define werase
|
|
||||||
w_erase' to the stdwin.h file (in the stdwin distribution,
|
- On SGI IRIX 5, you may have to add the following
|
||||||
subdirectory H). The GL conflict may be solvable by reordering the -l
|
to rldefs.h:
|
||||||
options on the final link command, but it appears unsafe... Another
|
|
||||||
hint: you may have to add -Dindex=strchr -Drindex=strrchr to
|
#ifndef sigmask
|
||||||
readline's CFLAGS if your system doesn't have index and rindex.
|
#define sigmask(sig) (1L << ((sig)-1))
|
||||||
|
#endif
|
||||||
|
|
||||||
|
- The readline library requires use of the termcap library. A
|
||||||
|
known problem with this is that it contains entry points which
|
||||||
|
cause conflicts with the STDWIN and SGI GL libraries. The stdwin
|
||||||
|
conflict can be solved (and will be, in the next release of
|
||||||
|
stdwin) by adding a line saying '#define werase w_erase' to the
|
||||||
|
stdwin.h file (in the stdwin distribution, subdirectory H). The
|
||||||
|
GL conflict has been solved in the Python configure script by a
|
||||||
|
hack that forces use of the static version of the termcap library.
|
||||||
|
|
||||||
|
- Check the newsgroup gnu.bash.bugs for specific problems with the
|
||||||
|
readline library.
|
||||||
|
|
||||||
- On SGI IRIX, and on Sun SOLARIS 2, you can use multiple threads. To
|
- On SGI IRIX, and on Sun SOLARIS 2, you can use multiple threads. To
|
||||||
enable this, pass --with-thread. In the Modules/Setup file, enable
|
enable this, pass --with-thread. In the Modules/Setup file, enable
|
||||||
@ -339,30 +352,22 @@ readline/ Source code for the GNU readline library
|
|||||||
Ftp access
|
Ftp access
|
||||||
----------
|
----------
|
||||||
|
|
||||||
The latest Python source distribution can be ftp'ed from site
|
The latest Python source distribution can be ftp'ed from
|
||||||
ftp.cwi.nl, directory /pub/python, file python<version>.tar.Z. You
|
ftp://ftp.cwi.nl/pub/python/python<version>.tar.gz. You can also find
|
||||||
can also find PostScript of the main Python documentation there,
|
PostScript of the main Python documentation there, Macintosh and PC
|
||||||
Macintosh and PC binaries, and the latest STDWIN source distribution
|
binaries, and the latest STDWIN source distribution (in directory
|
||||||
(in directory /pub/stdwin). Mirror sites are gatekeeper.dec.com
|
/pub/stdwin). oFr mirror sites, see the list in the FAQ (Misc/FAQ
|
||||||
(/pub/plan/python/cwi), ftp.wustl.edu
|
this directory).
|
||||||
(/graphics/graphics/sgi-stuff/python) and ftp.uu.net
|
|
||||||
(/languages/python) -- try these sites first if you are on the US
|
|
||||||
continent, or at least closer to it than to Europe. These mirror
|
|
||||||
sites are at most a day behind on the European archive!
|
|
||||||
|
|
||||||
If you don't have ftp access, send mail containing only the word HELP
|
|
||||||
to ftpmail@decwrl.dec.com or bitftp@pucc.princeton.edu, and the
|
|
||||||
server will send you instructions on how to make requests.
|
|
||||||
|
|
||||||
|
|
||||||
Mailing list
|
Mailing list and Newsgroup
|
||||||
------------
|
--------------------------
|
||||||
|
|
||||||
There is a mailing list devoted to Python programming, design and
|
There are a mailing list and a newsgroup devoted to Python
|
||||||
bugs. To subscribe, send mail containing your real name and e-mail
|
programming, design and bugs. The newsgroup, comp.lang.python,
|
||||||
address in Internet form to "python-list-request@cwi.nl". If you have
|
contains exactly the same messages as the mailing list. To subscribe
|
||||||
built and installed Python, you are urgently to subscribe to this
|
to the mailing list, send mail containing your real name and e-mail
|
||||||
mailing list.
|
address in Internet form to "python-list-request@cwi.nl".
|
||||||
|
|
||||||
|
|
||||||
Author
|
Author
|
||||||
|
Loading…
x
Reference in New Issue
Block a user