On Tue, Dec 16, 2008 at 8:42 AM, John Hunter wrote:
>> Yep, 0.5 it is
>
> Let me correct that -- I will test Darren's patch and if we can make
> it work with an earlier sphinx I'm happy to try. Stay tuned. Darren,
> can I assume you have tested this with 0.4.2 and the docs are building
> for yo
On Tue, Dec 16, 2008 at 9:48 AM, John Hunter wrote:
> On Mon, Dec 15, 2008 at 10:02 AM, Darren Dale wrote:
>
> > You're right, the error does not occur with sphinx-0.5. It looks like the
> > API for registering nodes has changed as of 0.5. The development branch
> of
> > sphinx was throwing erro
On Mon, Dec 15, 2008 at 10:02 AM, Darren Dale wrote:
> You're right, the error does not occur with sphinx-0.5. It looks like the
> API for registering nodes has changed as of 0.5. The development branch of
> sphinx was throwing errors when it got to latex, so I had a look and came up
> with some
On Tue, Dec 16, 2008 at 8:40 AM, John Hunter wrote:
> On Tue, Dec 16, 2008 at 6:12 AM, Sandro Tosi wrote:
>
>> So, should the doc be build using sphinx 0.5? Would it be the standard
>> version of sphinx used by mpl now on? Just to know what dependency to
>> throw in once building mpl for Debian :
On Tue, Dec 16, 2008 at 6:12 AM, Sandro Tosi wrote:
> So, should the doc be build using sphinx 0.5? Would it be the standard
> version of sphinx used by mpl now on? Just to know what dependency to
> throw in once building mpl for Debian :)
Yep, 0.5 it is.
---
On Mon, Dec 15, 2008 at 17:02, Darren Dale wrote:
> (John suggested in a private email to try upgrading to sphinx-0.5.)
>
> You're right, the error does not occur with sphinx-0.5. It looks like the
> API for registering nodes has changed as of 0.5. The development branch of
> sphinx was throwing e
On Sat, Dec 13, 2008 at 10:32 AM, John Hunter wrote:
> On Sat, Dec 13, 2008 at 9:22 AM, Darren Dale wrote:
>
> >> I haven't been able to get to the root of this problem, but an
> "svn-clean"
> >> in the doc directory always fixes it for me.
> >
> > I tried that but the problem persists. I have s
On Sat, Dec 13, 2008 at 9:22 AM, Darren Dale wrote:
>> I haven't been able to get to the root of this problem, but an "svn-clean"
>> in the doc directory always fixes it for me.
>
> I tried that but the problem persists. I have sphinx-0.4.2 installed, are
> you using the same version?
Can you po
On Sat, Dec 13, 2008 at 8:48 AM, Michael Droettboom wrote:
> Darren Dale wrote:
>
>> I am seeing some errors when I build the docs, including import errors for
>> nonexistent date_support and basic_units modules, and:
>>
> I added the ability for explicitly setting sys.path so that modules in the
> I get a similar error that I assumed was caused by the docs being
> generated by the version of matplotlib that is currently installed,
> rather than the new version that has just been compiled. I know the
> debian package has a workaround for this.
Of course we have one :)
We build doc this wa
Michael Droettboom writes:
> Darren Dale wrote:
> > I am seeing some errors when I build the docs, including import errors
> > for nonexistent date_support and basic_units modules, and:
> I added the ability for explicitly setting sys.path so that modules in
> the same directory as an example w
Darren Dale wrote:
> I am seeing some errors when I build the docs, including import errors
> for nonexistent date_support and basic_units modules, and:
I added the ability for explicitly setting sys.path so that modules in
the same directory as an example would be importable. It looks likes
th
I am seeing some errors when I build the docs, including import errors for
nonexistent date_support and basic_units modules, and:
WARNING: /home/darren/src/matplotlib/doc/api/artist_api.rst:37: (WARNING/2)
error while formatting signature for matplotlib.patches.ArrowStyle.BracketB:
arg is not a Py
13 matches
Mail list logo
