Update of /cvsroot/python/python/dist/src
In directory usw-pr-cvs1:/tmp/cvs-serv3578
Modified Files:
README
Log Message:
Updates related to Modules/Setup and setup.py. This addresses SF bug
#512871 (Jon Ribbens): Installation instructions are wrong.
Bugfix candidate.
Index: README
===================================================================
RCS file: /cvsroot/python/python/dist/src/README,v
retrieving revision 1.138
retrieving revision 1.139
diff -C2 -d -r1.138 -r1.139
*** README 4 Feb 2002 01:59:23 -0000 1.138
--- README 8 Feb 2002 22:22:35 -0000 1.139
***************
*** 46,50 ****
and then "make install".
! The section `Build Instructions' below is still recommended reading,
especially the part on customizing Modules/Setup.
--- 46,50 ----
and then "make install".
! The section `Build instructions' below is still recommended reading,
especially the part on customizing Modules/Setup.
***************
*** 152,181 ****
==================
! Before you can build Python, you must first configure it. Fortunately,
! the configuration and build process has been streamlined for most Unix
! installations, so all you have to do is type a few commands,
! optionally edit one file, and sit back. There are some platforms
! where things are not quite as smooth; see the platform specific notes
! below. If you want to build for multiple platforms sharing the same
! source tree, see the section on VPATH below.
! Start by running the script "./configure", which determines your system
! configuration and creates the Makefile. (It takes a minute or two --
! please be patient!) You may want to pass options to the configure
! script or edit the Modules/Setup file after running configure -- see the
! section below on configuration options and variables. When it's done,
! you are ready to run make.
! To build Python, you normally type "make" in the toplevel directory. If
! you have changed the configuration or have modified Modules/Setup, the
! Makefile may have to be rebuilt. In this case you may have to run make
! again to correctly build your desired target. The interpreter
! executable is built in the top level directory.
Once you have built a Python interpreter, see the subsections below on
! testing, configuring additional modules, and installation. If you run
! into trouble, see the next section. Editing the Modules/Setup file
! after running make is supported; just run "make" again after making
! the desired changes.
--- 152,185 ----
==================
! Before you can build Python, you must first configure it.
! Fortunately, the configuration and build process has been automated
! for Unix and Linux installations, so all you usually have to do is
! type a few commands and sit back. There are some platforms where
! things are not quite as smooth; see the platform specific notes below.
! If you want to build for multiple platforms sharing the same source
! tree, see the section on VPATH below.
! Start by running the script "./configure", which determines your
! system configuration and creates the Makefile. (It takes a minute or
! two -- please be patient!) You may want to pass options to the
! configure script -- see the section below on configuration options and
! variables. When it's done, you are ready to run make.
! To build Python, you normally type "make" in the toplevel directory.
! If you have changed the configuration, the Makefile may have to be
! rebuilt. In this case you may have to run make again to correctly
! build your desired target. The interpreter executable is built in the
! top level directory.
Once you have built a Python interpreter, see the subsections below on
! testing and installation. If you run into trouble, see the next
! section.
!
! Previous versions of Python used a manual configuration process that
! involved editing the file Modules/Setup. While this file still exists
! and manual configuration is still supported, it is rarely needed any
! more: almost all modules are automatically built as appropriate under
! guidance of the setup.py script, which is run by Make after the
! interpreter has been built.
***************
*** 229,232 ****
--- 233,237 ----
64-bit platforms: The modules audioop, imageop and rgbimg don't work.
+ The setup.py script disables them on 64-bit installations.
Don't try to enable them in the Modules/Setup file. They
contain code that is quite wordsize sensitive. (If you have a
***************
*** 245,251 ****
Under Linux systems using GNU libc 2 (aka libc6), the crypt
! module now needs the -lcrypt option. Uncomment this flag in
! Modules/Setup, or comment out the crypt module in the same
! file. Most modern Linux systems use glibc2.
Red Hat Linux: There's an executable /usr/bin/python which is Python
--- 250,255 ----
Under Linux systems using GNU libc 2 (aka libc6), the crypt
! module now needs the -lcrypt option. The setup.py script
! takes care of this automatically.
Red Hat Linux: There's an executable /usr/bin/python which is Python
***************
*** 561,565 ****
distribution attempts to detect which modules can be built and
automatically compiles them. Autodetection doesn't always work, so
! you can customize the configuration by editing the Modules/Setup file.
This file is initially copied from Setup.dist by the configure script;
if it does not exist yet, create it by copying Modules/Setup.dist
--- 565,574 ----
distribution attempts to detect which modules can be built and
automatically compiles them. Autodetection doesn't always work, so
! you can still customize the configuration by editing the Modules/Setup
! file; but this should be considered a last resort. The rest of this
! section only applies if you decide to edit the Modules/Setup file.
! You also need this to enable static linking of certain modules (which
! is needed to enable profiling on some systems).
!
This file is initially copied from Setup.dist by the configure script;
if it does not exist yet, create it by copying Modules/Setup.dist
***************
*** 629,634 ****
the compiled files left by the previous test run). The test set
produces some output. You can generally ignore the messages about
! skipped tests due to optional features which can't be imported. (If
! you want to test those modules, edit Modules/Setup to configure them.)
If a message is printed about a failed test or a traceback or core
dump is produced, something is wrong. On some Linux systems (those
--- 638,642 ----
the compiled files left by the previous test run). The test set
produces some output. You can generally ignore the messages about
! skipped tests due to optional features which can't be imported.
If a message is printed about a failed test or a traceback or core
dump is produced, something is wrong. On some Linux systems (those
***************
*** 733,738 ****
about the install prefix.
! --with-readline: This option is no longer supported. To use GNU
! readline, enable module "readline" in the Modules/Setup file.
--with-threads: On most Unix systems, you can now use multiple
--- 741,746 ----
about the install prefix.
! --with-readline: This option is no longer supported. GNU
! readline is automatically enabled by setup.py when present.
--with-threads: On most Unix systems, you can now use multiple
***************
*** 889,912 ****
! The Tk interface
! ----------------
! Tk (the user interface component of John Ousterhout's Tcl language) is
! also usable from Python. Since this requires that you first build and
! install Tcl/Tk, the Tk interface is not enabled by default when
! building Python from source. Python supports Tcl/Tk version 8.0 and
higher.
- See http://dev.ajubasolutions.com/ for more info on Tcl/Tk, including
- the on-line manual pages.
-
-
- To enable the Python/Tk interface, once you've built and installed
- Tcl/Tk, load the file Modules/Setup into your favorite text editor and
- search for the string "_tkinter". Then follow the instructions found
- there. If you have installed Tcl/Tk or X11 in unusual places, you
- will have to edit the first line to fix or add the -I and -L options.
- (Also see the general instructions at the top of that file.)
-
For more Tkinter information, see the Tkinter Resource page:
http://www.python.org/topics/tkinter/
--- 897,907 ----
! Tkinter
! -------
! The setup.py script automatically configures this when it detects a
! usable Tcl/Tk installation. This requires Tcl/Tk version 8.0 or
higher.
For more Tkinter information, see the Tkinter Resource page:
http://www.python.org/topics/tkinter/
***************
*** 920,932 ****
(lower case t and leading underscore) which lives in
Modules/_tkinter.c. Demos and normal Tk applications import only the
! Python Tkinter module -- the latter uses the C _tkinter module
! directly. In order to find the C _tkinter module, it must be compiled
! and linked into the Python interpreter -- the _tkinter line in the
! Setup file does this. In order to find the Python Tkinter module,
! sys.path must be set correctly -- the TKPATH assignment in the Setup
! file takes care of this, but only if you install Python properly
! ("make install libinstall"). (You can also use dynamic loading for
! the C _tkinter module, in which case you must manually fix up sys.path
! or set $PYTHONPATH for the Python Tkinter module.)
--- 915,923 ----
(lower case t and leading underscore) which lives in
Modules/_tkinter.c. Demos and normal Tk applications import only the
! Python Tkinter module -- only the latter imports the C _tkinter
! module. In order to find the C _tkinter module, it must be compiled
! and linked into the Python interpreter -- the setup.py script does
! this. In order to find the Python Tkinter module, sys.path must be
! set correctly -- normal installation takes care of this.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4