matplotlib-devel Mailing List for matplotlib

Dave wrote:
> Whilst trying to plot a scatter plot with no facecolor I was able to reliably
> reproduce a segfault in mpl 0.91.2 - see below:
> 
> Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)]
> IPython 0.8.3.svn.r3001 -- An enhanced Interactive Python.
> 
> In [1]: import matplotlib
> In [2]: matplotlib.__version__
> Out[2]: '0.91.2'
> In [3]: from pylab import scatter, rand
> In [4]: scatter(rand(100),rand(100),c='')
> <--SegFault-->
> 
> That's probably not the right way to do it but it does work in 0.98.0.
> I'm unable to test on 0.91.3 at the moment.
On ubuntu hardy with 0.91.3 from the svn maintenance branch:
In [1]:import matplotlib
In [2]:matplotlib.__version__
Out[2]:'0.91.3'
In [3]:from pylab import scatter, rand
In [4]:scatter(rand(100), rand(100), c='')
Out[4]:<matplotlib.collections.RegularPolyCollection instance at 0x8edf04c>
In [5]:from pylab import show
In [6]:show()
Floating point exception
On the svn trunk it works.
Eric

On Jun 1, 2008, at 9:47 AM, Rob Hetland wrote:
>
> 2. I like the figure to the side (and agree that there should be 
> only one), but it seems that polar plots are more rarely used than 
> normal x-y plots. Perhaps an x-y plot (the histogram, for example) 
> would be better advertising.
I was the one who originally chose the polar plot. I admit, it was 
mainly for aesthetics. Here are a few reasons:
* I think a circular plot works better on the logo than a rectangular 
plot would.
* The polar plot is one of the more attractive plots in the examples.
* It's a plotting featuring that most plotting software wouldn't have 
so it seems to differentiate matplotlib from other plotting software.
Originally, it wasn't a big deal because there were other plots in the 
logo. Still, I'd be in favor of keeping the polar plot for aesthetic 
reasons.
Great, now I'm that guy who's arguing for looks over practicality. :(
-Tony

I'm not sure either, it was something simple like having problems 
building and John suggesting that I blow away the previous 
installation. But I indeed did eventually mail the doughnut.
Perry
On May 31, 2008, at 10:35 PM, John Hunter wrote:
> On Sat, May 31, 2008 at 3:19 PM, Darren Dale 
> <dar...@co...> wrote:
>
> Darren> I have to break here for the weekend, I'll be back monday 
> afternoon.
> Darren> Leave some for me! (although I'll owe doughnut to whoever 
> can fix the
> Darren> arrow docstring).
>
> John> I'll claim that doughnut.
>
> Darren> When was the last time you received one in the mail?
>
> Well, I remember the last time quite clearly, when Perry sent me a
> doughnut in the mail from Maryland to settle a "dollars-to doughnuts"
> bet. Unfortunately, I can't remember the subject of the bet right
> now (Perry?), though I kept the doughnut in my freezer, in the
> addressed envelope, for many months as a souvenir.
>
> JDH

On Sunday 01 June 2008 10:23:47 am Tony Yu wrote:
> On Jun 1, 2008, at 6:00 AM, Darren Dale wrote:
> > I was intending to write the list and ask if anyone was interested
> > in playing
> > with CSS to customize the looks of the new sphinx-based
> > documentation effort.
> > I'm really happy to hear that you're interested in helping out, Tony.
>
> Actually, I really like the default look of sphinx-based docs, but I
> wouldn't mind playing around with it. What did you have in mind?
Our front page has various sidebars that include announcements, links to the 
sourceforge download page, etc. I like the default look of sphinx-based html 
as well, but I also like the look of the moin-based scipy page.
> > For the moment, you can build the html documentation by running
> > "make.py html"
> > in the doc directory. The latex->pdf docs are experiencing growing
> > pains,
> > I'll work on it this morning.
>
> html built fine on my machine; it looks really nice. The pdf docs also
> built without problems. Nice work.
Yes, pdf is working again, I sorted out the issues that John and Fernando 
reported last night.
Darren

On Jun 1, 2008, at 6:00 AM, Darren Dale wrote:
> On Sunday 01 June 2008 12:53:48 am John Hunter wrote:
>>
>>
>> We're definitely interested. Try checking out the htdocs svn
>> repository.
Hmm, the README file says I need all the backends working. I don't 
think I want to try that on my Mac. I'll try it out with a linux 
machine I have in lab.
>> Admittedly we do things in our own special way (eg the
>> YAPTU template engine), but if we could improve the look-and-feel 
>> that
>> would be great. None of us have any special powers in the
>> website-design department. Even better, as part of our new trunk
>> documentation effort, we have moved to a sphinx based documentation
>> system (in the doc subdir of svn trunk). If you could figure out a
>> way to hook custom CSSandr mpl figures/screenshots or any other 
>> snazzy
>> features into the base sphinx build system, that would be a big help
>> since we hope to jettison the somewhat anachronistic website build
>> system n the not-too-distant-future.
>
> I was intending to write the list and ask if anyone was interested 
> in playing
> with CSS to customize the looks of the new sphinx-based 
> documentation effort.
> I'm really happy to hear that you're interested in helping out, Tony.
Actually, I really like the default look of sphinx-based docs, but I 
wouldn't mind playing around with it. What did you have in mind?
> For the moment, you can build the html documentation by running 
> "make.py html"
> in the doc directory. The latex->pdf docs are experiencing growing 
> pains,
> I'll work on it this morning.
html built fine on my machine; it looks really nice. The pdf docs also 
built without problems. Nice work.
-Tony

Whilst trying to plot a scatter plot with no facecolor I was able to reliably
reproduce a segfault in mpl 0.91.2 - see below:
Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) [MSC v.1310 32 bit (Intel)]
IPython 0.8.3.svn.r3001 -- An enhanced Interactive Python.
In [1]: import matplotlib
In [2]: matplotlib.__version__
Out[2]: '0.91.2'
In [3]: from pylab import scatter, rand
In [4]: scatter(rand(100),rand(100),c='')
<--SegFault-->
That's probably not the right way to do it but it does work in 0.98.0.
I'm unable to test on 0.91.3 at the moment.
NB: The work-around (correct way?) to get the same result in 0.91.2 is:
scatter(rand(100),rand(100),c='w',alpha=0)

