There was both a parser bug (where accents were taking precedence over
symbols), and a mapping bug (where ldots was mapped to the wrong Unicode
code point). Both of these should now be fixed on the branch and
trunk. Let me know if you see any further problems.
Mike
Fernando Perez wrote:
> Ho
Hi Michael,
[Cc'ing nipy-dev, where we ran into the problem. Docs should look
fine now, if you rebuild mpl]
On Wed, Feb 4, 2009 at 7:42 AM, Michael Droettboom wrote:
> There was both a parser bug (where accents were taking precedence over
> symbols), and a mapping bug (where ldots was mapped to
Another vote here for changing resolution=1 to be the default. It seems
strange to plot values on a line plot and not have the values connected. At
least in my area, every polar plot of real-world data we make needs to set this
flag to 1 or the wrong plot is created.
Ted
> -Original Mess
Hello,
I was having trouble getting matplotlib to link to the correct Tcl and
Tk, and as a result uncovered what I would call a bug, or at least
unpredictable behavior.
Basically, I have a custom Tcl/Tk installation, and I setup python to
correctly find them, so I have the expectation that Matplo
I should also add that the reason it won't find my tclConfig.sh and
tkConfig.sh files is because they were configured/installed with the
--prefix option, but with the information from Python this is easily
resolvable.
Jayson
On Wed, Feb 4, 2009 at 3:08 PM, Jayson Barr wrote:
> Hello,
>
> I was h
