matplotlib-devel Mailing List for matplotlib

This release is compiled against numpy-1.0 final. The binaries are
fresh on sourceforge, so they may take some time to propagate to the
mirrors.
http://cheeseshop.python.org/pypi/matplotlib/
http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
Note: There is a compile error on python2.3 that will probably require
a slight modification to the released source. Please allow some time
for us to fix this and post the binaries.
===============================================================
2006年10月26日 Released 0.87.7 at revision 2835
2006年10月25日 Made "tiny" kwarg in Locator.nonsingular much smaller - EF
2006年10月17日 Closed sf bug 1562496 update line props dash/solid/cap/join
 styles - JDH
2006年10月17日 Complete overhaul of the annotations API and example code -
 See matplotlib.text.Annotation and
 examples/annotation_demo.py JDH
2006年10月12日 Committed Manuel Metz's StarPolygon code and
 examples/scatter_star_poly.py - JDH
2006年10月11日 commented out all default values in matplotlibrc.template
 Default values should generally be taken from defaultParam in
 __init__.py - the file matplotlib should only contain those values
 that the user wants to explicitly change from the default.
 (see thread "marker color handling" on matplotlib-devel)
2006年10月10日 Changed default comment character for load to '#' - JDH
2006年10月10日 deactivated rcfile-configurability of markerfacecolor
 and markeredgecolor. Both are now hardcoded to the special value
	 'auto' to follow the line color. Configurability at run-time
	 (using function arguments) remains functional. - NN
2006年10月07日 introduced dummy argument magnification=1.0 to
 FigImage.make_image to satisfy unit test figimage_demo.py
 The argument is not yet handled correctly, which should only
	 show up when using non-standard DPI settings in PS backend,
	 introduced by patch #1562394. - NN
2006年10月06日 add backend-agnostic example: simple3d.py - NN
2006年09月29日 fix line-breaking for SVG-inline images (purely cosmetic) - NN
2006年09月29日 reworked set_linestyle and set_marker
	 markeredgecolor and markerfacecolor now default to
	 a special value "auto" that keeps the color in sync with
	 the line color
	 further, the intelligence of axes.plot is cleaned up,
	 improved and simplified. Complete compatibility cannot be
	 guaranteed, but the new behavior should be much more predictable
	 (see patch #1104615 for details) - NN
2006年09月29日 changed implementation of clip-path in SVG to work around a
 limitation in inkscape - NN
2006年09月29日 added two options to matplotlibrc:
	 svg.image_inline
	 svg.image_noscale
	 see patch #1533010 for details - NN
2006年09月29日 axes.py: cleaned up kwargs checking - NN
2006年09月29日 setup.py: cleaned up setup logic - NN
2006年09月29日 setup.py: check for required pygtk versions, fixes bug #1460783 - SC

Hey all. I am building the windows binaries of mpl-0.87.7 and I am
running into a problem with python2.3 that I have never ran into
before. I don't have too much time debug it, so I was wondering if
anyone made changes to _isnan? There is a linking error for it, and
it appears a python2.4+ dependency was added.
Thanks,
 Charlie
gcc -mno-cygwin -O2 -Wall -Wstrict-prototypes -Iwin32_static\include -I. -Ic:\Py
thon23\include -Ic:\Python23\PC -c src/_isnan.c -o build\temp.win32-2.3\Release\
src\_isnan.o
g++ -mno-cygwin -shared build\temp.win32-2.3\Release\src\_isnan.o -Lwin32_static
\lib -Lc:\Python23\libs -Lc:\Python23\PCBuild -lpython23 -o build\lib.win32-2.3\
matplotlib\_isnan.pyd
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x20):_isnan.c: undefined refere
nce to `_imp__PyArg_ParseTuple'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x55):_isnan.c: undefined refere
nce to `_imp___Py_TrueStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x5d):_isnan.c: undefined refere
nce to `_imp___Py_TrueStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x71):_isnan.c: undefined refere
nce to `_imp___Py_ZeroStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0x79):_isnan.c: undefined refere
nce to `_imp___Py_ZeroStruct'
build\temp.win32-2.3\Release\src\_isnan.o(.text+0xbd):_isnan.c: undefined refere
nce to `_imp__Py_InitModule4'
collect2: ld returned 1 exit status
error: Command "g++ -mno-cygwin -shared build\temp.win32-2.3\Release\src\_isnan.
o -Lwin32_static\lib -Lc:\Python23\libs -Lc:\Python23\PCBuild -lpython23 -o buil
d\lib.win32-2.3\matplotlib\_isnan.pyd" failed with exit status 1