On Jun 1, 2008, at 4:30 AM, John Hunter wrote:
> Let me know what you think...
Generally, I like the logo, and think it is a *huge* improvement on 
the old one.
Two suggestions:
1. The original new logo was done in a Helvetica medium font, which is 
much nicer for this type of logo. (See the Helvetica movie, and 
become a true believer...).
2. I like the figure to the side (and agree that there should be only 
one), but it seems that polar plots are more rarely used than normal x- 
y plots. Perhaps an x-y plot (the histogram, for example) would be 
better advertising.
-Rob
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

On Saturday 31 May 2008 10:45:34 pm John Hunter wrote:
> On Sat, May 31, 2008 at 7:50 PM, Darren Dale <dar...@co...> 
wrote:
> > I just realized, though, that I should probably be striving to conform
> > with the standard that the numpy and scipy folks put together:
> > http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines and
> > http://svn.scipy.org/svn/numpy/trunk/numpy/doc/example.py . Any comments?
> > I think I have been relying too heavily on tables for the keyword
> > arguments.
>
> I think that following their guidelines is a good idea for the most
> part, but we needn't adhere to them religiously. For one thing,
> matplotlib uses *a lot* more keyword args than either numpy or scipy,
> and what works for them for kwargs may not be best for us. In
> particular, if we use the format they suggest, I'm afraid our
> docstrings will simply take up too much space. For example, see
> http://mentat.za.net/numpy/refguide/functions.xhtml#all-a-axis-none-out-non
>e . What if we formatted all the Line2d kwargs that way? It seems a bit
> bloated in terms of vertical space for the number of kwargs we need to
> handle, and so a ReST table may in fact be better.
I agree. We should default to parameter lists, but longer lists of kwargs will 
be formatted as tables.
There are also some features in the numpy template (like the use of sections) 
that cause sphinx to fail. I wonder how the webpage you referenced was 
generated?
> We want our documentation to be mostly consistent to aid the folks
> trying to put together bits and pieces of documentation from several
> projects to write in-house docs (which incorporate local docs) or
> books, but I'm not sure we need our doc formatting to be entirely
> consistent at the API level.
Right, we shouldn't worry about rigorously adhering to a standard, but their 
template seems like a good guideline to keep in mind.

