matplotlib-devel Mailing List for matplotlib

Normally, this would have been a bugfix release, but I reorganized the
matplotlib configuration files so thought it best to tick the version
number. All of the configuration files and dirs (matplotlibrc,
tex.cache, ttffont.cache ) now reside in $HOME/.matplotlib (on windows
C:\Documents and Settings\youracct\.matplotlib). Please rename your
.matplotlibrc file to matplotlibrc and put it there.
Other changes are 
2005年07月07日 Added Eric's MA set_xdata Line2D fix - JDH
2005年07月06日 Made HOME/.matplotlib the new config dir where the
 matplotlibrc file, the ttf.cache, and the tex.cache live.
 The new default filenames in .matplotlib have no leading
 dot and are not hidden. Eg, the new names are matplotlibrc
 tex.cache ttffont.cache. This is how ipython does it so it
 must be right. If old files are found, a warning is issued
 and they are moved to the new location. Also fixed
 texmanager to put all files, including temp files in
 ~/.matplotlib/tex.cache, which allows you to usetex in
 non-writable dirs.
2005年07月05日 Fixed bug #1231611 in subplots adjust layout. The problem
 was that the text cacheing mechanism was not using the
 transformation affine in the key. - JDH
2005年07月05日 Fixed default backend import problem when using API (SF bug
 # 1209354 - see API_CHANGES for more info - JDH
2005年07月04日 backend_gtk.py: require PyGTK version 2.0.0 or higher - SC
2005年06月30日 setupext.py: added numarray_inc_dirs for building against
 numarray when not installed in standard location - ADS
2005年06月27日 backend_svg.py: write figure width, height as int, not float.
 Update to fix some of the pychecker warnings - SC
 
2005年06月23日 Updated examples/agg_test.py to demonstrate curved paths
 and fills - JDH
2005年06月21日 Moved some texmanager and backend_agg tex caching to class
 level rather than instance level - JDH
2005年06月20日 setupext.py: fix problem where _nc_backend_gdk is installed to the
 wrong directory - SC
2005年06月19日 Added 10.4 support for CocoaAgg. - CM
2005年06月18日 Move Figure.get_width_height() to FigureCanvasBase and return
 int instead of float. - SC
2005年06月18日 Applied Ted Drain's QtAgg patch: 1) Changed the toolbar to
 be a horizontal bar of push buttons instead of a QToolbar
 and updated the layout algorithms in the main window
 accordingly. This eliminates the ability to drag and drop
 the toolbar and detach it from the window. 2) Updated the
 resize algorithm in the main window to show the correct
 size for the plot widget as requested. This works almost
 correctly right now. It looks to me like the final size of
 the widget is off by the border of the main window but I
 haven't figured out a way to get that information yet. We
 could just add a small margin to the new size but that
 seems a little hacky. 3) Changed the x/y location label to
 be in the toolbar like the Tk backend instead of as a
 status line at the bottom of the widget. 4) Changed the
 toolbar pixmaps to use the ppm files instead of the png
 files. I noticed that the Tk backend buttons looked much
 nicer and it uses the ppm files so I switched them.
2005年06月17日 Modified the gtk backend to not queue mouse motion events.
 This allows for live updates when dragging a slider. - CM
2005年06月17日 Added starter CocoaAgg backend. Only works on OS 10.3 for
 now and requires PyObjC. (10.4 is high priority) - CM
2005年06月17日 Upgraded pyparsing and applied Paul McGuire's suggestions
 for speeding things up. This more than doubles the speed
 of mathtext in my simple tests. JDH
2005年06月16日 Applied David Cooke's subplot make_key patch
Downloads at http://matplotlib.sf.net
Enjoy!
JDH

