matplotlib-devel Mailing List for matplotlib (Page 9)

Manuel Metz wrote:
>    x = np.asarray(x).astype(np.float32)
>    x = np.zeros( x, np.float_ )
>    x = np.ones((col,), float)
> 
> Is there a preferred one to stick to ?!

Michael Droettboom wrote:
>   x = np.asarray(x, np.float_)

I'd vote for:

x = np.asarray(x, np.float)

It ends up resulting in the same thing, but I prefer not to have 
magic-looking underscores in names. There is a slight difference:

np.float is the python float type, whereas np.float_ is the numpy 
float64 type. I suppose in some future 128 bit OS, the python float may 
be something else. I like saying: "make this the standard python float 
type", rather than "make this a 64 bit float", even though it means the 
same thing in all versions of python I know of.

This, or course, only when casting really is required, as John H. 
pointed out.

-Chris



-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

John Hunter wrote:
> On Thu, Jun 12, 2008 at 7:47 AM, Michael Droettboom <md...@st...> wrote:
>
>   
>> Barring that, I suppose we'll have to a) drop the symbol table or b) use
>> mathtext to generate the math for LaTeX (there's something very patricidal
>> about that... ;).  b) may be a little bit of work to do well, since we don't
>> currently have a way to get a nice tightly-bound PDF of a math expression,
>> and embedding PNGs will look bad.
>>     
>
> Now that we have this bug fixed, we don't need to consider any of
> these alternatives.  But not having correct bounding boxes for the PDF
> mathtext expressions is a problem worth fixing.  What is the status of
> this: tried and impossible, tried but haven't figured it out, haven't
> tried, etc?   Jouni, is this something you could take another look at?
>
>   
I don't think this is a PDF problem necessarily.  I only meant that 
there is no mathtext2pdf (equivalent to mathtext2png).  It would need to 
render the math to determine its bounding box (doable now), and then 
create a new figure of the correct size to render to.  Not difficult, 
but potentially finicky.

We still have the problem of a lack of baseline output from mathtext 
(but that exists regardless of backend).
> In a perfect world, we would have mathtext format our math using the
> pdf backend for the mathtext expressions in the spirit of "what you
> see is what you get", but I don't consider this to be a high priority
> now that users can build some docs (html) w/o a latex install.  Since
> building PDF requires latex anyhow, using our own mathtext is only a
> marginal benefit.
>   
Right -- that's how I see it, too.  Plus having LaTeX render the math 
means that everything looks like it belongs (the right sizes, spacing etc.)

Cheers,
Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

right, I agree : I tried because I did not know for sure whether it 
would work or not, and because that was post-lunch time :) .... Looks 
like bleeding edge sphinx is not required seemingly!
Johann

John Hunter wrote:
> On Thu, Jun 12, 2008 at 9:52 AM, Michael Droettboom <md...@st...> wrote:
>
>   
>> Eventually, we'll have to track down and document which versions of sphinx,
>> docutils and pygments work to build the matplotlib documentation.  There's a
>> lot of moving parts here...
>>     
>
> Documenting is good, and I don't mind requiring updated versions of
> everything, or even svn for now,  to get the docs to build.  I
> consider these to be development/bleeding edge only, and don't want to
> announce them to the user community until we have a reasonably
> complete set of docs.   But having a documented combination that works
> in the dev guide would be useful.
>   

On Thu, Jun 12, 2008 at 7:47 AM, Michael Droettboom <md...@st...> wrote:

> Barring that, I suppose we'll have to a) drop the symbol table or b) use
> mathtext to generate the math for LaTeX (there's something very patricidal
> about that... ;).  b) may be a little bit of work to do well, since we don't
> currently have a way to get a nice tightly-bound PDF of a math expression,
> and embedding PNGs will look bad.

Now that we have this bug fixed, we don't need to consider any of
these alternatives.  But not having correct bounding boxes for the PDF
mathtext expressions is a problem worth fixing.  What is the status of
this: tried and impossible, tried but haven't figured it out, haven't
tried, etc?   Jouni, is this something you could take another look at?

In a perfect world, we would have mathtext format our math using the
pdf backend for the mathtext expressions in the spirit of "what you
see is what you get", but I don't consider this to be a high priority
now that users can build some docs (html) w/o a latex install.  Since
building PDF requires latex anyhow, using our own mathtext is only a
marginal benefit.

JDH

On Thu, Jun 12, 2008 at 9:52 AM, Michael Droettboom <md...@st...> wrote:

> Eventually, we'll have to track down and document which versions of sphinx,
> docutils and pygments work to build the matplotlib documentation.  There's a
> lot of moving parts here...

Documenting is good, and I don't mind requiring updated versions of
everything, or even svn for now,  to get the docs to build.  I
consider these to be development/bleeding edge only, and don't want to
announce them to the user community until we have a reasonably
complete set of docs.   But having a documented combination that works
in the dev guide would be useful.

Johann Cohen-Tanugi wrote:
> Personnally I get:
> build/latex/Matplotlib.tex:$\Cap$ \code{\textbackslash{}Cap}
That's a usage, not a definition.  The problem is related to duplicate 
definitions of \Cap.
> but I have sphinx 0.3 which is the version easy_installed on my FC8 
> box. Actually I wonder how much trouble this 0.3 version is a promise 
> of.....
Eventually, we'll have to track down and document which versions of 
sphinx, docutils and pygments work to build the matplotlib 
documentation.  There's a lot of moving parts here...

