matplotlib-devel Mailing List for matplotlib (Page 4)

On Fri, 8 Aug 2008 08:47:11 -0500
 "John Hunter" <jd...@gm...> wrote:
> On Fri, Aug 8, 2008 at 8:20 AM, Nils Wagner
> <nw...@ia...> wrote:
> 
>> I have installed matplotlib locally on a linux box
>> (without root access).
>> Is it possible for o t h e r users to use my local
>> matplotlib installation ? The problem is that show()
>> doesn't produce a result on the screen.
>>
>> Any pointer would be appreciated.
> 
> This is really a question for matplotlib-users, but, 
>there is no
> reason this shouldn't work. Some of my colleagues have 
>run out of my
> directory before.
> 
> * what backend are they using?
> 
> * what test script are they trying (I suggest
> examples/pylab_examples/simple_plot.py
> 
> * what is the output of --verbose-debug when the other 
>users run this script?
> 
> * does it help to try different backends, eg if they 
>run the script
> with -dTKAgg, -dWXAgg, -dQt4Agg or -dGTKAgg
> 
> * what are the permissions on your install directory -- 
>can the
> other uses see all the files?
> 
> * what version of matplotlib are you using? What 
>platform (you say
> linux, but when reporting problems it helps to include 
>as much detail
> as possible). Are the users running from the console or 
>an X11
> session?
> 
> JDH
 
Hi John,
I think it was a missing matplotlibrc in ~/.matplotlib
Now it works fine.
Thank you very much !
Next time I will post to matploblib-user. Sorry for that.
Nils

Hello everybody,
I have sent this message to the user group, but thinking of it, it may be more
relevant to the development mailing list...so here it is again.
We are looking for the best way to plot a waterfall diagram in
Matplotlib. The 2 functions which could be used 
to do that are (as far as I have found) imshow and pcolormesh. Here is a
small script that use both to compare the output:
-----------------
from pylab import *
delta = 0.2
x = arange(-3.0, 3.0, delta)
y = arange(-2.0, 2.0, delta)
X, Y = meshgrid(x, y)
Z1 = bivariate_normal(X, Y, 1.0, 1.0, 0.0, 0.0)
Z2 = bivariate_normal(X, Y, 1.5, 0.5, 1, 1)
# difference of Gaussians
Z = 10.0 * (Z2 - Z1)
figure(1)
im = imshow(Z,extent=(-3,3,-2,2))
CS = contour(X, -Y, Z, 6,
 colors='k', # negative contours will be dashed by default
 )
clabel(CS, fontsize=9, inline=1)
title('Using imshow')
figure(2)
im = pcolormesh(X,-Y,Z)
CS = contour(X, -Y, Z, 6,
 colors='k', # negative contours will be dashed by default
 )
clabel(CS, fontsize=9, inline=1)
title('Using pcolormesh')
show()
---------------------
The problem is that we need some of the flexibility of pcolormesh (which
is able to map the matrix of value on any deformed mesh), while
we would like to use the interpolations available in imshow (which
explain why the imshow version is much "smoother" than the pcolormesh
one).
In fact, what would be needed is not the full flexibility of pcolormesh
(which can map the grid to any kind of shape), we "only" have to deal
with rectangular grids where x- and y- graduations are irregularly spaced.
Is there a drawing function in Matplotlib which would be able to work
with such a rectangular non-uniform grid?
And if not (and a quick look at the example and the code make me think 
that indeed the capability is currently not present),
what about an extension of imshow which would work as this:
 
im = imshow(Z,x_gridpos=x, y_gridpos=y) #specify the
position of the grid's nodes, instead of giving the extend and assuming
uniform spacing.
Longer term, would a pcolormesh accepting interpolation be possible? The
current behavior, averaging the color of the grids node to get a uniform
cell color, 
is quite rough except for a large number of cells...And even then, it
soon shows when you zoom in...
The best would be to allow the same interpolations as in imshow (or a
subset of it), and also allows to use interpolation before colormap
lookup (or after), 
like in Matlab. Indeed, Matlab allows to finely tune interpolation by
specifying Gouraud (interpolation after color
lookup)/Phong(interpolation before color lookup, i.e. for each pixel).
Phong is usually much better but also more CPU intensive. Phong is
especially when using discrete colormap, producing banded colors
equivalent to countour lines, while Gouraud does not work in those
cases.
Of course, the performance will be impacted by some of those
interpolation options, which would degrade performance in animations for
example.... but I think that having the different options available
would be very useful, it allows to have the highest map quality, or have
a "quick and dirty" map depending on situation (grid spacing, type of
map, animation or not, ...).
Best regards,
Greg.

On Fri, Aug 8, 2008 at 8:20 AM, Nils Wagner
<nw...@ia...> wrote:
> I have installed matplotlib locally on a linux box
> (without root access).
> Is it possible for o t h e r users to use my local
> matplotlib installation ? The problem is that show()
> doesn't produce a result on the screen.
>
> Any pointer would be appreciated.
This is really a question for matplotlib-users, but, there is no
reason this shouldn't work. Some of my colleagues have run out of my
directory before.
 * what backend are they using?
 * what test script are they trying (I suggest
examples/pylab_examples/simple_plot.py
 * what is the output of --verbose-debug when the other users run this script?
 * does it help to try different backends, eg if they run the script
with -dTKAgg, -dWXAgg, -dQt4Agg or -dGTKAgg
 * what are the permissions on your install directory -- can the
other uses see all the files?
 * what version of matplotlib are you using? What platform (you say
linux, but when reporting problems it helps to include as much detail
as possible). Are the users running from the console or an X11
session?
JDH

Hi all,
I have installed matplotlib locally on a linux box 
(without root access).
Is it possible for o t h e r users to use my local 
matplotlib installation ? The problem is that show() 
doesn't produce a result on the screen.
Any pointer would be appreciated.
 
Nils

John Hunter wrote:
> On Wed, Aug 6, 2008 at 8:51 AM, Manuel Metz <mm...@as...> wrote:
> 
>> I think the section Controlling axes properties of
>> http://matplotlib.sourceforge.net/tutorial.html needs to be updated, since
>>
>> frame = gca(gca(), 'frame')
>> setp(frame, 'linewidth', 2)
>>
>> doesn't work any more with mpl 0.98.x ...
> 
> Argg, the dreaded frame/patch rears it's ugly head. Eric, did you add
> the deprecation warning? It seems to me we could use set/get frame to
> set the frame attr and set/get patch to set the patch attr to support
> people used to the matlab idiom as in the tutorial above.
Uh, I just noticed that the example couldn't have worked before ;-)
 frame = gca(gca(), 'frame') # fails
--> frame = getp(gca(), 'frame') #
;-)

On Wed, Aug 6, 2008 at 8:51 AM, Manuel Metz <mm...@as...> wrote:
> I think the section Controlling axes properties of
> http://matplotlib.sourceforge.net/tutorial.html needs to be updated, since
>
> frame = gca(gca(), 'frame')
> setp(frame, 'linewidth', 2)
>
> doesn't work any more with mpl 0.98.x ...
Argg, the dreaded frame/patch rears it's ugly head. Eric, did you add
the deprecation warning? It seems to me we could use set/get frame to
set the frame attr and set/get patch to set the patch attr to support
people used to the matlab idiom as in the tutorial above.

Hi,
 I think the section Controlling axes properties of 
http://matplotlib.sourceforge.net/tutorial.html needs to be updated, since
 frame = gca(gca(), 'frame')
 setp(frame, 'linewidth', 2)
doesn't work any more with mpl 0.98.x ...
Manuel

Thanks. This should be fixed in r5979. It seems to work fine over the 
backend_driver tests now.
Cheers,
Mike
Eric Firing wrote:
> Mike,
>
> Try contour_demo and contourf_demo--I think you will find that r5976 
> has whacked them both. I don't know how. I have not looked closely.
>
> Eric
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Mike,
Try contour_demo and contourf_demo--I think you will find that r5976 has 
whacked them both. I don't know how. I have not looked closely.
Eric

On Tue, Aug 5, 2008 at 6:30 PM, Darren Dale <dsd...@gm...> wrote:
> I've been wanting a physical quantities package based on numpy for quite a
> while. Over the weekend I started one, pulling code from Enthoughts units
> package and Charles Doutriaux's python wrappers of udunits (which appears to
> work on windows).
Hey Darren,
You may want to take a look at the examples/units/basic_units.py
module which is a poor-man's unit implementation. As a units package,
it's mostly worthless, and is used primarily for testing. But it will
show you how to connect to the mpl unit support to make your unit
arrays work with mpl (which can be done outside of mpl as in the
basic_units module or inside as in the dates support in the dates
module) usin the units registry. Of course, the support for custom
types is incomplete and limited to a few functions (notably plot), and
I have been promising to clarify the units API and requirements, but
in the meantime you might want to experiment with it to see how the
existing framework works with your package.
In terms of clarifying the units requirements, I have been thinking
about it a fair amount and I think this time has been fruitful, but I
haven't committed anything to paper yet.
JDH

