matplotlib-devel Mailing List for matplotlib

On Thursday 02 February 2006 15:26, Ed Schofield wrote:
> Hi all,
>
> Matplotlib CVS has a bug in the validate_key() function in __init__.py
> that prevents it from corrrectly handling unrecognized entries in the
> matplotlibrc file. The attached patch fixes it by passing the
> (previously undefined) variable fname.
Thanks, this is fixed in cvs.

Hi all,
Matplotlib CVS has a bug in the validate_key() function in __init__.py
that prevents it from corrrectly handling unrecognized entries in the
matplotlibrc file. The attached patch fixes it by passing the
(previously undefined) variable fname.
-- Ed
Index: __init__.py
===================================================================
RCS file: /cvsroot/matplotlib/matplotlib/lib/matplotlib/__init__.py,v
retrieving revision 1.114
diff -r1.114 __init__.py
885c885
< def validate_key(key, val, line, cnt, fail_on_error):
---
> def validate_key(key, val, line, cnt, fname, fail_on_error):
949c949
< cval = validate_key(key, val, line, cnt, fail_on_error)
---
> cval = validate_key(key, val, line, cnt, fname, fail_on_error)
954c954
< cval = validate_key(key, val, line, cnt, fail_on_error)
---
> cval = validate_key(key, val, line, cnt, fname, fail_on_error)

Currently when plotting dates the tick mark locations
are only generated once, so when zooming in on a plot
takes you between tick marks, they dissapear.
Attatched is a patch file (against the cvs repository
as of 10:40am, Feb 02, 2006) that has an
AutoDateLocator class that derives from the DateLocator
class. It essentially does what AutoLocator does,
except for Dates.
In addition I also provided an AutoDateFormatter class
that inherits from Formatter and will chande the format
of the date label based on the range of dates being
spanned in the current view.
The AutoDateFormatter class may not be as robust as it
could be, but it might be nice to have it around.
The attatched patch file will set the default behaviour
of date plots to use both AutoDateLocator and
AutoDateFormatter. 
--James Evans

On Thursday 02 February 2006 09:05, Darren Dale wrote:
> My current mpl cvs checkout wont build. I guess this is a problem
> with my OS (gentoo), although I just built numpy and scipy without
> problems. Could anyone suggest why
> - L / u s r / l i b 6 4 / t k 8 . 4 / . . /
> appears on line 2 instead of
> -L/usr/lib64/tk8.4/../
I found the problem. In setupext.py, line 320, tk_lib is formatted as unicode 
on my machine. I changed this:
o.tk_lib = os.path.join((tk.getvar('tk_library')), '../')
to this:
o.tk_lib = os.path.join(str(tk.getvar('tk_library')), '../')
and I can build mpl again.
changes in cvs.

My current mpl cvs checkout wont build. I guess this is a problem 
with my OS (gentoo), although I just built numpy and scipy without 
problems. Could anyone suggest why 
- L / u s r / l i b 6 4 / t k 8 . 4 / . . / 
appears on line 2 instead of 
-L/usr/lib64/tk8.4/../
Thanks,
Darren
x86_64-pc-linux-gnu-gcc: src/_tkagg.cpp
x86_64-pc-linux-gnu-g++ -pthread -shared build/temp.linux-x86_64-2.4/src/_tkagg.o build/temp.linux-x86_64-2.4/CXX/cxx_extensions.o build/temp.linux-x86_64-2.4/CXX/cxxsupport.o build/temp.linux-x86_64-2.4/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-2.4/CXX/cxxextensions.o -L/usr/lib64/tcl8.4/../ - L / u s r / l i b 6 4 / t k 8 . 4 / . . / -L/usr/local/lib -L/usr/lib -L/usr/local/lib -L/usr/lib -ltk8.4 -ltcl8.4 -lpng -lz -lstdc++ -lm -lfreetype -lz -lstdc++ -lm -o build/lib.linux-x86_64-2.4/matplotlib/backends/_tkagg.so
x86_64-pc-linux-gnu-g++: L: No such file or directory
x86_64-pc-linux-gnu-g++: u: No such file or directory
x86_64-pc-linux-gnu-g++: s: No such file or directory
x86_64-pc-linux-gnu-g++: r: No such file or directory
x86_64-pc-linux-gnu-g++: l: No such file or directory
x86_64-pc-linux-gnu-g++: i: No such file or directory
x86_64-pc-linux-gnu-g++: b: No such file or directory
x86_64-pc-linux-gnu-g++: 6: No such file or directory
x86_64-pc-linux-gnu-g++: 4: No such file or directory
x86_64-pc-linux-gnu-g++: t: No such file or directory
x86_64-pc-linux-gnu-g++: k: No such file or directory
x86_64-pc-linux-gnu-g++: 8: No such file or directory
x86_64-pc-linux-gnu-g++: 4: No such file or directory
x86_64-pc-linux-gnu-g++: -E or -x required when input is from standard input
x86_64-pc-linux-gnu-g++: L: No such file or directory
x86_64-pc-linux-gnu-g++: u: No such file or directory
x86_64-pc-linux-gnu-g++: s: No such file or directory
x86_64-pc-linux-gnu-g++: r: No such file or directory
x86_64-pc-linux-gnu-g++: l: No such file or directory
x86_64-pc-linux-gnu-g++: i: No such file or directory
x86_64-pc-linux-gnu-g++: b: No such file or directory
x86_64-pc-linux-gnu-g++: 6: No such file or directory
x86_64-pc-linux-gnu-g++: 4: No such file or directory
x86_64-pc-linux-gnu-g++: t: No such file or directory
x86_64-pc-linux-gnu-g++: k: No such file or directory
x86_64-pc-linux-gnu-g++: 8: No such file or directory
x86_64-pc-linux-gnu-g++: 4: No such file or directory
x86_64-pc-linux-gnu-g++: -E or -x required when input is from standard input
error: Command "x86_64-pc-linux-gnu-g++ -pthread -shared build/temp.linux-x86_64-2.4/src/_tkagg.o build/temp.linux-x86_64-2.4/CXX/cxx_extensions.o build/temp.linux-x86_64-2.4/CXX/cxxsupport.o build/temp.linux-x86_64-2.4/CXX/IndirectPythonInterface.o build/temp.linux-x86_64-2.4/CXX/cxxextensions.o -L/usr/lib64/tcl8.4/../ - L / u s r / l i b 6 4 / t k 8 . 4 / . . / -L/usr/local/lib -L/usr/lib -L/usr/local/lib -L/usr/lib -ltk8.4 -ltcl8.4 -lpng -lz -lstdc++ -lm -lfreetype -lz -lstdc++ -lm -o build/lib.linux-x86_64-2.4/matplotlib/backends/_tkagg.so" failed with exit status 1