I'd like to help the docstring formats of numpy, scipy. and matplotlib converge
on a high-quality standard (hence the cross-posting). However, before that can
happen all maintainers from all three packages need to agree on a format. In
the interest of speeding things along, I've taken the liberty o
> I don't remember why we did it this way originally, or if was you or I
> who did it, but if it is correct that the mapping is sometimes many
> codes point to one one glyph index, but there each glyph index must
> point to a single character code (the latter must be correct, right?)
> then reversi
On 2/14/07, Paul Barrett <[EMAIL PROTECTED]> wrote:
> My first reply:
>
> I suggest that this patch not be applied, since this was the intended
> behavior when the font manager was implemented. The standard behavior
> for indicating a missing character is to print a square. In addition,
> if a s
I'll be away on vacation fro Feb 16th-Feb23rd, and for the most part
out of email contact. Hold down the fort for me!
JDH
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll
On Thursday 15 February 2007 21:41, Nicolas Grilly wrote:
> On 2/14/07, Paul Barrett <[EMAIL PROTECTED]> wrote:
> > My first reply:
> >
> > I suggest that this patch not be applied, since this was the intended
> > behavior when the font manager was implemented. The standard behavior
> > for indic
On 2/15/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> On 2/15/07, Keir Mierle <[EMAIL PROTECTED]> wrote:
> > On the DocstringStandard page I have also put a completely re-done docstring
> > for the 'contour' function from matplotlib. I think it is far more readable
> > than the original [3]. JDH and
