[Scipy-svn] r5298 - trunk/doc/release

[scipy-svn at scipy.org]

Author: jarrod.millman
Date: 2008-12-30 08:52:31 -0600 (Tue, 30 Dec 2008)
New Revision: 5298

Modified:
   trunk/doc/release/0.7.0-notes.rst
Log:
working on release notes


Modified: trunk/doc/release/0.7.0-notes.rst
===================================================================
--- trunk/doc/release/0.7.0-notes.rst	2008-12-30 13:52:27 UTC (rev 5297)
+++ trunk/doc/release/0.7.0-notes.rst	2008-12-30 14:52:31 UTC (rev 5298)
@@ -2,10 +2,36 @@
 SciPy 0.7.0 Release Notes
 =========================
 
-This is a new stable release.  Please note that unlike previous versions
-of SciPy, this release requires Python 2.4 or greater.  This release also
-requires NumPy 1.2.0 or greater.
+.. contents::
 
+This stable release comes almost one year after the 0.6.0 release
+and contains many new features, numerous bug-fixes, improved test
+coverage, and better documentation.
+
+Please note that unlike previous versions of SciPy, this release
+requires Python 2.4 or 2.5.  This release also requires NumPy 1.2.0
+or greater.
+
+.. note:: Python 2.6 and 3.0
+
+   Python 3.0 is not supported at all:  it requires NumPy to be ported to
+   Python 3.0, which is a massive effort, since a lot of C code has to be
+   ported.  It will happen, but not anytime soon.
+
+The main issue with 2.6 support is numpy. On Unix (including Mac OS X), numpy
+1.2.1 mostly works, with a few caveats. On windows, there are some problems
+related to the compilation process. The upcoming 1.3 version of numpy will fix
+those. Then, because of some python 2.6 bugs, f2py does not work on python 2.6;
+the fixes will also be in the upcoming numpy 1.3.
+
+The bottom line: if you can avoid it, do not use python 2.6 yet for
+numpy/scipy. If you really need scipy on python 2.6, then it is recommended
+have to build numpy from svn by yourself, and then build scipy.
+
+License review
+~~~~~~~~~~~~~~
+
+
 Changes
 -------
 
@@ -192,8 +218,8 @@
 Users of ``scipy.interpolate.interp1d`` may need to revise their code
 if it relies on the incorrect behavior.
 
-Bug fixes in the stats package
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Statistics package
+~~~~~~~~~~~~~~~~~~
 
 Statistical functions for masked arrays have been added and are accessible 
 through scipy.stats.mstats. The functions are similar to their counterparts 
@@ -239,19 +265,13 @@
 Support for NumScons has been added. NumScons is a tentative new
 build system for NumPy/SciPy, using scons at its core.
 
-Python 2.6 and 3.0
-------------------
+Sandbox Removed
+~~~~~~~~~~~~~~~
 
-Python 3.0 is not supported at all: it requires numpy to be ported to python
-3.0, which is a massive effort, since a lot of C code has to be ported. It will
-happen, but not anytime soon.
-
-The main issue with 2.6 support is numpy. On Unix (including Mac OS X), numpy
-1.2.1 mostly works, with a few caveats. On windows, there are some problems
-related to the compilation process. The upcoming 1.3 version of numpy will fix
-those. Then, because of some python 2.6 bugs, f2py does not work on python 2.6;
-the fixes will also be in the upcoming numpy 1.3.
-
-The bottom line: if you can avoid it, do not use python 2.6 yet for
-numpy/scipy. If you really need scipy on python 2.6, then it is recommended
-have to build numpy from svn by yourself, and then build scipy.
+While porting SciPy to NumPy in 2005, several packages and modules were moved into
+``scipy.sandbox``.  The sandbox was a staging ground for packages that were undergoing
+rapid development and whose APIs were in flux.  It was also a place where broken code
+could live.  The sandbox has served its purpose well and was starting to create confusion,
+so ``scipy.sandbox`` was removed.  Most of the code was moved into ``scipy``, some code was
+made into a ``scikit``, and the remaining code was just deleted as the functionality had
+been replaced by other code.