On Saturday 31 May 2008 11:44:34 pm Darren Dale wrote:
> On Saturday 31 May 2008 10:19:47 pm John Hunter wrote:
> > On Sat, May 31, 2008 at 9:01 PM, Fernando Perez <fpe...@gm...>
>
> wrote:
> > > I don't know if you are so in the middle of things that you'd rather
> > > not get bug reports on this for a while. If that's the case I'll wait
> > > until the dust settles a bit.
> >
> > Well, we definitely want our docs to build so we're happy to get the
> > feedback -- sometimes it's a simple matter of a dev forgetting to
> > commit a critical file. I am getting this error too. It appears to
> > be a bug in the pyplot docstrings -- Darren, perhaps you haven't
> > committed all you recent changes?
>
> All my changes had already been committed. I had only been creating html
> (./make.py html) and it looks like some of the tables I have been creating
> dont agree with latex. I'll fix it tomorrow, but in the meantime, please
> just make html.
Alright, I've tracked down the source of these two errors. Sphinx can not 
create tables in latex that have cells spanning multiple rows or multiple 
columns. Maybe it is a limitation of latex, I'm not sure, I don't have my 
latex books handy. But it looks like tables with row- or column-spanning 
cells are henceforth verboten.
I've updated pyplot_api.rst in svn so it is basically empty and will not cause 
anyone trouble while I fix the broken tables.
> > But if I remove entirely the pyplot
> > api doc which is causing this problem, I get lots of other errors
> > along the lines of those shown below. Is this a latex or sphinxext
> > config error?
> >
> > [8 <./pyplot_formatstr.png> <./pyplot_three.png>] [9] [10]
> > <pyplot_two_subplots.png, id=368, 578.16pt x 433.62pt>
> > <use pyplot_two_subplots.png> <use pyplot_two_subplots.png> [11
> > <./pyplot_two_s ubplots.png>] <pyplot_text.png, id=375, 578.16pt x
> > 433.62pt>
> > <use pyplot_text.png> <use pyplot_text.png> [12 <./pyplot_text.png>] [13]
> > [14]
> > Chapter 2.
> > [15] [16]
> > ! Undefined control sequence.
> > <recently read> \mathbb
> >
> > l.954 \end{tabulary}
I tracked this down by checking the contents of the generated 
build/latex/Matplotlib.tex, line 954. It is from the following code from 
mathtext.rst:
> When using the STIX fonts, you also have the choice of:
>
> ================ =================================
> Command Result
> ================ =================================
> ``\mathbb`` :math:`\mathbb{Blackboard}`
> ``\mathcircled`` :math:`\mathcircled{Circled}`
> ``\mathfrak`` :math:`\mathfrak{Fraktur}`
> ``\mathsf`` :math:`\mathsf{sans-serif}`
> ================ =================================
I'm not sure this is being properly rendered in the HTML output for me, 
either. Mike, are you able to compile this into a pdf on your machine, and if 
so, would you tell us how to configure STIX support? I commented this block 
out in svn for now.
Cheers,
Darren

On Sunday 01 June 2008 12:53:48 am John Hunter wrote:
> On Sat, May 31, 2008 at 11:27 PM, Tony Yu <ts...@gm...> wrote:
> > I like the new color scheme on the website. Since you asked for
> > criticism, though, I'm not a fan of the blue "matplotlib" in the logo (on
> > the website, the attached logo is actually different). I think black or a
> > dark gray looks better (color=[0.2, 0.2, 0.2]). Or, if you prefer blue,
> > something less like the default hyperlink color (e.g. color=[.1,.1,.5]).
> > My 2 cents.
>
> I agree -- I had already reverted to black (hit refresh). But if you
> think some other shade of dark gray or blue/gray is better let me
> know.
Speaking as a recovering graphical design major and insensitive curmudgeon... 
it looks great, nice work! 
I do have two comments though: the 90 and 270 ticklabels are cut off, and I 
think the plot would look a little cleaner if the ticklabel pad were 
increased so the radial ticks were a little further from the axes.
> > BTW, I noticed that website is a little old (pure HTML, no CSS). If
> > you're ever interested in redesigning the website (nothing fancy, mainly
> > just moving to CSS), I'd be happy to help out.
>
> We're definitely interested. Try checking out the htdocs svn
> repository. Admittedly we do things in our own special way (eg the
> YAPTU template engine), but if we could improve the look-and-feel that
> would be great. None of us have any special powers in the
> website-design department. Even better, as part of our new trunk
> documentation effort, we have moved to a sphinx based documentation
> system (in the doc subdir of svn trunk). If you could figure out a
> way to hook custom CSSandr mpl figures/screenshots or any other snazzy
> features into the base sphinx build system, that would be a big help
> since we hope to jettison the somewhat anachronistic website build
> system n the not-too-distant-future.
I was intending to write the list and ask if anyone was interested in playing 
with CSS to customize the looks of the new sphinx-based documentation effort. 
I'm really happy to hear that you're interested in helping out, Tony.
I second Johns suggestion of having a look at the doc/ directory in the trunk, 
and getting familiar with sphinx. I think most of the content on the website 
is going to find a new home in the sphinx-based docs, and it would be nice if 
the front page, sidebars, etc could also be generated with sphinx.
For the moment, you can build the html documentation by running "make.py html" 
in the doc directory. The latex->pdf docs are experiencing growing pains, 
I'll work on it this morning.
Darren

