On Fri, Jul 25, 2008 at 4:12 PM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 25, 2008 at 18:37, John Hunter <[EMAIL PROTECTED]> wrote:
>> On Fri, Jul 25, 2008 at 10:42 AM, Sandro Tosi <[EMAIL PROTECTED]> wrote:
>>
>>> Thanks! i've just downlaoded: is 55M tarball the real intended size?
>>> it seems a little too big... ;)
>>
>> Argg, I forgot to svn clean before I did the sdist.  Please try again.
>>
>>  http://matplotlib.sourceforge.net/tmp/matplotlib-0.98.3rc1.tar.gz
>>
>> The new file is under 6M
>
> Yeah, much better :)
>
> I've updated the package in our trunk and it's building fine.
>
> Playing with the generated doc I got an error on "matplotlib.colorbar":
>
> "
> System Message: ERROR/3
> (/home/morph/deb/build-area/matplotlib-0.98.3rc1/doc/api/colorbar_api.rst,
> line 9)
>
> Error in "automodule" directive: unknown option: "show-inheritance".

The docs require sphinx 0.4, which if I recall correctly, we got
pushed into debian on short notice precisely to support the mpl docs.
 What version of sphinx are you using?

>From our earlier thread on the subject:

Mikhail Gusarov
 to Chris, me, Sandro, Michael
        

        
Twas brillig at 00:26:04 19.06.2008 UTC+07 when
[EMAIL PROTECTED] did gyre and gimble:

 MG> I just got a confirmation from Georg that he will release the next
 MG> version of sphinx this weekend, and I'll immediately prepare the
 MG> package.

Here we are:

Accepted:
python-sphinx_0.4-1_all.deb
 to pool/main/s/sphinx/python-sphinx_0.4-1_all.deb

-------------------------------------------------------------------------
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
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to