Re: [matplotlib-devel] A small patch for sphinxext tools

2009-02-02 Thread John Hunter
On Mon, Feb 2, 2009 at 1:26 AM, Fernando Perez wrote: >> I believe mpl-data/matplotlibrc is not version-controled, but created >> when you run setup.py. >> Maybe you're trying to build the documentation from a new svn checkout >> but didn't build the library? > > Aha, that's it, thanks. I'd run

Re: [matplotlib-devel] A small patch for sphinxext tools

2009-02-01 Thread Fernando Perez
On Sun, Feb 1, 2009 at 9:22 PM, Jae-Joon Lee wrote: >> I'm a bit surprised to see this problem, since I imagine you guys >> build frequently. But my svn is indeed up to date and that file is >> just not there. I'm not sure which way you want the fix to go, so >> I'll leave that decision to you g

Re: [matplotlib-devel] A small patch for sphinxext tools

2009-02-01 Thread Jae-Joon Lee
> I'm a bit surprised to see this problem, since I imagine you guys > build frequently. But my svn is indeed up to date and that file is > just not there. I'm not sure which way you want the fix to go, so > I'll leave that decision to you guys. I believe mpl-data/matplotlibrc is not version-cont

Re: [matplotlib-devel] A small patch

2007-08-20 Thread Michael Droettboom
John Hunter wrote: > On 8/20/07, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >> UTF-8 is my default system encoding, so I didn't catch this. I just >> fixed the comment (the unicode character is unnecessary to get the point >> across and wasonly in there due to a cut-and-paste accident anyway

Re: [matplotlib-devel] A small patch

2007-08-20 Thread John Hunter
On 8/20/07, Michael Droettboom <[EMAIL PROTECTED]> wrote: > UTF-8 is my default system encoding, so I didn't catch this. I just > fixed the comment (the unicode character is unnecessary to get the point > across and wasonly in there due to a cut-and-paste accident anyway). > I have committed thi

Re: [matplotlib-devel] A small patch

2007-08-20 Thread Michael Droettboom
Fernando Perez wrote: > Hi all, > > here's a small patch for two little things I saw today: > > 1. The new mathtext has some unicode in it and on my system, python2.5 > was throwing a syntax error due to the lack of an encoding > declaration. I just stuck utf-8 though I don't know if that's real