>
> Hi Pierre,
>
> On Friday 30 May 2008 5:21:01 pm Pierre Raybaut wrote:
> 
>> > First, I would like to congratulate you for your work on Matplotlib. I
>> > am using Matplotlib widgets in all my current projects, embedded in PyQt
>> > graphical user interfaces.
>> >
>> > As you may know, PyQt 4.4.2 has been released a few days ago.
>> > And I found out a performance bug when embedding a Matplotlib 0.91.2
>> > canvas in a PyQt 4.4.2 object: the pan/zoom feature is very slow (with
>> > PyQt 4.3.3, and the exact same scripts, pan/zoom is real-time).
>> 
>
> Would it be possible to post some benchmarks, something a little more 
> concrete, like specifically what calls are taking the most time, and how they 
> compare for the different versions of PyQt?
> 
Yes of course, I will send the requested informations as soon as I can.
> 
>> > I am posting this in PyQt mailing-list too, but I guess that you could
>> > have more ideas on that matter (Matplotlib widgets may not be used very
>> > often in PyQt).
>> 
>
> Please don't do that. Its not fair to the people who volunteer their time on 
> open source projects to try to draw so many people into the problem before 
> the problem is understood.
Wow... I did not expect this reaction! :) The only reason that I posted 
on the two mailing-list was to be sure to inform everyone who was 
potentially interested by the topic. Otherwise, if I was really trying 
outrageously to draw many people into the problem, I wouldn't have 
mentioned the post on the other mailing-list, would I? Thanks for the 
warm welcome though ;)
Regards,
Pierre Raybaut

On Sat, May 31, 2008 at 11:27 PM, Tony Yu <ts...@gm...> wrote:
> I like the new color scheme on the website. Since you asked for criticism,
> though, I'm not a fan of the blue "matplotlib" in the logo (on the website,
> the attached logo is actually different). I think black or a dark gray looks
> better (color=[0.2, 0.2, 0.2]). Or, if you prefer blue, something less like
> the default hyperlink color (e.g. color=[.1,.1,.5]). My 2 cents.
I agree -- I had already reverted to black (hit refresh). But if you
think some other shade of dark gray or blue/gray is better let me
know.
> BTW, I noticed that website is a little old (pure HTML, no CSS). If you're
> ever interested in redesigning the website (nothing fancy, mainly just
> moving to CSS), I'd be happy to help out.
We're definitely interested. Try checking out the htdocs svn
repository. Admittedly we do things in our own special way (eg the
YAPTU template engine), but if we could improve the look-and-feel that
would be great. None of us have any special powers in the
website-design department. Even better, as part of our new trunk
documentation effort, we have moved to a sphinx based documentation
system (in the doc subdir of svn trunk). If you could figure out a
way to hook custom CSSandr mpl figures/screenshots or any other snazzy
features into the base sphinx build system, that would be a big help
since we hope to jettison the somewhat anachronistic website build
system n the not-too-distant-future.
JDH