That's good to know. I tried googling it, but I guess I should've also 
checked CVS as well. I'm sure it's better than my hack anyways -- just 
good to have my scripts working again. I tend to prefer the subplot(w, 
h, n) since most of my plotting is automated, and it's more of a pain to 
have to convert the parameters to a string first, etc.
A
Eric Firing wrote:
> Abe,
>
> That bug has been fixed in CVS; like you, I tripped over it in 0.82 
> and tracked it down--but someone else had already fixed it. A 
> workaround, if you don't want to install from CVS, is to use the old 
> subplot(211) form instead of subplot(2,1,1).
>
> Eric
>
> Abraham Schneider wrote:
>
>> Hi. I just installed the newest version of matplotlib (0.82), and 
>> discovered all my subplots were ending on top of each other. After 
>> going through my code and verifying everything looked okay, I tried a 
>> simple:
>>
>> subplot(2, 1, 1); plot(range(0, 10)); subplot(2, 2, 2); plot(range(0, 
>> 10))
>>
>> and still only got one subplot. I went to the matplotlib code, and 
>> after some prodding, discovered that all the keys for the _seen map 
>> were exactly the same. Going to the _make_key function revealed that 
>> my use of subplot (i.e. three seperate arguments), was not working. 
>> Here is a fix that seems to work for me:
>>
>> (int _make_key function):
>> if iterable(args[0]):
>> key = tuple(args[0]), tuple( fixitems(kwargs.items()))
>> ## NEW
>> elif len(args) > 1:
>> key = args, tuple( fixitems(kwargs.items()))
>> ## \NEW
>> else:
>> key = args[0], tuple(fixitems( kwargs.items()))
>>
>> Abe
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
>> happening
>> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
>> core and dual graphics technology at this free one hour event hosted 
>> by HP,
>> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted 
> by HP,
> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Abe,
That bug has been fixed in CVS; like you, I tripped over it in 0.82 and 
tracked it down--but someone else had already fixed it. A workaround, 
if you don't want to install from CVS, is to use the old subplot(211) 
form instead of subplot(2,1,1).
Eric
Abraham Schneider wrote:
> Hi. I just installed the newest version of matplotlib (0.82), and 
> discovered all my subplots were ending on top of each other. After going 
> through my code and verifying everything looked okay, I tried a simple:
> 
> subplot(2, 1, 1); plot(range(0, 10)); subplot(2, 2, 2); plot(range(0, 10))
> 
> and still only got one subplot. I went to the matplotlib code, and after 
> some prodding, discovered that all the keys for the _seen map were 
> exactly the same. Going to the _make_key function revealed that my use 
> of subplot (i.e. three seperate arguments), was not working. Here is a 
> fix that seems to work for me:
> 
> (int _make_key function):
> if iterable(args[0]):
> key = tuple(args[0]), tuple( fixitems(kwargs.items()))
> ## NEW
> elif len(args) > 1:
> key = args, tuple( fixitems(kwargs.items()))
> ## \NEW
> else:
> key = args[0], tuple(fixitems( kwargs.items()))
> 
> Abe
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar 
> happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by HP,
> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi. I just installed the newest version of matplotlib (0.82), and 
discovered all my subplots were ending on top of each other. After going 
through my code and verifying everything looked okay, I tried a simple:
subplot(2, 1, 1); plot(range(0, 10)); subplot(2, 2, 2); plot(range(0, 10))
and still only got one subplot. I went to the matplotlib code, and after 
some prodding, discovered that all the keys for the _seen map were 
exactly the same. Going to the _make_key function revealed that my use 
of subplot (i.e. three seperate arguments), was not working. Here is a 
fix that seems to work for me:
(int _make_key function):
 if iterable(args[0]):
 key = tuple(args[0]), tuple( fixitems(kwargs.items()))
## NEW
 elif len(args) > 1:
 key = args, tuple( fixitems(kwargs.items()))
## \NEW
 else:
 key = args[0], tuple(fixitems( kwargs.items()))
Abe

John,
Attached is the diff against CVS for lines.py, with a fix for the 
set_xdata/set_ydata bug that Torsten found. The changes are:
(0) (Sorry--looks like part of the diff is caused merely by trailing 
space characters that my editor strips off.)
1) I replaced _masked_x and _masked_y attributes with _x_orig and 
_y_orig, which hold the inputs to set_data with no changes; they are 
always used, regardless of whether the inputs are masked or not. This 
leads to some simplification, and solves the problem Torsten found. The 
penalty is that if neither x nor y is masked and both are already 1-D 
numerix float arrays, then both are needlessly stored twice, once in 
_x_orig/_y_orig, and again in _x and _y. (Actually, this may not be 
true; I am not sure whether the arrays are duplicated or whether there 
are merely separate references to the same data arrays. I could figure 
it out, but I don't want to spend time on that now unless it is deemed 
urgent.)
2) I made some other changes in set_data to make it simpler and more 
readable; in particular, using ma.ravel() at the start eliminates 
several later conditionals and calls to ravel.
3) There seems to have been half-way support for letting either x or y 
be of length 1, and having it automatically expanded to match the other 
variable; I completed this support and moved it to near the top of the 
function. If it is not useful, it can be removed easily with no ill 
effects. (All it would be good for is making horizontal or vertical lines.)
Eric