matplotlib-devel Mailing List for matplotlib

On Mon, Jan 10, 2011 at 6:45 PM, Benjamin Root <ben...@ou...> wrote:
> John,
>
> Just to clarify, have we officially released 1.0.1, or are we still in the
> RC phase? If we haven't released yet, what is the deadline for final
> patches for 1.0.1?
>
1.0.1 is final but I held off on the announcement until Russel got the
OSX builds uploaded (which he did yesterday, but I still haven't
gotten to the announcement). If there are significant problems (eg
the 3D stuff you reported or other issues) I have no problem pushing
out 1.0.2 quickly.
JDH

I am on the online version of the matplotlib documentation, and I am finding
some artifacts of the Sphinx build.
For example there is ".. _gridspec-guide:" at the top of the page on
http://matplotlib.sourceforge.net/users/gridspec.html
There is also a " `AxesGrid`_" in the last paragraph of this section:
http://matplotlib.sourceforge.net/mpl_toolkits/axes_grid/users/overview.html#what-is-axesgrid-toolkit
I can probably fix these if these are the only ones, but I mention it here
in case anyone has a clue what happened (and where there might be others)
and knows how to fix it.
Ben Root

John,
Just to clarify, have we officially released 1.0.1, or are we still in the
RC phase? If we haven't released yet, what is the deadline for final
patches for 1.0.1?
Ben Root

Hi John,
On Thu, Jan 6, 2011 at 20:57, John Hunter <jd...@gm...> wrote:
> On Thu, Jan 6, 2011 at 1:24 PM, Benjamin Root <ben...@ou...> wrote:
>> Ah, all the more reason to apply abspath() or realpath(). To decide which
>> to use, let's consider the case of someone (like a developer) having
>> multiple builds of matplotlib in separate directories, and uses a symlink to
>> point to whichever he wants to use at the moment.
>>
>> The question is, in this use-case, would we want the symbolic link pathname,
>> or the absolute pathname? I don't mess around with docs enough to know
>> which I would want.
>>
>> I have attached a modified patch (which uses realpath(), but could easily be
>> changed to abspath()). I also included some comments to more fully document
>> what is going on and the rational for the logic being taken.
>
> OK, I incorporated your changes and committed. Thanks.
Just to be sure: this patch is *not* in the released 1.0.1 tarball
(and it will be included in the next released version), is that
correct?
Anyhow, with a bit of hackery in our building process, I'm able to
prepare Debian packages without download anything from the net: thanks
a lot for your support throughout all the process!!
Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi