Those of you who have been building the docs have probably seen the
inscrutable table warnings coming from sphinx. I just got a clue
where these are coming from. Look at the table formatting from this
ipython session (in case your email client doesn't handle monospace
right, the table border at the top is not indented right. Darren,
I'll let you take this -- somewhere in the dedent/kwarg table
interpolation, some spacing is getting botched.
JDH
class Arrow(Patch)
···
An arrow patch
>
> Method resolution order:
> Arrow
> Patch
> matplotlib.artist.Artist
> __builtin__.object
>
> Methods defined here:
>
> __init__(self, x, y, dx, dy, width=1.0, **kwargs)
> Draws an arrow, starting at (x,y), direction and length
> given by (dx,dy) the width of the arrow is scaled by width
>
> Valid kwargs are:
> =================
> Property Description
> ================= ==============================================
> alpha float
> animated [True | False]
> antialiased or aa [True | False]
> clip_box a matplotlib.transform.Bbox instance
> clip_on [True | False]
> edgecolor or ec any matplotlib color
> facecolor or fc any matplotlib color
> figure a matplotlib.figure.Figure instance
> fill [True | False]
> hatch unknown
> label any string
> linewidth or lw float
> lod [True | False]
> transform a matplotlib.transform transformation instance
> visible [True | False]
> zorder any number
> ================= ==============================================