Cheers,
Mike
> Johann
>
>
> Michael Droettboom wrote:
>> Interestingly, sphinx *doesn't* define it for me.  One of the first 
>> things I did was "grep Cap" on the latex build directory.
>> I updated sphinx from SVN pretty recently... I wonder if that has 
>> anything to do with it.  If that doesn't fix it, yes, that sounds 
>> like something to report.
>>
>> Cheers,
>> Mike
>>
>> John Hunter wrote:
>>  
>>> On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <jd...@gm...> wrote:
>>>
>>>      
>>>> ! LaTeX Error: Command \Cap already defined.
>>>>               Or name \end... illegal, see p.192 of the manual.
>>>>           
>>> This may have been obvious to all of you,but I am just discovering it.
>>>  The problem is that *sphinx* is defining \Cap as a color, and this is
>>> clashing with the ams name.  From Matplotlib.tex::
>>>
>>>     \newcommand\Car[1]{\textcolor[rgb]{0.73,0.38,0.84}{#1}}
>>>     \newcommand\Caq[1]{\textcolor[rgb]{0.38,0.68,0.84}{#1}}
>>>     \newcommand\Cap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>>>     \newcommand\Caw[1]{\textcolor[rgb]{0.13,0.50,0.31}{#1}}
>>>
>>> but I haven't yet found the file which is adding this.  This looks
>>> like a docutils/sphinx bug.
>>>
>>> JDH
>>> JDH
>>>       
>>
>>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Thu, Jun 12, 2008 at 9:25 AM, Michael Droettboom <md...@st...> wrote:
> Interestingly, sphinx *doesn't* define it for me.  One of the first things I
> did was "grep Cap" on the latex build directory.
> I updated sphinx from SVN pretty recently... I wonder if that has anything
> to do with it.  If that doesn't fix it, yes, that sounds like something to
> report.

The sphinx highlighting module uses
pygments.formatters.latex.LatexFormatter which cycles through letters
using a command prefix which defaults to 'C'

    def _create_stylecmds(self):
        t2c = self.ttype2cmd = {Token: ''}
        c2d = self.cmd2def = {}
        cp = self.commandprefix

        letters = 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'
        first = iter(letters)
        second = iter(letters)
        firstl = first.next()


In sphinx.highlighting, I can override this default with commandprefix='PYGC'
and get the build to work,


class PygmentsBridge(object):
    def __init__(self, dest='html', stylename='sphinx'):
        self.dest = dest
        if not pygments:
            return
        if stylename == 'sphinx':
            style = SphinxStyle
        elif '.' in stylename:
            module, stylename = stylename.rsplit('.', 1)
            style = getattr(__import__(module, None, None, ['']), stylename)
        else:
            style = get_style_by_name(stylename)
        self.hfmter = {False: HtmlFormatter(style=style),
                       True: HtmlFormatter(style=style, linenos=True)}
        self.lfmter = {False: LatexFormatter(style=style, commandprefix='PYGC'),
                       True: LatexFormatter(style=style, linenos=True,
commandprefix='PYGC')}

It appears to be Pygments (source code highlighter) that produces these 
lines.  I have Pygments 0.10 which "works for me" (TM).

pygments/formatters/latex.py
158:                cmndef = r'\textcolor[rgb]{%s}{%s}' % (

Cheers,
Mike

Michael Droettboom wrote:
> Interestingly, sphinx *doesn't* define it for me.  One of the first 
> things I did was "grep Cap" on the latex build directory.
> I updated sphinx from SVN pretty recently... I wonder if that has 
> anything to do with it.  If that doesn't fix it, yes, that sounds like 
> something to report.
>
> Cheers,
> Mike
>
> John Hunter wrote:
>> On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <jd...@gm...> wrote:
>>
>>  
>>> ! LaTeX Error: Command \Cap already defined.
>>>               Or name \end... illegal, see p.192 of the manual.
>>>     
>>
>> This may have been obvious to all of you,but I am just discovering it.
>>  The problem is that *sphinx* is defining \Cap as a color, and this is
>> clashing with the ams name.  From Matplotlib.tex::
>>
>>     \newcommand\Car[1]{\textcolor[rgb]{0.73,0.38,0.84}{#1}}
>>     \newcommand\Caq[1]{\textcolor[rgb]{0.38,0.68,0.84}{#1}}
>>     \newcommand\Cap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>>     \newcommand\Caw[1]{\textcolor[rgb]{0.13,0.50,0.31}{#1}}
>>
>> but I haven't yet found the file which is adding this.  This looks
>> like a docutils/sphinx bug.
>>
>> JDH
>> JDH
>>   
>

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Personnally I get:
build/latex/Matplotlib.tex:$\Cap$ \code{\textbackslash{}Cap}
but I have sphinx 0.3 which is the version easy_installed on my FC8 box. 
Actually I wonder how much trouble this 0.3 version is a promise of.....
Johann


Michael Droettboom wrote:
> Interestingly, sphinx *doesn't* define it for me.  One of the first 
> things I did was "grep Cap" on the latex build directory. 
>
> I updated sphinx from SVN pretty recently... I wonder if that has 
> anything to do with it.  If that doesn't fix it, yes, that sounds like 
> something to report.
>
> Cheers,
> Mike
>
> John Hunter wrote:
>   
>> On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <jd...@gm...> wrote:
>>
>>   
>>     
>>> ! LaTeX Error: Command \Cap already defined.
>>>               Or name \end... illegal, see p.192 of the manual.
>>>     
>>>       
>> This may have been obvious to all of you,but I am just discovering it.
>>  The problem is that *sphinx* is defining \Cap as a color, and this is
>> clashing with the ams name.  From Matplotlib.tex::
>>
>>     \newcommand\Car[1]{\textcolor[rgb]{0.73,0.38,0.84}{#1}}
>>     \newcommand\Caq[1]{\textcolor[rgb]{0.38,0.68,0.84}{#1}}
>>     \newcommand\Cap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>>     \newcommand\Caw[1]{\textcolor[rgb]{0.13,0.50,0.31}{#1}}
>>
>> but I haven't yet found the file which is adding this.  This looks
>> like a docutils/sphinx bug.
>>
>> JDH
>> JDH
>>   
>>     
>
>   

Interestingly, sphinx *doesn't* define it for me.  One of the first 
things I did was "grep Cap" on the latex build directory. 

I updated sphinx from SVN pretty recently... I wonder if that has 
anything to do with it.  If that doesn't fix it, yes, that sounds like 
something to report.

Cheers,
Mike

John Hunter wrote:
> On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <jd...@gm...> wrote:
>
>   
>> ! LaTeX Error: Command \Cap already defined.
>>               Or name \end... illegal, see p.192 of the manual.
>>     
>
> This may have been obvious to all of you,but I am just discovering it.
>  The problem is that *sphinx* is defining \Cap as a color, and this is
> clashing with the ams name.  From Matplotlib.tex::
>
>     \newcommand\Car[1]{\textcolor[rgb]{0.73,0.38,0.84}{#1}}
>     \newcommand\Caq[1]{\textcolor[rgb]{0.38,0.68,0.84}{#1}}
>     \newcommand\Cap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>     \newcommand\Caw[1]{\textcolor[rgb]{0.13,0.50,0.31}{#1}}
>
> but I haven't yet found the file which is adding this.  This looks
> like a docutils/sphinx bug.
>
> JDH
> JDH
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Wed, Jun 11, 2008 at 4:00 PM, John Hunter <jd...@gm...> wrote:

> ! LaTeX Error: Command \Cap already defined.
>               Or name \end... illegal, see p.192 of the manual.

This may have been obvious to all of you,but I am just discovering it.
 The problem is that *sphinx* is defining \Cap as a color, and this is
clashing with the ams name.  From Matplotlib.tex::

    \newcommand\Car[1]{\textcolor[rgb]{0.73,0.38,0.84}{#1}}
    \newcommand\Caq[1]{\textcolor[rgb]{0.38,0.68,0.84}{#1}}
    \newcommand\Cap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
    \newcommand\Caw[1]{\textcolor[rgb]{0.13,0.50,0.31}{#1}}

but I haven't yet found the file which is adding this.  This looks
like a docutils/sphinx bug.

JDH
JDH

That's my bad -- I added even more symbols to the symbol table without 
updating the preamble.  I should have a fix shortly.

Cheers,
Mike

Johann Cohen-Tanugi wrote:
> thanks Darren,
> I just tried and it completed to a readable pdf files, though after a 
> couple of error message of this type :
> ! Undefined control sequence.
> <recently read> \Equiv
>                      l.2379 \end{tabulary}
>                    ? x
>
> escaping with 'x' everythime lead to completion....
> best,
> Johann
>
> Darren Dale wrote:
>> On Thursday 12 June 2008 08:08:41 am Michael Droettboom wrote:
>>  
>>> It looks as if the docs can't be built if text.usetex is "True", first
>>> because of needing Unicode (which also requires setting
>>> text.latex.unicode to True), and second because the dollar_ticks.py 
>>> demo
>>> doesn't escape '$'.
>>>
>>> I suppose we should hardcode text.usetex to "False" when building the
>>> documentation figures.  Better yet, it might be a good idea to 
>>> provide a
>>> "documentation-only" matplotlibrc (or use only the defaults) so that we
>>> can always get consistent results when building the documentation.
>>>     
>>
>> I think an empty matplotlibrc file is the right way to go. I added it 
>> in svn.
>>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Thu, Jun 12, 2008 at 8:20 AM, Michael Droettboom <md...@st...> wrote:

>> Both `np.float_` and the Python `float` are interpreted as
>> `np.float64`.  The only time you really need something other than
>> `float` is if you require a width other than 64 (like in the first
>> line you showed).

One rule to remember is don't cast user input to float unless there is
no alternative.
Consider that input might be dates::

  In [9]: import numpy as np

  In [10]: import datetime

  In [11]: x = [datetime.date(2007,1,1), datetime.date(2008,1,1),,
datetime.date(2009,1,1)]

  In [12]: xa = np.asarray(x)

  In [13]: print xa[1:]-xa[:-1]
  [365 days, 0:00:00 366 days, 0:00:00]

So many operations may be valid w/o an explicit cast to floats.  Since
we are supporting custom user types, albeit imperfectly, this is
something to bear in mind.  In particular, I find the native datetime
plotting invaluable, and the JPL uses custom unit types extensively.
All of this happens via the unit converter infrastructure in
matplotlib.units and there is machinery there to do the case to
floats.  Last time this came up, Eric I think requested a document
specifying what operations can be assumed on input sequences.  I
haven't done that yet, but I am mentioning this again here as a
reminder.  When I have some time I'll try to get a document together
as well as some test code to test custom input types.

JDH

On Thu, Jun 12, 2008 at 7:56 AM, Stéfan van der Walt <st...@su...> wrote:

> linestyle 'x' ---> legend  '   x   '
> linestyle '-x' ---> legend '---x---'
>
> Has this been considered before?  If not, I'll write a patch.

I think this is just something that has been overlooked.  The legend
code is quite old, so don't be surprised if it looks a little crusty
in there, as it was one of the early features, and it has been updated
piecemeal with new features.  A patch would be great.

JDH

thanks Darren,
I just tried and it completed to a readable pdf files, though after a 
couple of error message of this type :
! Undefined control sequence.
<recently read> \Equiv
                      
l.2379 \end{tabulary}
                    
? x

escaping with 'x' everythime lead to completion....
best,
Johann

Darren Dale wrote:
> On Thursday 12 June 2008 08:08:41 am Michael Droettboom wrote:
>   
>> It looks as if the docs can't be built if text.usetex is "True", first
>> because of needing Unicode (which also requires setting
>> text.latex.unicode to True), and second because the dollar_ticks.py demo
>> doesn't escape '$'.
>>
>> I suppose we should hardcode text.usetex to "False" when building the
>> documentation figures.  Better yet, it might be a good idea to provide a
>> "documentation-only" matplotlibrc (or use only the defaults) so that we
>> can always get consistent results when building the documentation.
>>     
>
> I think an empty matplotlibrc file is the right way to go. I added it in svn.
>   

This suggests that maybe the first line is a buglet (without any real 
consequence), since there happens to be no good reason to require that 
array to be single precision.  I think it's reasonable to say that we 
should use double precision (float/float_/float64) everywhere floating 
point is needed, since a) that's what Python floats are and b) it's on 
the safe side precision-wise, and c) that's what most (if not all) of 
the C++ extensions, such as _backend_agg.cpp expect.  Exceptions would 
be when some binary interface or file format etc. requires otherwise. 

Note, the first line also has a moderate performance penalty since the 
array might be converted twice (once for asarray, and once for astype).  
It would be better to do:

  x = np.asarray(x, np.float_)

As for the distinction between the last two, I think it is primarily a 
style issue.  I don't have a strong feeling either way, but consistency 
would be an improvement, I suppose.

Cheers,
Mike

Stéfan van der Walt wrote:
> 2008/6/12 Manuel Metz <mm...@as...>:
>   
>> When looking, e.g. at axes.py, I see 3 different arguments passed to
>> numpy astype()/array()/zero() and friends:
>>
>>   x = np.asarray(x).astype(np.float32)
>>   x = np.zeros( x, np.float_ )
>>   x = np.ones((col,), float)
>>
>> Is there a preferred one to stick to ?!
>>     
>
> Both `np.float_` and the Python `float` are interpreted as
> `np.float64`.  The only time you really need something other than
> `float` is if you require a width other than 64 (like in the first
> line you showed).
>
> Regards
> Stéfan
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

This message looks interesting.  It suggests that combining non-Computer 
Modern fonts with ams* packages can be troublesome.  Perhaps this has 
been fixed in recent LaTeX distributions, which is why it works for me.

http://osdir.com/ml/tex.latex.beamer.general/2006-01/msg00026.html

I wonder if removing the

\usepackage{times}

from sphinx.sty fixes things for you.  Then we have the Computer Modern 
fonts, of course...

Mike

Michael Droettboom wrote:
> John Hunter wrote:
>   
>> On Thu, Jun 12, 2008 at 7:01 AM, Michael Droettboom <md...@st...> wrote:
>>   
>>     
>>> Hmm.  Isn't broken for me.  I suspect we have some sort of version mismatch.
>>>
>>> One thing to try -- in conf.py remove the line
>>>
>>> \usepackage{amsfonts}
>>>
>>> It actually doesn't seem to be necessary (but the other two are).  This
>>> error message happens during package loading, before any of the core of our
>>> document is parsed.  Is suspect its a bug in your LaTeX distribution that is
>>> causing package conflicts.
>>>     
>>>       
>> No luck on commenting out amsfonts.  I've seen this bug on two
>> platforms, solaris x86 and a recent ubuntu linux distro, so I suspect
>> this mispackaging may be fairly common.
>>     
> Ubuntu 8.4 works for me, but RHEL4 has unrelated errors and has never 
> built Sphinx docs for me.
>   
>>   If I comment out *all* of the
>> ams* usepackages packages, I get past the duplicate Cap error I posted
>>  but then get some undefined symbol error (eg digamma) unsurprisingly.
>>
>> I've tried a few tests, and it looks like   including only amssymb and
>> nothing else gives the duplicate cap error, but excluding it gives the
>> digamma and friends error even if the others are included.  So it
>> looks like I'm stuck, since no combination of these packages works.
>>
>> jdhunter@bic128:doc> uname -a
>> Linux bic128.bic.berkeley.edu 2.6.25.4-10.fc8 #1 SMP Thu May 22
>> 22:58:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
>> jdhunter@bic128:doc> latex --version
>> pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4)
>> kpathsea version 3.5.4
>>
>>   
>>     
> One way I've fixed these errors (manually) in the past is to change the 
> ordering of the \usepackage{} statements.  I wonder if you move the 
> "ams" ones above everything else if that fixes things.  If so hopefully 
> we can submit a patch to sphinx to allow putting the custom preamble 
> earlier.
>
> Barring that, I suppose we'll have to a) drop the symbol table or b) use 
> mathtext to generate the math for LaTeX (there's something very 
> patricidal about that... ;).  b) may be a little bit of work to do well, 
> since we don't currently have a way to get a nice tightly-bound PDF of a 
> math expression, and embedding PNGs will look bad.
>
> Cheers,
> Mike
>
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

2008/6/12 Manuel Metz <mm...@as...>:
> When looking, e.g. at axes.py, I see 3 different arguments passed to
> numpy astype()/array()/zero() and friends:
>
>   x = np.asarray(x).astype(np.float32)
>   x = np.zeros( x, np.float_ )
>   x = np.ones((col,), float)
>
> Is there a preferred one to stick to ?!

Both `np.float_` and the Python `float` are interpreted as
`np.float64`.  The only time you really need something other than
`float` is if you require a width other than 64 (like in the first
line you showed).

Regards
Stéfan

Hi all,

By default, 'legend' uses two points two represent a line.  This looks
a bit weird when you have only markers (no line), e.g.,

import matplotlib.pyplot as plt
plt.plot([1,2,3], [4,5,6], 'x', label='first line')
plt.legend()
plt.show()

Notice how there are two crosses in the legend.  Having only one, as in

import matplotlib.pyplot as plt
plt.plot([1,2,3], [4,5,6], 'x', label='first line')
plt.legend(numpoints=1)
plt.show()

would look better.

Unfortunately, I can't always use numpoints=1, because then the legend
for a normal line isn't drawn properly:

import matplotlib.pyplot as plt
plt.plot([1,2,3], [4,5,6], 'x-', label='first line')
plt.legend(numpoints=1)
plt.show()

What would be ideal (for me personally), is to have, for numpoints=1:

linestyle 'x' ---> legend  '   x   '
linestyle '-x' ---> legend '---x---'

Has this been considered before?  If not, I'll write a patch.

Regards
Stéfan

John Hunter wrote:
> On Thu, Jun 12, 2008 at 7:01 AM, Michael Droettboom <md...@st...> wrote:
>   
>> Hmm.  Isn't broken for me.  I suspect we have some sort of version mismatch.
>>
>> One thing to try -- in conf.py remove the line
>>
>> \usepackage{amsfonts}
>>
>> It actually doesn't seem to be necessary (but the other two are).  This
>> error message happens during package loading, before any of the core of our
>> document is parsed.  Is suspect its a bug in your LaTeX distribution that is
>> causing package conflicts.
>>     
>
> No luck on commenting out amsfonts.  I've seen this bug on two
> platforms, solaris x86 and a recent ubuntu linux distro, so I suspect
> this mispackaging may be fairly common.
Ubuntu 8.4 works for me, but RHEL4 has unrelated errors and has never 
built Sphinx docs for me.
>   If I comment out *all* of the
> ams* usepackages packages, I get past the duplicate Cap error I posted
>  but then get some undefined symbol error (eg digamma) unsurprisingly.
>
> I've tried a few tests, and it looks like   including only amssymb and
> nothing else gives the duplicate cap error, but excluding it gives the
> digamma and friends error even if the others are included.  So it
> looks like I'm stuck, since no combination of these packages works.
>
> jdhunter@bic128:doc> uname -a
> Linux bic128.bic.berkeley.edu 2.6.25.4-10.fc8 #1 SMP Thu May 22
> 22:58:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
> jdhunter@bic128:doc> latex --version
> pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4)
> kpathsea version 3.5.4
>
>   
One way I've fixed these errors (manually) in the past is to change the 
ordering of the \usepackage{} statements.  I wonder if you move the 
"ams" ones above everything else if that fixes things.  If so hopefully 
we can submit a patch to sphinx to allow putting the custom preamble 
earlier.

Barring that, I suppose we'll have to a) drop the symbol table or b) use 
mathtext to generate the math for LaTeX (there's something very 
patricidal about that... ;).  b) may be a little bit of work to do well, 
since we don't currently have a way to get a nice tightly-bound PDF of a 
math expression, and embedding PNGs will look bad.

Cheers,
Mike

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

On Thu, Jun 12, 2008 at 7:01 AM, Michael Droettboom <md...@st...> wrote:
> Hmm.  Isn't broken for me.  I suspect we have some sort of version mismatch.
>
> One thing to try -- in conf.py remove the line
>
> \usepackage{amsfonts}
>
> It actually doesn't seem to be necessary (but the other two are).  This
> error message happens during package loading, before any of the core of our
> document is parsed.  Is suspect its a bug in your LaTeX distribution that is
> causing package conflicts.

No luck on commenting out amsfonts.  I've seen this bug on two
platforms, solaris x86 and a recent ubuntu linux distro, so I suspect
this mispackaging may be fairly common.  If I comment out *all* of the
ams* usepackages packages, I get past the duplicate Cap error I posted
 but then get some undefined symbol error (eg digamma) unsurprisingly.

I've tried a few tests, and it looks like   including only amssymb and
nothing else gives the duplicate cap error, but excluding it gives the
digamma and friends error even if the others are included.  So it
looks like I'm stuck, since no combination of these packages works.

jdhunter@bic128:doc> uname -a
Linux bic128.bic.berkeley.edu 2.6.25.4-10.fc8 #1 SMP Thu May 22
22:58:37 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
jdhunter@bic128:doc> latex --version
pdfeTeX 3.141592-1.21a-2.2 (Web2C 7.5.4)
kpathsea version 3.5.4


JDH

On Thursday 12 June 2008 08:08:41 am Michael Droettboom wrote:
> It looks as if the docs can't be built if text.usetex is "True", first
> because of needing Unicode (which also requires setting
> text.latex.unicode to True), and second because the dollar_ticks.py demo
> doesn't escape '$'.
>
> I suppose we should hardcode text.usetex to "False" when building the
> documentation figures.  Better yet, it might be a good idea to provide a
> "documentation-only" matplotlibrc (or use only the defaults) so that we
> can always get consistent results when building the documentation.

I think an empty matplotlibrc file is the right way to go. I added it in svn.

matplotlib-0.98 is not available for easy_install it seems:
 sudo easy_install --dry-run matplotlib
Searching for matplotlib
Best match: matplotlib 0.91.2
Processing matplotlib-0.91.2-py2.5-linux-x86_64.egg
matplotlib 0.91.2 is already the active version in easy-install.pth

It looks as if the docs can't be built if text.usetex is "True", first 
because of needing Unicode (which also requires setting 
text.latex.unicode to True), and second because the dollar_ticks.py demo 
doesn't escape '$'.

I suppose we should hardcode text.usetex to "False" when building the 
documentation figures.  Better yet, it might be a good idea to provide a 
"documentation-only" matplotlibrc (or use only the defaults) so that we 
can always get consistent results when building the documentation.

Cheers,
Mike

Johann Cohen-Tanugi wrote:
> I did not manage to build it either, but with another error, the 
> output is actually huge, and ipython (how come it is called?) crashes, 
> but after CTRL-C I get:
> Original exception was:
> Traceback (most recent call last):
>  File "make.py", line 54, in <module>
>    all()
>  File "make.py", line 39, in all
>    figs()
>  File "make.py", line 25, in figs
>    plt.savefig(outfile)
>  File "/usr/lib/python2.5/site-packages/matplotlib/pyplot.py", line 
> 278, in savefig
>    return fig.savefig(*args, **kwargs)
>  File "/usr/lib/python2.5/site-packages/matplotlib/figure.py", line 
> 986, in savefig
>    self.canvas.print_figure(*args, **kwargs)
>  File "/usr/lib/python2.5/site-packages/matplotlib/backend_bases.py", 
> line 1286, in print_figure
>    **kwargs)
>  File 
> "/usr/lib/python2.5/site-packages/matplotlib/backends/backend_agg.py", 
> line 300, in print_png
>    FigureCanvasAgg.draw(self)
>  File 
> "/usr/lib/python2.5/site-packages/matplotlib/backends/backend_agg.py", 
> line 256, in draw
>    self.figure.draw(self.renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/figure.py", line 
> 825, in draw
>    for a in self.axes: a.draw(renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/axes.py", line 
> 1502, in draw
>    a.draw(renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/axis.py", line 674, 
> in draw
>    tick.draw(renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/axis.py", line 173, 
> in draw
>    self.label1.draw(renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/text.py", line 764, 
> in draw
>    Text.draw(self, renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/text.py", line 298, 
> in draw
>    bbox, info = self._get_layout(renderer)
>  File "/usr/lib/python2.5/site-packages/matplotlib/text.py", line 198, 
> in _get_layout
>    line, self._fontproperties, ismath=self.is_math_text(line))
>  File 
> "/usr/lib/python2.5/site-packages/matplotlib/backends/backend_agg.py", 
> line 128, in get_text_width_height_descent
>    Z = texmanager.get_grey(s, size, self.dpi)
>  File "/usr/lib/python2.5/site-packages/matplotlib/texmanager.py", 
> line 366, in get_grey
>    pngfile = self.make_png(tex, fontsize, dpi)
>  File "/usr/lib/python2.5/site-packages/matplotlib/texmanager.py", 
> line 300, in make_png
>    dvifile = self.make_dvi(tex, fontsize)
>  File "/usr/lib/python2.5/site-packages/matplotlib/texmanager.py", 
> line 269, in make_dvi
>    texfile = self.make_tex(tex, fontsize)
>  File "/usr/lib/python2.5/site-packages/matplotlib/texmanager.py", 
> line 248, in make_tex
>    fh.write(s)
>
> Johann
>
>
> John Hunter wrote:
>> On Wed, Jun 11, 2008 at 12:35 PM, John Hunter <jd...@gm...> wrote:
>>  
>>> On Wed, Jun 11, 2008 at 12:25 PM, Michael Droettboom 
>>> <md...@st...> wrote:
>>>    
>>>> Ok.  I think I have that worked out -- would you mind testing on 
>>>> docutils
>>>> 0.4?  (I don't think I broke anything that wasn't already broken...)
>>>>       
>>> OK, sorry I've been causing so much trouble, but I guess it is good
>>> that at least one of works on python 2.4 sometimes.
>>>     
>>
>> Just a quick note that latex builds appear broken, and the error
>> message suggests it is a math problem, perhaps caused by the new
>> symbol table.  First error is:
>>
>> ! LaTeX Error: Command \Cap already defined.
>>                Or name \end... illegal, see p.192 of the manual.
>>
>> complete output below...
>>
>> jdhunter@bic128:doc> python make.py latex
>> making figs
>>     already have dollar_ticks.png
>>     already have pyplot_three.png
>>     already have pyplot_two_subplots.png
>>     already have fig_x.png
>>     already have pyplot_annotate.png
>>     already have text_commands.png
>>     already have pyplot_simple.png
>>     already have pyplot_mathtext.png
>>     already have annotation_polar.png
>>     already have annotation_basic.png
>>     already have fig_axes_labels_simple.png
>>     already have text_layout.png
>>     already have pyplot_text.png
>>     already have fig_axes_customize_simple.png
>>     already have pyplot_formatstr.png
>> all figures made
>> Sphinx v0.3, building latex
>> trying to load pickled env... not found
>> building [latex]: all documents
>> updating environment: 31 added, 0 changed, 0 removed
>> reading... api/artist_api api/axes_api api/backend_api api/index
>> api/pyplot_api devel/add_new_projection devel/coding_guide
>> devel/documenting_mpl devel/index devel/outline devel/transformations
>> faq/environment_variables_faq faq/howto_faq faq/index
>> faq/installing_faq faq/troubleshooting_faq index users/annotations
>> users/arraydata users/artists users/customizing users/event_handling
>> users/index users/index_text users/intro users/mathtext
>> users/navigation_toolbar users/pyplot_tutorial users/text_intro
>> users/text_props users/usetex
>> pickling the env... done
>> checking consistency...
>> WARNING: /home/jdhunter/mpl/doc/users/arraydata.rst:: document isn't
>> included in any toctree
>> processing Matplotlib.tex... index users/index users/intro
>> users/pyplot_tutorial users/navigation_toolbar users/customizing
>> users/index_text users/text_intro users/text_props users/mathtext
>> users/usetex users/annotations users/artists users/event_handling
>> faq/index faq/installing_faq faq/troubleshooting_faq faq/howto_faq
>> faq/environment_variables_faq devel/index devel/coding_guide
>> devel/documenting_mpl devel/transformations devel/add_new_projection
>> devel/outline api/index api/artist_api api/axes_api api/pyplot_api
>> api/backend_api
>> resolving references...
>> writing... done
>> finishing...
>> copying images... _static/cm_fontset.png
>> users/figures/fig_axes_labels_simple.png mpl_data/images/back.png
>> _static/stix_fontset.png users/figures/fig_x.png
>> mpl_data/images/zoom_to_rect.png mpl_data/images/filesave.png
>> users/figures/pyplot_text.png users/figures/dollar_ticks.png
>> _static/transforms.png users/figures/annotation_basic.png
>> users/figures/annotation_polar.png users/figures/pyplot_mathtext.png
>> mpl_data/images/home.png _static/stixsans_fontset.png
>> users/figures/pyplot_formatstr.png mpl_data/images/move.png
>> users/figures/fig_axes_customize_simple.png
>> users/figures/text_layout.png mpl_data/images/subplots.png
>> users/figures/text_commands.png users/figures/pyplot_annotate.png
>> _static/tex_unicode_demo.png users/figures/pyplot_three.png
>> _static/tex_demo.png mpl_data/images/forward.png
>> users/figures/pyplot_two_subplots.png _static/toolbar.png
>> _static/stix_fonts.png users/figures/pyplot_simple.png
>> copying TeX support files...
>> build succeeded, 1 warning.
>> This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
>> entering extended mode
>> (./Matplotlib.tex
>> LaTeX2e <2003/12/01>
>> Babel <v3.8d> and hyphenation patterns for american, french, german, 
>> ngerman, b
>> ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, 
>> esperanto, e
>> stonian, finnish, greek, icelandic, irish, italian, latin, magyar, 
>> norsk, polis
>> h, portuges, romanian, russian, serbian, slovak, slovene, spanish, 
>> swedish, tur
>> kish, ukrainian, nohyphenation, loaded.
>> (./manual.cls
>> Document Class: manual 2008/05/01 Document class (Sphinx manual)
>> (/usr/share/texmf/tex/latex/fancybox/fancybox.sty
>> Style option: `fancybox' v1.3 <2000/09/19> (tvz)
>> ) (/usr/share/texmf/tex/latex/base/report.cls
>> Document Class: report 2004/02/16 v1.4f Standard LaTeX document class
>> (/usr/share/texmf/tex/latex/base/size11.clo))
>> (/usr/share/texmf/tex/latex/fancyhdr/fancyhdr.sty) (./fncychap.sty)
>> (./sphinx.sty (/usr/share/texmf/tex/latex/base/textcomp.sty
>> (/usr/share/texmf/tex/latex/base/ts1enc.def))
>> (/usr/share/texmf/tex/latex/psnfss/times.sty)
>> (/usr/share/texmf/tex/latex/fancyvrb/fancyvrb.sty
>> Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
>> (/usr/share/texmf/tex/latex/graphics/keyval.sty)
>> No file fancyvrb.cfg.
>> ) (/usr/share/texmf/tex/latex/titlesec/titlesec.sty) (./tabulary.sty
>> (/usr/share/texmf/tex/latex/tools/array.sty))
>> (/usr/share/texmf/tex/latex/graphics/color.sty
>> (/usr/share/texmf/tex/latex/graphics/color.cfg)
>> (/usr/share/texmf/tex/latex/graphics/pdftex.def))
>> (/usr/share/texmf/tex/latex/hyperref/hyperref.sty
>> (/usr/share/texmf/tex/latex/hyperref/pd1enc.def)
>> (/usr/share/texmf/tex/latex/hyperref/hyperref.cfg)
>> Implicit mode ON; LaTeX internals redefined
>> (/usr/share/texmf/tex/latex/url/url.sty))
>> *hyperref using default driver hpdftex*
>> (/usr/share/texmf/tex/latex/hyperref/hpdftex.def
>> (/usr/share/texmf/tex/latex/psnfss/pifont.sty
>> (/usr/share/texmf/tex/latex/psnfss/upzd.fd)
>> (/usr/share/texmf/tex/latex/psnfss/upsy.fd)))
>> (/usr/share/texmf/tex/latex/framed/framed.sty)
>> (/usr/share/texmf/tex/latex/graphics/graphicx.sty
>> (/usr/share/texmf/tex/latex/graphics/graphics.sty
>> (/usr/share/texmf/tex/latex/graphics/trig.sty)
>> (/usr/share/texmf/tex/latex/graphics/graphics.cfg)))
>> (/usr/share/texmf/tex/plain/pdfcolor/pdfcolor.tex))
>> (/usr/share/texmf/tex/latex/base/makeidx.sty))
>> (/usr/share/texmf/tex/latex/base/inputenc.sty
>> (/usr/share/texmf/tex/latex/base/utf8.def
>> (/usr/share/texmf/tex/latex/base/t1enc.dfu)
>> (/usr/share/texmf/tex/latex/base/ot1enc.dfu)
>> (/usr/share/texmf/tex/latex/base/omsenc.dfu)
>> (/usr/share/texmf/tex/latex/base/ts1enc.dfu)))
>> (/usr/share/texmf/tex/latex/base/fontenc.sty
>> (/usr/share/texmf/tex/latex/base/t1enc.def))
>> (/usr/share/texmf/tex/latex/amsmath/amsmath.sty
>> For additional information on amsmath, use the `?' option.
>> (/usr/share/texmf/tex/latex/amsmath/amstext.sty
>> (/usr/share/texmf/tex/latex/amsmath/amsgen.sty))
>> (/usr/share/texmf/tex/latex/amsmath/amsbsy.sty)
>> (/usr/share/texmf/tex/latex/amsmath/amsopn.sty))
>> (/usr/share/texmf/tex/latex/amsfonts/amsfonts.sty)
>> (/usr/share/texmf/tex/latex/amsfonts/amssymb.sty)
>> Writing index file Matplotlib.idx
>>
>> ! LaTeX Error: Command \Cap already defined.
>>                Or name \end... illegal, see p.192 of the manual.
>>
>> See the LaTeX manual or LaTeX Companion for explanation.
>> Type  H <return>  for immediate help.
>>  ...
>>
>> l.28 ...ap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>>
>> ------------------------------------------------------------------------- 
>>
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hmm.  Isn't broken for me.  I suspect we have some sort of version mismatch.

One thing to try -- in conf.py remove the line

\usepackage{amsfonts}

It actually doesn't seem to be necessary (but the other two are).  This 
error message happens during package loading, before any of the core of 
our document is parsed.  Is suspect its a bug in your LaTeX distribution 
that is causing package conflicts.

Cheers,
Mike

John Hunter wrote:
> On Wed, Jun 11, 2008 at 12:35 PM, John Hunter <jd...@gm...> wrote:
>   
>> On Wed, Jun 11, 2008 at 12:25 PM, Michael Droettboom <md...@st...> wrote:
>>     
>>> Ok.  I think I have that worked out -- would you mind testing on docutils
>>> 0.4?  (I don't think I broke anything that wasn't already broken...)
>>>       
>> OK, sorry I've been causing so much trouble, but I guess it is good
>> that at least one of works on python 2.4 sometimes.
>>     
>
> Just a quick note that latex builds appear broken, and the error
> message suggests it is a math problem, perhaps caused by the new
> symbol table.  First error is:
>
> ! LaTeX Error: Command \Cap already defined.
>                Or name \end... illegal, see p.192 of the manual.
>
> complete output below...
>
> jdhunter@bic128:doc> python make.py latex
> making figs
>     already have dollar_ticks.png
>     already have pyplot_three.png
>     already have pyplot_two_subplots.png
>     already have fig_x.png
>     already have pyplot_annotate.png
>     already have text_commands.png
>     already have pyplot_simple.png
>     already have pyplot_mathtext.png
>     already have annotation_polar.png
>     already have annotation_basic.png
>     already have fig_axes_labels_simple.png
>     already have text_layout.png
>     already have pyplot_text.png
>     already have fig_axes_customize_simple.png
>     already have pyplot_formatstr.png
> all figures made
> Sphinx v0.3, building latex
> trying to load pickled env... not found
> building [latex]: all documents
> updating environment: 31 added, 0 changed, 0 removed
> reading... api/artist_api api/axes_api api/backend_api api/index
> api/pyplot_api devel/add_new_projection devel/coding_guide
> devel/documenting_mpl devel/index devel/outline devel/transformations
> faq/environment_variables_faq faq/howto_faq faq/index
> faq/installing_faq faq/troubleshooting_faq index users/annotations
> users/arraydata users/artists users/customizing users/event_handling
> users/index users/index_text users/intro users/mathtext
> users/navigation_toolbar users/pyplot_tutorial users/text_intro
> users/text_props users/usetex
> pickling the env... done
> checking consistency...
> WARNING: /home/jdhunter/mpl/doc/users/arraydata.rst:: document isn't
> included in any toctree
> processing Matplotlib.tex... index users/index users/intro
> users/pyplot_tutorial users/navigation_toolbar users/customizing
> users/index_text users/text_intro users/text_props users/mathtext
> users/usetex users/annotations users/artists users/event_handling
> faq/index faq/installing_faq faq/troubleshooting_faq faq/howto_faq
> faq/environment_variables_faq devel/index devel/coding_guide
> devel/documenting_mpl devel/transformations devel/add_new_projection
> devel/outline api/index api/artist_api api/axes_api api/pyplot_api
> api/backend_api
> resolving references...
> writing... done
> finishing...
> copying images... _static/cm_fontset.png
> users/figures/fig_axes_labels_simple.png mpl_data/images/back.png
> _static/stix_fontset.png users/figures/fig_x.png
> mpl_data/images/zoom_to_rect.png mpl_data/images/filesave.png
> users/figures/pyplot_text.png users/figures/dollar_ticks.png
> _static/transforms.png users/figures/annotation_basic.png
> users/figures/annotation_polar.png users/figures/pyplot_mathtext.png
> mpl_data/images/home.png _static/stixsans_fontset.png
> users/figures/pyplot_formatstr.png mpl_data/images/move.png
> users/figures/fig_axes_customize_simple.png
> users/figures/text_layout.png mpl_data/images/subplots.png
> users/figures/text_commands.png users/figures/pyplot_annotate.png
> _static/tex_unicode_demo.png users/figures/pyplot_three.png
> _static/tex_demo.png mpl_data/images/forward.png
> users/figures/pyplot_two_subplots.png _static/toolbar.png
> _static/stix_fonts.png users/figures/pyplot_simple.png
> copying TeX support files...
> build succeeded, 1 warning.
> This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
> entering extended mode
> (./Matplotlib.tex
> LaTeX2e <2003/12/01>
> Babel <v3.8d> and hyphenation patterns for american, french, german, ngerman, b
> ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e
> stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis
> h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur
> kish, ukrainian, nohyphenation, loaded.
> (./manual.cls
> Document Class: manual 2008/05/01 Document class (Sphinx manual)
> (/usr/share/texmf/tex/latex/fancybox/fancybox.sty
> Style option: `fancybox' v1.3 <2000/09/19> (tvz)
> ) (/usr/share/texmf/tex/latex/base/report.cls
> Document Class: report 2004/02/16 v1.4f Standard LaTeX document class
> (/usr/share/texmf/tex/latex/base/size11.clo))
> (/usr/share/texmf/tex/latex/fancyhdr/fancyhdr.sty) (./fncychap.sty)
> (./sphinx.sty (/usr/share/texmf/tex/latex/base/textcomp.sty
> (/usr/share/texmf/tex/latex/base/ts1enc.def))
> (/usr/share/texmf/tex/latex/psnfss/times.sty)
> (/usr/share/texmf/tex/latex/fancyvrb/fancyvrb.sty
> Style option: `fancyvrb' v2.6, with DG/SPQR fixes <1998/07/17> (tvz)
> (/usr/share/texmf/tex/latex/graphics/keyval.sty)
> No file fancyvrb.cfg.
> ) (/usr/share/texmf/tex/latex/titlesec/titlesec.sty) (./tabulary.sty
> (/usr/share/texmf/tex/latex/tools/array.sty))
> (/usr/share/texmf/tex/latex/graphics/color.sty
> (/usr/share/texmf/tex/latex/graphics/color.cfg)
> (/usr/share/texmf/tex/latex/graphics/pdftex.def))
> (/usr/share/texmf/tex/latex/hyperref/hyperref.sty
> (/usr/share/texmf/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texmf/tex/latex/hyperref/hyperref.cfg)
> Implicit mode ON; LaTeX internals redefined
> (/usr/share/texmf/tex/latex/url/url.sty))
> *hyperref using default driver hpdftex*
> (/usr/share/texmf/tex/latex/hyperref/hpdftex.def
> (/usr/share/texmf/tex/latex/psnfss/pifont.sty
> (/usr/share/texmf/tex/latex/psnfss/upzd.fd)
> (/usr/share/texmf/tex/latex/psnfss/upsy.fd)))
> (/usr/share/texmf/tex/latex/framed/framed.sty)
> (/usr/share/texmf/tex/latex/graphics/graphicx.sty
> (/usr/share/texmf/tex/latex/graphics/graphics.sty
> (/usr/share/texmf/tex/latex/graphics/trig.sty)
> (/usr/share/texmf/tex/latex/graphics/graphics.cfg)))
> (/usr/share/texmf/tex/plain/pdfcolor/pdfcolor.tex))
> (/usr/share/texmf/tex/latex/base/makeidx.sty))
> (/usr/share/texmf/tex/latex/base/inputenc.sty
> (/usr/share/texmf/tex/latex/base/utf8.def
> (/usr/share/texmf/tex/latex/base/t1enc.dfu)
> (/usr/share/texmf/tex/latex/base/ot1enc.dfu)
> (/usr/share/texmf/tex/latex/base/omsenc.dfu)
> (/usr/share/texmf/tex/latex/base/ts1enc.dfu)))
> (/usr/share/texmf/tex/latex/base/fontenc.sty
> (/usr/share/texmf/tex/latex/base/t1enc.def))
> (/usr/share/texmf/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texmf/tex/latex/amsmath/amstext.sty
> (/usr/share/texmf/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texmf/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texmf/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texmf/tex/latex/amsfonts/amsfonts.sty)
> (/usr/share/texmf/tex/latex/amsfonts/amssymb.sty)
> Writing index file Matplotlib.idx
>
> ! LaTeX Error: Command \Cap already defined.
>                Or name \end... illegal, see p.192 of the manual.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H <return>  for immediate help.
>  ...
>
> l.28 ...ap[1]{\textcolor[rgb]{0.78,0.36,0.04}{#1}}
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA