[Python-checkins] CVS: distutils README.txt,1.16,1.17 CHANGES.txt,1.10,1.11
Greg Ward
python-dev@python.org
Thu, 29 Jun 2000 19:54:02 -0700
Update of /cvsroot/python/distutils
In directory slayer.i.sourceforge.net:/tmp/cvs-serv10850
Modified Files:
README.txt CHANGES.txt
Log Message:
Update for Distutils 0.9.
Index: README.txt
===================================================================
RCS file: /cvsroot/python/distutils/README.txt,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -r1.16 -r1.17
*** README.txt 2000/06/04 13:46:19 1.16
--- README.txt 2000/06/30 02:54:00 1.17
***************
*** 1,5 ****
Python Distribution Utilities
! release 0.9 (pre)
! June ??, 2000
--- 1,5 ----
Python Distribution Utilities
! release 0.9
! June 29, 2000
***************
*** 11,20 ****
installation of Python modules. (It is intended that ultimately the
Distutils will grow up into a system for distributing and installing
! whole Python applications, but for now their scope is limited to module
distributions.)
! The Distutils are a standard part of Python 1.6; if you are running 1.6,
! you don't need to install the Distutils separately. This release is
! primarily so that you can add the Distutils to a Python 1.5.2
installation -- you will then be able to install modules that require
the Distutils, or use the Distutils to distribute your own modules.
--- 11,20 ----
installation of Python modules. (It is intended that ultimately the
Distutils will grow up into a system for distributing and installing
! whole Python applications, but for now their scope is primarily module
distributions.)
! The Distutils are a standard part of Python 1.6/2.0; if you are running
! 1.6/2.0, you don't need to install the Distutils separately. This
! release is primarily so that you can add the Distutils to a Python 1.5.2
installation -- you will then be able to install modules that require
the Distutils, or use the Distutils to distribute your own modules.
***************
*** 43,50 ****
Release 0.9 of the Distutils requires Python 1.5.2 or later. (If you
! absolutely must Python 1.5.1, Distutils 0.1.5 is backwards compatible.
! However, I have dropped plans to port the current Distutils code back to
! Python 1.5.1, as I have received exactly zero complaints about requiring
! Python 1.5.2 since releasing Distutils 0.8 in April.)
To use the Distutils under Unix, you must have a *complete* Python
--- 43,50 ----
Release 0.9 of the Distutils requires Python 1.5.2 or later. (If you
! absolutely must use Python 1.5.1, Distutils 0.1.5 is backwards
! compatible. However, I have dropped plans to port the current Distutils
! code back to Python 1.5.1, as I have received exactly zero complaints
! about requiring Python 1.5.2 since releasing Distutils 0.8 in April.)
To use the Distutils under Unix, you must have a *complete* Python
***************
*** 71,81 ****
extensions works or not.
! To build extensions on Windows, you need Microsoft Visual C++ 5.0 or
! 6.0. It also helps to have access to the Windows registry from Python;
! if you have the Win32 extensions (win32api, win32con) installed, you're
! fine. (Python 1.6 includes the winreg module for this purpose, which
! the Distutils will use if available.) If not, the Distutils might not
! be able to find the Visual C++ executables, in which case it will die
! horribly when you attempt to build any Python extensions.
--- 71,85 ----
extensions works or not.
! Building extensions on Windows works best with Microsoft Visual C++ 5.0
! or 6.0. It also helps to have access to the Windows registry from
! Python; if you have the Win32 extensions (win32api, win32con) installed,
! you're fine. (Python 2.0 includes the winreg module for this purpose,
! which the Distutils will use if available.) If not, the Distutils might
! not be able to find the Visual C++ executables, in which case it will
! die horribly when you attempt to build any Python extensions.
!
! There is also experimental support for building extensions under Windows
! using Borland C++ or GCC (Cygwin or Mingw32 ports). Come join the
! Distutils SIG to learn about using these compilers.
***************
*** 104,115 ****
! INSTALLATION UNDER PYTHON 1.6
! -------------------------------
! The Distutils are included with Python 1.6, so there's generally no need
! to install it under Python 1.6. However, this release is more recent
! than the code included with Python 1.6a2, so if you really like life on
the bleeding edge, you might want to install this Distutils release into
! your Python 1.6a2 library.
To do this, you'll need to hide the original Distutils package directory
--- 108,121 ----
! INSTALLATION UNDER PYTHON 1.6/2.0
! ---------------------------------
! The Distutils have been included with Python since 1.6a1, and Distutils
! 0.9 is approximately the code that will be included with Python 2.0b1
! (modulo bug fixes). Thus, there's generally no need to install the
! Distutils under Python 1.6/2.0. However, Distutils releases may
! occasionally get ahead of Python releases, so if you really like life on
the bleeding edge, you might want to install this Distutils release into
! your Python 1.6/2.0 library.
To do this, you'll need to hide the original Distutils package directory
***************
*** 119,127 ****
follows:
! cd /usr/local/lib/python1.6
mv distutils distutils-orig
On Windows, the stock Distutils installation is "Lib\distutils" under
! the Python directory ("C:\Python" by default for Python 1.6a2 and
later). Again, you should just rename this directory, eg. to
"distutils-orig", so that Python won't find it.
--- 125,133 ----
follows:
! cd /usr/local/lib/python1.6 # or 2.0
mv distutils distutils-orig
On Windows, the stock Distutils installation is "Lib\distutils" under
! the Python directory ("C:\Python" by default with Python 1.6a2 and
later). Again, you should just rename this directory, eg. to
"distutils-orig", so that Python won't find it.
***************
*** 138,143 ****
seriously caters to all three communities: developers can use it to
build and install their modules, as well as create source distributions;
! packagers can use it to create RPMs and (soon!) executable installers
! for Windows; and of course installers can build and install modules from
source (or just use an installer created by some kind packager).
--- 144,149 ----
seriously caters to all three communities: developers can use it to
build and install their modules, as well as create source distributions;
! packagers can use it to create RPMs and executable installers for
! Windows; and of course installers can build and install modules from
source (or just use an installer created by some kind packager).
***************
*** 148,154 ****
way around LaTeX, the Python documentation tools, and Unix, you might be
able to get something out of these. Realistically, though, the
! documentation is just provided in the distributio so you can send me doc
! patches; if you want to read it, you're better off getting the latest
! documentation from the Distutils documentation page:
http://www.python.org/sigs/distutils-sig/doc/
--- 154,160 ----
way around LaTeX, the Python documentation tools, and Unix, you might be
able to get something out of these. Realistically, though, the
! documentation is just provided in the distribution so you can send me
! doc patches; if you want to read it, you're better off getting the
! latest documentation from the Distutils documentation page:
http://www.python.org/sigs/distutils-sig/doc/
***************
*** 171,190 ****
------------------------------
! There are a couple of small incompatibilities between Distutils 0.1.x
! and 0.8.x that affect setup scripts. Unfortunately, two of the major
! module distributions currently using the Distutils -- Numerical Python and
! PyXML -- stumble across these incompatibilities. If you need to build
! and install either of these (or, in theory, any module distribution that
! used Distutils 0.1.x -- although most will not be affected), you have
! two options:
* stick with Distutils 0.1.x (to be avoided, especially if you are
! running Python 1.6)
* replace the setup script provided by the module distribution with
! the Distutils 0.8-compatibile version provided here (recommended)
! For example, if you want to build Numerical Python 15.2 using
! Distutils 0.8.x, you would:
* rename the setup.py provided with Numerical Python 15.2, eg. to
--- 177,196 ----
------------------------------
! There were a couple of small incompatibilities introduced with Distutils
! 0.8 (the previous major release) that affected setup scripts.
! Unfortunately, two of the major module distributions currently using the
! Distutils -- Numerical Python and PyXML -- stumble across these
! incompatibilities. If you need to build and install either of these
! (or, in theory, any module distribution that used Distutils 0.1.x --
! although most will not be affected), you have two options:
* stick with Distutils 0.1.x (to be avoided, especially if you are
! running Python 1.6/2.0)
* replace the setup script provided by the module distribution with
! the Distutils 0.8-compatible version provided here (recommended)
! For example, if you want to build Numerical Python 15.2 using Distutils
! 0.8.x or 0.9, you would:
* rename the setup.py provided with Numerical Python 15.2, eg. to
***************
*** 268,278 ****
there are a few outstanding problems:
- * Distutils 0.8.x doesn't yet work with Python 1.5.1
- * not well tested with Python 1.6
* problems with specifying relative directories in an installation
scheme
- * "bdist_dumb" command untested on Windows
* Mac OS support only partially included
! * no test suite (hmm, is this testing thing a common theme?)
* doesn't check to see if you're clobbering an existing module
installation
--- 274,281 ----
there are a few outstanding problems:
* problems with specifying relative directories in an installation
scheme
* Mac OS support only partially included
! * no test suite
* doesn't check to see if you're clobbering an existing module
installation
***************
*** 280,287 ****
There are some major features that still need to be added:
- * no configuration file mechanism (although it's talked about
- in the documentation)
- * no support for probing the target system for either C- or Python-
- level dependencies
* no knowledge of whether you have installed some module distribution
before
--- 283,286 ----
***************
*** 296,309 ****
http://www.python.org/mailman/listinfo/distutils-sig
FUTURE PLANS
------------
- Distutils 0.9 will include support for configuration files and building
- extensions on Mac OS (definitely with the MPW compiler, possibly with
- CodeWarrior as well).
-
Distutils 1.0 will, if all goes well, be the version included with
! Python 1.6 (final). (If all does not go well, that version will be
1.0.1 or 1.0.2 or so.)
--- 295,307 ----
http://www.python.org/mailman/listinfo/distutils-sig
+ Also, take a look through the TODO file to see a more recent/complete
+ version of the Distutils to-do list.
+
FUTURE PLANS
------------
Distutils 1.0 will, if all goes well, be the version included with
! Python 2.0 (final). (If all does not go well, that version will be
1.0.1 or 1.0.2 or so.)
***************
*** 339,343 ****
* Thomas Heller: more work on the registry support, several
bug fixes in the Windows support, and just generally improving
! the code for compiling extensions on Windows
* Eric Tiedemann: bug fixes
* Fred Drake and Guido van Rossum: helping to figure out the
--- 337,342 ----
* Thomas Heller: more work on the registry support, several
bug fixes in the Windows support, and just generally improving
! the code for compiling extensions on Windows; also, the
! "bdist_wininst" command (and associated C code)
* Eric Tiedemann: bug fixes
* Fred Drake and Guido van Rossum: helping to figure out the
***************
*** 345,356 ****
* Joe Van Andel: tweaks to the sysconfig module, misc. bug fixes
* Corran Webster: Mac OS support in general
! * Bastian Kleineidam: the "clean" command, and a pile of
! patches, bug-fixes, and ideas, large and small
* Lyle Johnson: bug-spotting and -fixing; support for Borland's C/C++
! compiler (forthcoming)
* Harry Henry Gebel: bug-spotting and -fixing; the "bztar" archive
format; the "bdist_rpm" command
! * Rene Liebscher: smarter extension-building; Cygwin/Mingw32 support
! (forthcoming)
[spiritual, in roughly chronological order since the birth of the project]
--- 344,356 ----
* Joe Van Andel: tweaks to the sysconfig module, misc. bug fixes
* Corran Webster: Mac OS support in general
! * Bastian Kleineidam: a bunch of small but vital commands: clean,
! install_scripts, install_data, build_scripts; a pile of patches,
! bug-fixes, and good ideas, large and small
* Lyle Johnson: bug-spotting and -fixing; support for Borland's C/C++
! compiler
* Harry Henry Gebel: bug-spotting and -fixing; the "bztar" archive
format; the "bdist_rpm" command
! * Rene Liebscher: smarter extension-building; Cygwin/Mingw32 support;
! more help options
[spiritual, in roughly chronological order since the birth of the project]
Index: CHANGES.txt
===================================================================
RCS file: /cvsroot/python/distutils/CHANGES.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -r1.10 -r1.11
*** CHANGES.txt 2000/04/25 03:05:17 1.10
--- CHANGES.txt 2000/06/30 02:54:00 1.11
***************
*** 1,2 ****
--- 1,89 ----
+ Release 0.9 (29 June, 2000):
+ ----------------------------
+ * added config file mechanism
+
+ * added "bdist_rpm" command: create an RPM built distribution (thanks to
+ Harry Henry Gebel)
+
+ * added "bdist_wininst" command: create an executable Windows installer
+ (self-extracting ZIP file with a small GUI) (thanks to Thomas
+ Heller)
+
+ * added extra help options to list the available C/C++ compilers
+ ("build_ext", "build_clib" commands), archive formats for source
+ distributions ("sdist"), and formats for built distributions
+ ("bdist") (thanks to Rene Liebscher)
+
+ * added "install_data" and "install_scripts" commands to install,
+ respectively, arbitrary data files and scripts (thanks to Bastian
+ Kleineidam)
+
+ * added the "build_scripts" command, mainly to fix the "#!" line
+ of Python scripts to point to the current Python interpreter
+ (Bastian Kleineidam again)
+
+ * added "install_headers" command to install C/C++ header files
+ (to the include/python<ver> directory by default)
+
+ * added a new, much simpler way to describe extensions in the setup
+ script (no more hairy list-of-tuples-of-dicts: just call the
+ Extension constructor to create an Extension object that describes
+ your extension)
+
+ * modified all the example setup scripts to use the new way of
+ describing extensions (thanks to Harry Henry Gebel for help)
+
+ * added another bit of meta-data: the "long description" (Harry Henry
+ Gebel)
+
+ * added the ability to compile and link in resource files with
+ Visual C++ on Windows (Thomas Heller)
+
+ * extension building now works on AIX (actually tested this time)
+ (thanks to Rene Liebscher for the initial patch, and Vladimir
+ Marangozov for testing)
+
+ * extension building now works on OSF/1 (aka Digital Unix, aka Tru64
+ Unix) (thanks to Mark Favas for testing)
+
+ * experimental support for auto-configuration, via the "config" command
+ (think "Autoconf in Python")
+
+ * modified example setup scripts for PIL and mxDateTime to do some
+ auto-configuration (only partially implemented -- no support for
+ actually using the information discovered during the build process)
+
+ * experimental interface to Borland C++ for building extensions on
+ Windows (thanks to Lyle Johnson)
+
+ * experimental interface to Cygwin and Mingw32 ports of GCC for building
+ extensions on Windows (thanks to Rene Liebscher)
+
+ * added ability to select which compiler to use as an option to "build",
+ "build_ext", and/or "build_clib"
+
+ * experimental support for building extensions from SWIG interface files
+
+ * added more ways to sneak compiler and/or linker options in through
+ the back door ('extra_link_args', 'extra_compile_args' when
+ constructing an Extension object, for now)
+
+ * fixed a bunch of silly bugs in "sdist"; most importantly, it will now
+ exclude directories from the source distribution that really shouldn't
+ be there (like the build tree, the temporary tree that is used to
+ build the source distribution archive, CVS and RCS directories, ...)
+
+ * added a minimal debugging framework (set environment variable
+ DISTUTILS_DEBUG to 1 and you get a *lot* more feedback!)
+
+ * added the notion of "list of symbols to export" to CCompiler interface
+
+ * added preprocessor interface to CCompiler (only implemented in
+ UnixCCompiler, so far)
+
+ * better separation of responsibilities between the UnixCCompiler class
+ and the build_ext command
+
+
Release 0.8.2 (24 April, 2000):
-------------------------------