Hi Everyone,
I've been wanting a physical quantities package based on numpy for quite a 
while. Over the weekend I started one, pulling code from Enthoughts units 
package and Charles Doutriaux's python wrappers of udunits (which appears to 
work on windows).
I've got a page up at http://dale.chess.cornell.edu/chess-wiki/Quantities 
which shows how this thing works and how to get it. Its pretty capable, 
reducing units automatically by default, but it provides a mechanism for 
preserving compound units too, like J, parsec/cm^3, m^2/m^3, and reducing 
them on demand. I also started a unit test suite.
Its pre-alpha, so dont go relying on it for production use, but I thought I 
would share it in case anyone is interested.
Darren

On Mon, Aug 4, 2008 at 15:41, Sandro Tosi <mat...@gm...> wrote:
> 2008年8月4日 Michael Droettboom <md...@st...>:
>> The graphviz failing is my bad. I failed to test the latex doc build (since
>> it never works for me anyway due to a too-old version of latex). This is
>> fixed in SVN r5962, and a patch against doc/sphinxext/inheritance_diagram.py
>> is attached.
> I'll apply it once at home and test if works in Debian: Thanks for the
> prompt reply!!
Patch applied and matplotlib 0.98.3 version has just been uploaded in
Debian: thank you guys for the support!!
A mail to Debian Release Team has been sent[1], let's see if they'll
accept it for Lenny.
Cheers,
Sandro
[1] http://lists.debian.org/debian-release/2008/08/msg00258.html
-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Hi guys,
a gentle kfreebsd porter, submitted a patch against setupext.py to
allow kfreebsd as arch for matplotlib.
I'm going to merge and upload mpl based on it, but he (and me, of
course) would be happy if you could merge this change directly in your
code (since the change is indipendent from Debian).
Thanks,
Sandro
On Tue, Aug 5, 2008 at 14:10, Petr Salinger <Pet...@se...> wrote:
> Package: matplotlib
> Severity: important
> Version: 0.98.3-1
> Tags: patch
> User: gli...@li...
> Usertags: kfreebsd
>
> Hi,
>
> the current version fails to build on GNU/kFreeBSD.
>
> It does not recognize kfreebsd7 based systems.
> Please extend debian/patches/build_fix.patch, see bellow.
>
> It would also be nice if you can ask upstream
> to include similar change.
>
> Thanks in advance
>
> --- debian/patches/build_fix.patch~ 2008年08月05日 13:44:10.000000000 +0000
> +++ debian/patches/build_fix.patch 2008年08月05日 13:44:10.000000000 +0000
> @@ -13,7 +13,7 @@
> 'cygwin' : ['/usr/local', '/usr',],
> 'darwin' : ['/sw/lib/freetype2', '/sw/lib/freetype219', '/usr/local',
> '/usr', '/sw', '/usr/X11R6'],
> -@@ -56,8 +56,8 @@
> +@@ -56,8 +56,10 @@
> 'freebsd5' : ['/usr/local', '/usr'],
> 'freebsd6' : ['/usr/local', '/usr'],
> 'sunos5' : [os.getenv('MPLIB_BASE') or '/usr/local',],
> @@ -21,6 +21,8 @@
> - 'gnukfreebsd6' : ['/usr/local', '/usr'],
> + 'gnukfreebsd5' : ['/usr'],
> + 'gnukfreebsd6' : ['/usr'],
> ++ 'gnukfreebsd7' : ['/usr'],
> ++ 'gnukfreebsd8' : ['/usr'],
> 'aix5' : ['/usr/local'],
> }
-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