We are very pleased to announce the release of NumPy 1.0 available for 
download at http://www.numpy.org
This release is the culmination of over 18 months of effort to allow 
unification of the Numeric and Numarray communities. NumPy provides the 
features of both packages as well as comparable speeds in the domains 
where both were considered fast --- often beating both packages on 
certain problems. If there is an area where we can speed up NumPy then 
we are interested in hearing about the solution.
NumPy is essentially a re-write of Numeric to include the features of 
Numarray plus more. NumPy is a C-based extension module to Python that 
provides an N-dimensional array object (ndarray), a collection of fast 
math functions, basic linear algebra, array-producing random number 
generators, and basic Fourier transform capabilities.
Also included with NumPy are:
1) A data-type object. The data-type of all NumPy arrays are defined by 
a data-type object that describes how the block of memory that makes up 
an element of the array is to be interpreted. Supported are all basic 
C-types, structures containing C-types, arrays of C-types, and 
structures containing structures of C-types. Data-types can also be in 
big or little-endian order. NumPy arrays can therefore be constructed 
from any regularly-sized chunk of data. A chunk of data can also be a 
pointer to a Python object and therefore Object arrays can be 
constructed (including record arrays with object members).
2) Array scalars: there is a Python scalar object (inheriting from the 
standard object where possible) defined for every basic data-type that 
an array can have.
2) A matrix object so that '*' is re-defined as matrix-multiplication 
and '**' as matrix-power.
3) A character array object that can replace Numarray's similarly-named 
object. It is basically an array of strings (or unicode) with methods 
matching the string and unicode methods.
4) A record array that builds on the advanced data-type support of the 
basic array object to allow field access using attribute look-up as well 
as to provide more ways to build-up a record-array.
5) A memory-map object that makes it easier to use memory-mapped areas 
as the memory for an array object.
6) A basic container class that uses the ndarray as a member. This 
often facilitates multiple-inheritance.
7) A large collection of basic functions on the array.
8) Compatibility layer for Numeric including code to help in the 
conversion to NumPy and full C-API support.
9) Compatibility layer for NumPy including code to help in the 
conversion to NumPy and full C-API support.
NumPy can work with Numeric and Numarray installed and while the three 
array objects are different to Python, they can all share each other's 
data through the use of the array interface.
As the developers for Numeric we can definitively say development of 
Numeric has ceased as has effective support. You may still find an 
answer to a question or two and Numeric will be available for download 
as long as Sourceforge is around so and code written to Numeric will 
still work, but there will not be "official" releases of Numeric for 
future versions of Python (including Python2.5).
The development of NumPy has been supported by the people at STScI who 
created Numarray and support it. They have started to port their 
applications to NumPy and have indicated that support for Numarray will 
be phased out over the next year.
You are strongly encouraged to move to NumPy. The whole point of NumPy 
is to unite the Numeric/Numarray development and user communities. We 
have done our part in releasing NumPy 1.0 and doing our best to make the 
transistion as easy as possible. Please support us by adopting NumPy. 
If you have trouble with that, please let us know why so that we can 
address the problems you identify. Even better, help us in fixing the 
problems.
New users should download NumPy first unless they need an older package 
to work with third party code. Third-party package writers should 
migrate to use NumPy. Though it is not difficult, there are some things 
that have to be altered. Several people are available to help with that 
process, just ask (we will do it free for open source code and as 
work-for-hire for commercial code).
This release would not have been possible without the work of many 
people. Thanks go to (if we have missed your contribution please let 
us know):
 * Travis Oliphant for the majority of the code adaptation (blame him 
for code problems :-) )
 * Jim Hugunin, Paul Dubois, Konrad Hinsen, David Ascher, Jim Fulton 
and many others for Numeric on which the code is based.
 * Perry Greenfield, J Todd Miller, Rick White, Paul Barrett for 
Numarray which gave much inspiration and showed the way forward.
 * Paul Dubois for Masked Arrays
 * Pearu Peterson for f2py and numpy.distutils and help with code 
organization
 * Robert Kern for mtrand, bug fixes, help with distutils, code 
organization, and much more.
 * David Cooke for many code improvements including the auto-generated 
C-API and optimizations.
 * Alexander Belopolsky (Sasha) for Masked array bug-fixes and tests, 
rank-0 array improvements, scalar math help and other code additions
 * Francesc Altet for unicode and nested record tests and much help 
with rooting out nested record array bugs.
 * Tim Hochberg for getting the build working on MSVC, optimization 
improvements, and code review
 * Charles Harris for the sorting code originally written for Numarray 
and for improvements to polyfit, many bug fixes, and documentation strings.
 * Robert Cimrman for numpy.distutils help and the set-operations for 
arrays
 * David Huard for histogram code improvements including 2-d and d-d code
 * Eric Jones for sundry subroutines borrowed from scipy_base
 * Fernando Perez for code snippets, ideas, bugfixes, and testing.
 * Ed Schofield for matrix.py patches, bugfixes, testing, and docstrings.
 * John Hunter for code snippets (from matplotlib)
 * Chris Hanley for help with records.py, testing, and bug fixes.
 * Travis Vaught, Joe Cooper, Jeff Strunk for administration of 
numpy.org web site and SVN
 * Andrew Straw for bug-reports and help with www.scipy.org
 * Albert Strasheim for bug-reports, unit-testing and Valgrind runs
 * Stefan van der Walt for bug-reports, regression-testing, and 
bug-fixes.
 * Eric Firing for bugfixes.
 * Arnd Baecker for 64-bit testing
 * A.M. Archibald for code that decreases the number of times reshape 
makes a copy.
More information is available at http://numpy.scipy.org and 
http://www.scipy.org. Bug-reports and feature requests should be 
submitted as tickets to the Trac pages at 
http://projects.scipy.org/scipy/numpy/
As an anti-SPAM measure, you must create an account in order to post 
tickets.
Enjoy the new release,
Sincerely,
The NumPy Developers
*Disclaimer*: The main author, Travis Oliphant, has written a 350+ page 
book entitled "Guide to NumPy" that documents the new system fairly 
thoroughly. The first two chapters of this book are available on-line 
for free, but the remainder must be purchased (until 2010 or a certain 
number of total sales has been reached). See http://www.trelgol.com for 
more details. There is plenty of free documentation available now for 
NumPy, however. Go to http://www.scipy.org for more details.