On May 31, 2008, at 10:30 PM, John Hunter wrote:
>
> And I made several changes -- mainly to simplify the logo. My wife
> thought it looked busy, and she has better taste than I do, so I
> stripped it down a bunch and added the many small subplots as a
> sidebar on the right.
I agree, the stripped down logo looks much better.
> Let me know what you think and don't be shy
> about being critical despite Darren's kind sensitivities. I don't
> take pride in my graphic design abilities and so will happily make
> changes
>
> See http://matplotlib.sf.net for the new logo(s) and the attached for
> the stripped down script.
I like the new color scheme on the website. Since you asked for 
criticism, though, I'm not a fan of the blue "matplotlib" in the logo 
(on the website, the attached logo is actually different). I think 
black or a dark gray looks better (color=[0.2, 0.2, 0.2]). Or, if you 
prefer blue, something less like the default hyperlink color (e.g. 
color=[.1,.1,.5]). My 2 cents.
BTW, I noticed that website is a little old (pure HTML, no CSS). If 
you're ever interested in redesigning the website (nothing fancy, 
mainly just moving to CSS), I'd be happy to help out.
-Tony
> JDH
> <logo2.png>

On Saturday 31 May 2008 10:19:47 pm John Hunter wrote:
> On Sat, May 31, 2008 at 9:01 PM, Fernando Perez <fpe...@gm...> 
wrote:
> > I don't know if you are so in the middle of things that you'd rather
> > not get bug reports on this for a while. If that's the case I'll wait
> > until the dust settles a bit.
>
> Well, we definitely want our docs to build so we're happy to get the
> feedback -- sometimes it's a simple matter of a dev forgetting to
> commit a critical file. I am getting this error too. It appears to
> be a bug in the pyplot docstrings -- Darren, perhaps you haven't
> committed all you recent changes? 
All my changes had already been committed. I had only been creating html 
(./make.py html) and it looks like some of the tables I have been creating 
dont agree with latex. I'll fix it tomorrow, but in the meantime, please just 
make html. 
> But if I remove entirely the pyplot 
> api doc which is causing this problem, I get lots of other errors
> along the lines of those shown below. Is this a latex or sphinxext
> config error?
Not sure, I'll look into it on Sunday as well.
Cheers,
Darren

On Sat, May 31, 2008 at 7:50 PM, Darren Dale <dar...@co...> wrote:
> I just realized, though, that I should probably be striving to conform with
> the standard that the numpy and scipy folks put together:
> http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines and
> http://svn.scipy.org/svn/numpy/trunk/numpy/doc/example.py . Any comments? I
> think I have been relying too heavily on tables for the keyword arguments.
I think that following their guidelines is a good idea for the most
part, but we needn't adhere to them religiously. For one thing,
matplotlib uses *a lot* more keyword args than either numpy or scipy,
and what works for them for kwargs may not be best for us. In
particular, if we use the format they suggest, I'm afraid our
docstrings will simply take up too much space. For example, see
http://mentat.za.net/numpy/refguide/functions.xhtml#all-a-axis-none-out-none
. What if we formatted all the Line2d kwargs that way? It seems a
bit bloated in terms of vertical space for the number of kwargs we
need to handle, and so a ReST table may in fact be better.
We want our documentation to be mostly consistent to aid the folks
trying to put together bits and pieces of documentation from several
projects to write in-house docs (which incorporate local docs) or
books, but I'm not sure we need our doc formatting to be entirely
consistent at the API level.
JDH

On Sat, May 31, 2008 at 3:19 PM, Darren Dale <dar...@co...> wrote:
 Darren> I have to break here for the weekend, I'll be back monday afternoon.
 Darren> Leave some for me! (although I'll owe doughnut to whoever can fix the
 Darren> arrow docstring).
 John> I'll claim that doughnut.
 Darren> When was the last time you received one in the mail?
Well, I remember the last time quite clearly, when Perry sent me a
doughnut in the mail from Maryland to settle a "dollars-to doughnuts"
bet. Unfortunately, I can't remember the subject of the bet right
now (Perry?), though I kept the doughnut in my freezer, in the
addressed envelope, for many months as a souvenir.
JDH

On Mon, May 26, 2008 at 1:50 PM, Tony Yu <ts...@gm...> wrote:
> I played around with the script, but in the process I ended up rewriting it
> a bunch. I'm sure I've violated come coding guidelines along the way; my
> apologies.
And I made several changes -- mainly to simplify the logo. My wife
thought it looked busy, and she has better taste than I do, so I
stripped it down a bunch and added the many small subplots as a
sidebar on the right. Let me know what you think and don't be shy
about being critical despite Darren's kind sensitivities. I don't
take pride in my graphic design abilities and so will happily make
changes
See http://matplotlib.sf.net for the new logo(s) and the attached for
the stripped down script.
JDH