2008年8月4日 Michael Droettboom <md...@st...>:
> The graphviz failing is my bad. I failed to test the latex doc build (since
> it never works for me anyway due to a too-old version of latex). This is
> fixed in SVN r5962, and a patch against doc/sphinxext/inheritance_diagram.py
> is attached.
Err... the attached patch is empty :D Anyhow, I'm subscribed to commit
ml, so I got it:
--- trunk/matplotlib/doc/sphinxext/inheritance_diagram.py
2008年08月04日 12:20:25 UTC (rev 5961)
+++ trunk/matplotlib/doc/sphinxext/inheritance_diagram.py
2008年08月04日 13:09:02 UTC (rev 5962)
@@ -346,7 +346,7 @@
 parts = node['parts']
 graph_hash = get_graph_hash(node)
- name = "inheritance%s"
+ name = "inheritance%s" % graph_hash
 pdf_path = os.path.join('_static', name + ".pdf")
 graph.run_dot(['-Tpdf', '-o%s' % pdf_path],
(sorry if gmail wraps it).
I'll apply it once at home and test if works in Debian: Thanks for the
prompt reply!!
Sandro
-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

The graphviz failing is my bad. I failed to test the latex doc build 
(since it never works for me anyway due to a too-old version of latex). 
This is fixed in SVN r5962, and a patch against 
doc/sphinxext/inheritance_diagram.py is attached.
Cheers,
Mike
Sandro Tosi wrote:
> On Sun, Aug 3, 2008 at 20:29, Sandro Tosi <mat...@gm...> wrote:
> 
>> On Sun, Aug 3, 2008 at 20:19, Charlie Moad <cw...@gm...> wrote:
>> 
>>> I was going to wait on John about the docs, but I went ahead and cut the
>>> 0.98.3 release. The sdist including the docs was 34MB, so I decided not to
>>> include them. This would also cause the binaries to be huge if we included
>>> them there as well. The source release is up/tagged and I will post
>>> binaries asap.
>>> 
>> Thanks a lot, Charlie!! I'm downloading the brand new tarball and I'll
>> upgrade the Debian package short after.
>> 
>
> While building (in a clean chroot) the package to upload in Debian, I
> noticed some errors at doc creation (I attach the complete log, it
> might help you to track the issue), something like:
>
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/axes.py:docstring
> of matplotlib.axes.Axes.acorr:35: (ERROR/3) Unexpected indentation.
> WARNING: <autodoc>:0: (ERROR/3) Unexpected indentation.
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/backend_bases.py:docstring
> of matplotlib.backend_bases.FigureCanvasBase.stop_event_loop_default:8:
> (WARNING/2) Literal block expected; none found.
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/backend_qt4agg_api.rst:5:
> (WARNING/2) autodoc can't import/find module
> 'matplotlib.backends.backend_qt4agg', it reported error: "cannot
> import name QtCore",please check your spelling and sys.path
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/cbook_api.rst:9:
> (WARNING/2) error while formatting signature for
> matplotlib.cbook.Xlator: arg is not a Python function
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
> of matplotlib.pyplot.acorr:55: (ERROR/3) Unexpected indentation.
> WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
> of matplotlib.pyplot.annotate:17: (ERROR/3) Unexpected indentation.
> [...]
> resolving references...
> writing... Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> WARNING: unusable reference target found:
> https://sourceforge.net/project/admin/?group_id=80706
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
> Error: <stdin>:1: syntax error near line 1
> context: digraph >>> inheritance <<< s {
> WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
> 'dot' returned the errorcode 1
>
> I don't know if something bad has happened in mpl code or something in
> Debian is broken right now (graphviz?), but it would help me if
> someone can confirm this is not happening only on my box.
>
> Thanks,
> 
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Eric Firing wrote:
> Jeff,
>
> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
>
> Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
> they are ill-advised. They are based on the assumption that input to 
> rotate_vector, which must be called before m_quiver, should be 
> describing a rectangular array of points; but this is not the case for a 
> typical oceanographic use-case, plotting current vectors as measured 
> along a ship track. In that case one naturally has 4 1-D vectors of the 
> same shape for U, V, X, and Y, and one does not want meshgrid to be 
> called on X and Y. If you want automatic meshgrid, it should be called 
> only if X and Y are 1-D *and* their lengths match the 2-D shape of U and V.
>
> Eric
> 
Eric: Sorry about that. For some reason, I was thinking that 
rotate_vector only made sense for gridded data, which is obviously 
wrong. Fixed in r5960.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328

Eric Firing wrote:
> Jeff,
> 
> http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
> 
> Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
Oops! I meant 5534; 5520 was the predecessor.
Eric

Jeff,
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/toolkits/basemap/lib/mpl_toolkits/basemap/__init__.py?r1=5520&r2=5534
Lines 2311 and 2312 in changeset 5520 have bitten me badly, and I think 
they are ill-advised. They are based on the assumption that input to 
rotate_vector, which must be called before m_quiver, should be 
describing a rectangular array of points; but this is not the case for a 
typical oceanographic use-case, plotting current vectors as measured 
along a ship track. In that case one naturally has 4 1-D vectors of the 
same shape for U, V, X, and Y, and one does not want meshgrid to be 
called on X and Y. If you want automatic meshgrid, it should be called 
only if X and Y are 1-D *and* their lengths match the 2-D shape of U and V.
Eric

On Sun, Aug 3, 2008 at 20:29, Sandro Tosi <mat...@gm...> wrote:
> On Sun, Aug 3, 2008 at 20:19, Charlie Moad <cw...@gm...> wrote:
>> I was going to wait on John about the docs, but I went ahead and cut the
>> 0.98.3 release. The sdist including the docs was 34MB, so I decided not to
>> include them. This would also cause the binaries to be huge if we included
>> them there as well. The source release is up/tagged and I will post
>> binaries asap.
>
> Thanks a lot, Charlie!! I'm downloading the brand new tarball and I'll
> upgrade the Debian package short after.
While building (in a clean chroot) the package to upload in Debian, I
noticed some errors at doc creation (I attach the complete log, it
might help you to track the issue), something like:
WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/axes.py:docstring
of matplotlib.axes.Axes.acorr:35: (ERROR/3) Unexpected indentation.
WARNING: <autodoc>:0: (ERROR/3) Unexpected indentation.
WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/backend_bases.py:docstring
of matplotlib.backend_bases.FigureCanvasBase.stop_event_loop_default:8:
(WARNING/2) Literal block expected; none found.
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/backend_qt4agg_api.rst:5:
(WARNING/2) autodoc can't import/find module
'matplotlib.backends.backend_qt4agg', it reported error: "cannot
import name QtCore",please check your spelling and sys.path
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/api/cbook_api.rst:9:
(WARNING/2) error while formatting signature for
matplotlib.cbook.Xlator: arg is not a Python function
WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
of matplotlib.pyplot.acorr:55: (ERROR/3) Unexpected indentation.
WARNING: /tmp/buildd/matplotlib-0.98.3/build/lib.linux-x86_64-2.5/matplotlib/pyplot.py:docstring
of matplotlib.pyplot.annotate:17: (ERROR/3) Unexpected indentation.
[...]
resolving references...
writing... Error: <stdin>:1: syntax error near line 1
context: digraph >>> inheritance <<< s {
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
'dot' returned the errorcode 1
WARNING: unusable reference target found:
https://sourceforge.net/project/admin/?group_id=80706
Error: <stdin>:1: syntax error near line 1
context: digraph >>> inheritance <<< s {
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
'dot' returned the errorcode 1
Error: <stdin>:1: syntax error near line 1
context: digraph >>> inheritance <<< s {
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
'dot' returned the errorcode 1
Error: <stdin>:1: syntax error near line 1
context: digraph >>> inheritance <<< s {
WARNING: /tmp/buildd/matplotlib-0.98.3/doc/index.rst:None: (WARNING/2)
'dot' returned the errorcode 1
I don't know if something bad has happened in mpl code or something in
Debian is broken right now (graphviz?), but it would help me if
someone can confirm this is not happening only on my box.
Thanks,
-- 
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Matplotlib 0.98.3 is now available for download. We are not pushing an
additional 0.91.x release at this time due to lack of updates to that
branch.
http://sourceforge.net/project/showfiles.php?group_id=80706
- Charlie
=================================================================
2008年08月03日 Released 0.98.3 at svn r5947
2008年08月01日 Backported memory leak fixes in _ttconv.cpp - MGD
2008年07月31日 Added masked array support to griddata. - JSW
2008年07月26日 Added optional C and reduce_C_function arguments to
 axes.hexbin(). This allows hexbin to accumulate the values
 of C based on the x,y coordinates and display in hexagonal
 bins. - ADS
2008年07月24日 Deprecated (raise NotImplementedError) all the mlab2
 functions from matplotlib.mlab out of concern that some of
 them were not clean room implementations. JDH
2008年07月24日 Rewrite of a significant portion of the clabel code (class
 ContourLabeler) to improve inlining. - DMK
2008年07月22日 Added Barbs polygon collection (similar to Quiver) for plotting
 wind barbs. Added corresponding helpers to Axes and pyplot as
 well. (examples/pylab_examples/barb_demo.py shows it off.) - RMM
2008年07月21日 Added scikits.delaunay as matplotlib.delaunay. Added griddata
 function in matplotlib.mlab, with example (griddata_demo.py) in
 pylab_examples. griddata function will use mpl_toolkits._natgrid
 if installed. - JSW
2008年07月21日 Re-introduced offset_copy that works in the context of the
 new transforms. - MGD
2008年07月21日 Committed patch by Ryan May to add get_offsets and
 set_offsets to Collections base class - EF
2008年07月21日 Changed the "asarray" strategy in image.py so that
 colormapping of masked input should work for all
 image types (thanks Klaus Zimmerman) - EF
2008年07月20日 Rewrote cbook.delete_masked_points and corresponding
 unit test to support rgb color array inputs, datetime
 inputs, etc. - EF
2008年07月20日 Renamed unit/axes_unit.py to cbook_unit.py and modified
 in accord with Ryan's move of delete_masked_points from
 axes to cbook. - EF
2008年07月18日 Check for nan and inf in axes.delete_masked_points().
 This should help hexbin and scatter deal with nans. - ADS
2008年07月17日 Added ability to manually select contour label locations.
 Also added a waitforbuttonpress function. - DMK
2008年07月17日 Fix bug with NaNs at end of path (thanks, Andrew Straw for
 the report) - MGD
2008年07月16日 Improve error handling in texmanager, thanks to Ian Henry
 for reporting - DSD
2008年07月12日 Added support for external backends with the
 "module://my_backend" syntax - JDH
2008年07月11日 Fix memory leak related to shared axes. Grouper should
 store weak references. - MGD
2008年07月10日 Bugfix: crash displaying fontconfig pattern - MGD
2008年07月10日 Bugfix: [ 2013963 ] update_datalim_bounds in Axes not works - MGD
2008年07月10日 Bugfix: [ 2014183 ] multiple imshow() causes gray edges - MGD
2008年07月09日 Fix rectangular axes patch on polar plots bug - MGD
2008年07月09日 Improve mathtext radical rendering - MGD
2008年07月08日 Improve mathtext superscript placement - MGD
2008年07月07日 Fix custom scales in pcolormesh (thanks Matthew Turk) - MGD
2008年07月03日 Implemented findobj method for artist and pyplot - see
 examples/pylab_examples/findobj_demo.py - JDH
2008年06月30日 Another attempt to fix TextWithDash - DSD
2008年06月30日 Removed Qt4 NavigationToolbar2.destroy -- it appears to
 have been unnecessary and caused a bug reported by P.
 Raybaut - DSD
2008年06月27日 Fixed tick positioning bug - MM
2008年06月27日 Fix dashed text bug where text was at the wrong end of the
 dash - MGD
2008年06月26日 Fix mathtext bug for expressions like $x_{\leftarrow}$ - MGD
2008年06月26日 Fix direction of horizontal/vertical hatches - MGD
2008年06月25日 Figure.figurePatch renamed Figure.patch, Axes.axesPatch
 renamed Axes.patch, Axes.axesFrame renamed Axes.frame,
 Axes.get_frame, which returns Axes.patch, is deprecated.
 Examples and users guide updated - JDH
2008年06月25日 Fix rendering quality of pcolor - MGD

Hi all,
 I am implementing a program using the candlestick function which plots
some finance data.
 After plotting some graph, I found that it doesn't follow the candlestick
charting convention according to:
http://stockcharts.com/school/doku.php?id=chart_school:chart_analysis:introduction_to_candlesticks
I have made some changes to candlestick in finance.py but I have no idea how
to modify candlestick2... because I am a python newbie.
I am posting the modified code to the list because I don't know how to get
it patched into the source control. Please let me know If I post it to the
wrong list.
----------------------------------------code section
begin-----------------------------
def candlestick(ax, quotes, width=0.2, colorup='k', colordown='r',
 alpha=1.0):
 """
 quotes is a list of (time, open, close, high, low, ...) tuples.
 As long as the first 5 elements of the tuples are these values,
 the tuple can be as long as you want (eg it may store volume).
 time must be in float days format - see date2num
 Plot the time, open, close, high, low as a vertical line ranging
 from low to high. Use a rectangular bar to represent the
 open-close span. If close >= open, use colorup to color the bar,
 otherwise use colordown
 ax : an Axes instance to plot to
 width : fraction of a day for the rectangle width
 colorup : the color of the rectangle where close >= open
 colordown : the color of the rectangle where close < open
 alpha : the rectangle alpha level
 return value is lines, patches where lines is a list of lines
 added and patches is a list of the rectangle patches added
 """
 OFFSET = width/2.0
 lines = []
 patches = []
 prev_close=-1
 for q in quotes:
 t, open, close, high, low = q[:5]
 if(prev_close==-1 or close>=prev_close):
 color_edge=colorup
 else:
 color_edge=colordown
 prev_close=close
 if close>=open :
 color_body='w'
 lower = open
 height = close-open
 vline1 = Line2D(
 xdata=(t, t), ydata=(close, high),
 color=color_edge,
 linewidth=0.5,
 antialiased=True,
 )
 vline2 = Line2D(
 xdata=(t, t), ydata=(open, low),
 color=color_edge,
 linewidth=0.5,
 antialiased=True,
 )
 else :
 color_body = color_edge
 lower = close
 height = open-close
 vline1 = Line2D(
 xdata=(t, t), ydata=(close, low),
 color=color_edge,
 linewidth=0.5,
 antialiased=True,
 )
 vline2 = Line2D(
 xdata=(t, t), ydata=(open, high),
 color=color_edge,
 linewidth=0.5,
 antialiased=True,
 )
 rect = Rectangle(
 xy = (t-OFFSET, lower),
 width = width,
 height = height,
 facecolor = color_body,
 edgecolor = color_edge,
 )
 rect.set_alpha(alpha)
 lines.append(vline1)
 lines.append(vline2)
 patches.append(rect)
 ax.add_line(vline1)
 ax.add_line(vline2)
 ax.add_patch(rect)
 ax.autoscale_view()
 return lines, patches
----------------------------------------code section
end-----------------------------