On Sat, May 31, 2008 at 9:01 PM, Fernando Perez <fpe...@gm...> wrote:
> I don't know if you are so in the middle of things that you'd rather
> not get bug reports on this for a while. If that's the case I'll wait
> until the dust settles a bit.
Well, we definitely want our docs to build so we're happy to get the
feedback -- sometimes it's a simple matter of a dev forgetting to
commit a critical file. I am getting this error too. It appears to
be a bug in the pyplot docstrings -- Darren, perhaps you haven't
committed all you recent changes? But if I remove entirely the pyplot
api doc which is causing this problem, I get lots of other errors
along the lines of those shown below. Is this a latex or sphinxext
config error?
[8 <./pyplot_formatstr.png> <./pyplot_three.png>] [9] [10]
<pyplot_two_subplots.png, id=368, 578.16pt x 433.62pt>
<use pyplot_two_subplots.png> <use pyplot_two_subplots.png> [11 <./pyplot_two_s
ubplots.png>] <pyplot_text.png, id=375, 578.16pt x 433.62pt>
<use pyplot_text.png> <use pyplot_text.png> [12 <./pyplot_text.png>] [13]
[14]
Chapter 2.
[15] [16]
! Undefined control sequence.
<recently read> \mathbb
l.954 \end{tabulary}
?
! Undefined control sequence.
<recently read> \mathcircled
l.954 \end{tabulary}
...and lots more like this....
JDH

Hey folks,
I'm super excited about this, so I decided to give it a quick test run
with current trunk SVN. Running ./make.py in the doc/ directory
worked for a while, and then stalled at:
Sphinx v0.3, building latex
trying to load pickled env... done
building [latex]: all documents
updating environment: 0 added, 0 changed, 0 removed
processing Matplotlib.tex... index users/index users/pyplot_tutorial
users/mathtext users/navigation_toolbar users/customizing
users/artists users/event_handling faq/index faq/installing_faq
faq/troubleshooting_faq faq/howto_faq devel/index devel/coding_guide
devel/documenting_mpl devel/add_new_projection api/index
api/artist_api api/pyplot_api
resolving references...
writing... Exception occurred:
 File "/home/fperez/usr/local/lib/python2.5/site-packages/Sphinx-0.3-py2.5.egg/sphinx/latexwriter.py",
line 479, in visit_entry
 raise NotImplementedError('Column or row spanning cells are '
NotImplementedError: Column or row spanning cells are not implemented.
The full traceback has been saved in /tmp/sphinx-err-l_Oadi.log, if
you want to report the issue to the author.
Please also report this if it was a user error, so that a better error
message can be provided next time.
Send reports to sph...@go.... Thanks!
This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6)
 %&-line parsing enabled.
entering extended mode
! I can't find file `Matplotlib.tex'.
<*> Matplotlib.tex
Please type another input file name:
I don't know if you are so in the middle of things that you'd rather
not get bug reports on this for a while. If that's the case I'll wait
until the dust settles a bit.
In any case, many thanks for pushing this doc effort forward! The
overall usability of the combined tools, in a few months, is going to
really be massively improved thanks to all this common focus on
sphinx-based docs.
Cheers,
f

On Saturday 31 May 2008 4:14:39 pm Darren Dale wrote:
> On Saturday 31 May 2008 12:36:11 pm John Hunter wrote:
> > On Sat, May 31, 2008 at 9:19 AM, Darren Dale <dar...@co...>
>
> wrote:
> > > I'll be working on converting docstrings to rest this weekend. Should
> > > any of this be done on the branch? Or should we just focus on the
> > > trunk?
> >
> > As far as I am concerned, the documentation effort is for the trunk.
>
> I would really prefer to concentrate on the trunk. There's enough work as
> it is.
I made some pretty good progress today. I found the source of that error that 
was causing sphinx to fail without a helpfull message, there was a ********* 
in the contour documentation. pyplot_api is about halfway converted, there 
are only 60 warnings reported by sphinx for pyplot.
I just realized, though, that I should probably be striving to conform with 
the standard that the numpy and scipy folks put together: 
http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines and 
http://svn.scipy.org/svn/numpy/trunk/numpy/doc/example.py . Any comments? I 
think I have been relying too heavily on tables for the keyword arguments.
Darren