matplotlib-devel Mailing List for matplotlib (Page 3)

On 05/16/2011 09:08 AM, Benjamin Root wrote:
>
>
> On Mon, May 16, 2011 at 1:35 PM, Eric Firing <ef...@ha...
> <mailto:ef...@ha...>> wrote:
>
>     On 05/16/2011 06:56 AM, Benjamin Root wrote:
>      >
>      >
>      > On Tue, May 10, 2011 at 12:53 PM, John Hunter <jd...@gm...
>     <mailto:jd...@gm...>
>      > <mailto:jd...@gm... <mailto:jd...@gm...>>> wrote:
>      >
>      >
>      >
>      >     On Tue, May 10, 2011 at 12:48 PM, Benjamin Root
>     <ben...@ou... <mailto:ben...@ou...>
>      > <mailto:ben...@ou... <mailto:ben...@ou...>>> wrote:
>      >
>      >
>      >
>      >
>      >         The one thing I am confused about is what file to edit
>     for the
>      >         main page.  I must be very dense because I just simply
>     can not
>      >         figure out where the main page is generated from.  I have
>     been
>      >         meaning to fix some things on the front page for a while now,
>      >         but have been too afraid to ask.
>      >
>      >
>      >     see doc/_templates/*.html
>      >
>      >     After you have integrated the pull request into the 1.0.x branch
>      >     (which is what I build the website from) I'll build and push
>     it to
>      >     the sf site.
>      >
>      >
>      > Sorry it took so long.  I have made those immediate fixes and pushed
>      > them up to my pull request.  If there are any other doc fixes we
>     want to
>      > make, now would be a good time to do it.
>
>     Ben,
>
>     Would you add widget.py to the autogenerated API docs, please, unless
>     there is some reason for it to be excluded?  I happened to notice that
>     it is missing; I haven't checked for other missing modules.
>
>     Thank you.
>
>     Eric
>
>
> No problem.  Having a quick view through the docs, here is what I see as
> missing.  Maybe some of these don't need to be included?
>
>
> bezier.py
> blocking_input.py
> contour.py
> finance.py
> fontconfig_pattern.py
> hatch.py
> image.py
> legend.py
> lines.py
> mpl.py
> offsetbox.py
> patches.py
> patheffects.py
> pylab.py
> pyparsing.py
> quiver.py
> scale.py
> table.py
> texmanager.py
> textpath.py
> text.py
> tight_bbox.py
> transforms.py
> widgets.py
>
> Some of these might not be "modules" per se, I was just doing a quick
> comparison of what rst docs we have and what we have in lib/matplotlib.
> Note, we are also missing api docs for backends "cairo", "cocoaagg",
> "emf", "fltkagg", "gdk", "gtkcairo", "gtk", "macosx", "mixed", "ps",
> "qt4", "qtagg", "qt", "svg", "tkagg", and "wx".  Again, some of these
> might be redundant, I am just noticing differences between the available
> rst docs and the listed modules.

Ben,

I had no idea this would open such a big can of worms!  The strategy 
question here is, what do we want to include in the html API docs?

It looks like the process of setting up the sphinx API docs was never 
completed; the present set of modules that are included ranges from the 
fundamental (e.g. figure.py) to the peripheral (e.g. afm.py), but I 
doubt that text.py, for example, was deliberately excluded.

I don't see any major disadvantage to including all modules.  It might 
make sense to present them in categories, though, instead of dumping 
them all into a single alphabetical list.

Perhaps Mike and John will have sage advice.

>
> Also, I noticed that nxutils_api.rst is pretty much useless.  Should I
> fix that?

Yes, please.

I don't know how much time you have for working on the docs, but don't 
let the potential magnitude of the task block incremental improvements.

Here is an example of another miscellaneous doc problem that was pointed 
out by a user: the kwarg "agg_filter" shows up all over the place in 
kwarg tables, with helpful description "unknown"!  Now, how many of us, 
looking at such a table, know what "agg_filter" is, what it does, or 
where it comes from?  It is inherited from Artist, but there is nothing 
in the python code, or in the src, to indicate what it is or how to use 
it.  The magic of rgrep turns up one source of info: 
./examples/pylab_examples/demo_agg_filter.py, showing that agg_filter 
can enable truly impressive fancy effects.

Where that particular example leads is the conclusion that probably most 
of demo_agg_filter.py deserves to be promoted to a regular matplotlib 
module.  That doesn't change the original problem in the docs, which is 
the presence of irrelevant and/or inscrutable inherited  kwargs in kwarg 
tables.


Eric

>
> Ben Root
>

On Mon, May 16, 2011 at 2:08 PM, Benjamin Root <ben...@ou...> wrote:

>
>
> On Mon, May 16, 2011 at 1:35 PM, Eric Firing <ef...@ha...> wrote:
>
>> On 05/16/2011 06:56 AM, Benjamin Root wrote:
>> >
>> >
>> > On Tue, May 10, 2011 at 12:53 PM, John Hunter <jd...@gm...
>> > <mailto:jd...@gm...>> wrote:
>> >
>> >
>> >
>> >     On Tue, May 10, 2011 at 12:48 PM, Benjamin Root <ben...@ou...
>> >     <mailto:ben...@ou...>> wrote:
>> >
>> >
>> >
>> >
>> >         The one thing I am confused about is what file to edit for the
>> >         main page.  I must be very dense because I just simply can not
>> >         figure out where the main page is generated from.  I have been
>> >         meaning to fix some things on the front page for a while now,
>> >         but have been too afraid to ask.
>> >
>> >
>> >     see doc/_templates/*.html
>> >
>> >     After you have integrated the pull request into the 1.0.x branch
>> >     (which is what I build the website from) I'll build and push it to
>> >     the sf site.
>> >
>> >
>> > Sorry it took so long.  I have made those immediate fixes and pushed
>> > them up to my pull request.  If there are any other doc fixes we want to
>> > make, now would be a good time to do it.
>>
>> Ben,
>>
>> Would you add widget.py to the autogenerated API docs, please, unless
>> there is some reason for it to be excluded?  I happened to notice that
>> it is missing; I haven't checked for other missing modules.
>>
>> Thank you.
>>
>> Eric
>>
>>
> No problem.  Having a quick view through the docs, here is what I see as
> missing.  Maybe some of these don't need to be included?
>
>
> bezier.py
> blocking_input.py
> contour.py
> finance.py
> fontconfig_pattern.py
> hatch.py
> image.py
> legend.py
> lines.py
> mpl.py
> offsetbox.py
> patches.py
> patheffects.py
> pylab.py
> pyparsing.py
> quiver.py
> scale.py
> table.py
> texmanager.py
> textpath.py
> text.py
> tight_bbox.py
> transforms.py
> widgets.py
>
> Some of these might not be "modules" per se, I was just doing a quick
> comparison of what rst docs we have and what we have in lib/matplotlib.
> Note, we are also missing api docs for backends "cairo", "cocoaagg", "emf",
> "fltkagg", "gdk", "gtkcairo", "gtk", "macosx", "mixed", "ps", "qt4",
> "qtagg", "qt", "svg", "tkagg", and "wx".  Again, some of these might be
> redundant, I am just noticing differences between the available rst docs and
> the listed modules.
>
> Also, I noticed that nxutils_api.rst is pretty much useless.  Should I fix
> that?
>
> Ben Root
>
>

Corrections....

fontconfig_pattern is included in font_manager_api.rst
legend, lines, patches and text are included in artist_api.rst.  However,
legend is not included for the inheritance diagram.

Also, 'spines' is listed as 'spine'.  I don't know if that impacts anything,
but I am a stickler for consistency.  Should this be fixed?

Ben Root

On Mon, May 16, 2011 at 1:35 PM, Eric Firing <ef...@ha...> wrote:

> On 05/16/2011 06:56 AM, Benjamin Root wrote:
> >
> >
> > On Tue, May 10, 2011 at 12:53 PM, John Hunter <jd...@gm...
> > <mailto:jd...@gm...>> wrote:
> >
> >
> >
> >     On Tue, May 10, 2011 at 12:48 PM, Benjamin Root <ben...@ou...
> >     <mailto:ben...@ou...>> wrote:
> >
> >
> >
> >
> >         The one thing I am confused about is what file to edit for the
> >         main page.  I must be very dense because I just simply can not
> >         figure out where the main page is generated from.  I have been
> >         meaning to fix some things on the front page for a while now,
> >         but have been too afraid to ask.
> >
> >
> >     see doc/_templates/*.html
> >
> >     After you have integrated the pull request into the 1.0.x branch
> >     (which is what I build the website from) I'll build and push it to
> >     the sf site.
> >
> >
> > Sorry it took so long.  I have made those immediate fixes and pushed
> > them up to my pull request.  If there are any other doc fixes we want to
> > make, now would be a good time to do it.
>
> Ben,
>
> Would you add widget.py to the autogenerated API docs, please, unless
> there is some reason for it to be excluded?  I happened to notice that
> it is missing; I haven't checked for other missing modules.
>
> Thank you.
>
> Eric
>
>
No problem.  Having a quick view through the docs, here is what I see as
missing.  Maybe some of these don't need to be included?


bezier.py
blocking_input.py
contour.py
finance.py
fontconfig_pattern.py
hatch.py
image.py
legend.py
lines.py
mpl.py
offsetbox.py
patches.py
patheffects.py
pylab.py
pyparsing.py
quiver.py
scale.py
table.py
texmanager.py
textpath.py
text.py
tight_bbox.py
transforms.py
widgets.py

Some of these might not be "modules" per se, I was just doing a quick
comparison of what rst docs we have and what we have in lib/matplotlib.
Note, we are also missing api docs for backends "cairo", "cocoaagg", "emf",
"fltkagg", "gdk", "gtkcairo", "gtk", "macosx", "mixed", "ps", "qt4",
"qtagg", "qt", "svg", "tkagg", and "wx".  Again, some of these might be
redundant, I am just noticing differences between the available rst docs and
the listed modules.

Also, I noticed that nxutils_api.rst is pretty much useless.  Should I fix
that?

Ben Root

On 05/16/2011 06:56 AM, Benjamin Root wrote:
>
>
> On Tue, May 10, 2011 at 12:53 PM, John Hunter <jd...@gm...
> <mailto:jd...@gm...>> wrote:
>
>
>
>     On Tue, May 10, 2011 at 12:48 PM, Benjamin Root <ben...@ou...
>     <mailto:ben...@ou...>> wrote:
>
>
>
>
>         The one thing I am confused about is what file to edit for the
>         main page.  I must be very dense because I just simply can not
>         figure out where the main page is generated from.  I have been
>         meaning to fix some things on the front page for a while now,
>         but have been too afraid to ask.
>
>
>     see doc/_templates/*.html
>
>     After you have integrated the pull request into the 1.0.x branch
>     (which is what I build the website from) I'll build and push it to
>     the sf site.
>
>
> Sorry it took so long.  I have made those immediate fixes and pushed
> them up to my pull request.  If there are any other doc fixes we want to
> make, now would be a good time to do it.

Ben,

Would you add widget.py to the autogenerated API docs, please, unless 
there is some reason for it to be excluded?  I happened to notice that 
it is missing; I haven't checked for other missing modules.

Thank you.

Eric

>
> Ben Root
>

Oops.  I don't think we intend to drop support for Python 2.4 just yet.  
I forgot the with statement was so recent.  I will revert this.

Cheers,
Mike

On 05/16/2011 01:14 PM, Benjamin Root wrote:
> I just noticed that some recent commits included the use of the 
> (somewhat) new 'with' construct.  Are we officially dropping support 
> for python 2.4 in the master branch?  If so, what other features could 
> we now utilize that were introduced in 2.5?
>
> Ben Root
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

I just noticed that some recent commits included the use of the (somewhat)
new 'with' construct.  Are we officially dropping support for python 2.4 in
the master branch?  If so, what other features could we now utilize that
were introduced in 2.5?

Ben Root

On Tue, May 10, 2011 at 12:53 PM, John Hunter <jd...@gm...> wrote:

>
>
> On Tue, May 10, 2011 at 12:48 PM, Benjamin Root <ben...@ou...> wrote:
>
>>
>>
>>
>> The one thing I am confused about is what file to edit for the main page.
>> I must be very dense because I just simply can not figure out where the main
>> page is generated from.  I have been meaning to fix some things on the front
>> page for a while now, but have been too afraid to ask.
>>
>
> see doc/_templates/*.html
>
> After you have integrated the pull request into the 1.0.x branch (which is
> what I build the website from) I'll build and push it to the sf site.
>

Sorry it took so long.  I have made those immediate fixes and pushed them up
to my pull request.  If there are any other doc fixes we want to make, now
would be a good time to do it.

Ben Root

>
> import matplotlib.pyplot as plt
> fig = plt.figure()
> ax = plt.subplot(1,1,1)
> ax.plot(1.1, 2.2, label='foo')
> ax.legend(numpoints=0)
> # ValueError: numpoints must be >= 0; it was 0
>

In legend.__init__ the exception message doesn't match the condition that
raises it.  I think it should say "numpoints must be > 0".  I'm using
matplotlib version 0.99.3.


Steve

Thanks for the report.  Yes, the dependencies should be made more 
explicit in the docs.

On 05/11/2011 12:49 AM, bu...@gm... wrote:
> I've been trying to run the matplotlib test suite but the docs seem 
> incomplete on this subject.
>
> >> http://matplotlib.github.com/devel/coding_guide.html#running-the-tests
> Running the tests is simple. Make sure you have nose installed and 
> type from within Python:
> import matplotlib
> matplotlib.test()
> To run a single test from the command line, you can provide a 
> dot-separated path to the module and function, eg. (this is assuming 
> the test is installed):
> nosetests matplotlib.tests.test_simplification:test_clipping
>
>
>
> Most test fail when I do what is suggested because PIL is not 
> installed and is a requirement for all image_comparison tests.
>
> A bit more information in the docs would be helpful for first time 
> testers.
> IMO the optional dependencies required for running the test suite 
> should be listed (possibly in the installation guide:
> >> http://matplotlib.github.com/users/installing.html )
> and info should be provided on how to run only the tests that don't 
> require PIL.
There doesn't really exist a convenient way to do that, and besides the 
vast majority of tests are image comparison tests.  The when the Python 
3.x branch of matplotlib (which is designed to work with Python 2.6 
forward) is merged into master, this will all be moot anyways.  Since 
PIL doesn't yet exist on Python 3.x, the image comparison routines had 
to be rewritten without using PIL.

Mike

-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

On Thu, Mar 31, 2011 at 11:39 AM, Benjamin Root <ben...@ou...> wrote:

>
>
> On Sat, Mar 26, 2011 at 10:16 AM, Virgil Stokes <vs...@it...> wrote:
>
>> I found that
>>
>> def set_sort_zpos(self,val):
>>      '''Set the position to use for z-sorting.'''
>>      self._sort_zpos = val
>>
>> was missing from
>>
>> class Line3DCollection(LineCollection) (in matplotlib 1.0.1):
>>
>> Now,  with the above method added, add_collection3d works as it should
>> with line
>> segments, and the following will work as expected :-)
>>
>> '''
>>  Purpose: Waterfall plot using LineCollection
>>  Author: V.P.S. (2011-03-26)
>> '''
>> from mpl_toolkits.mplot3d import Axes3D
>> from matplotlib.collections import LineCollection
>> from matplotlib.colors import colorConverter
>> import matplotlib.pyplot as plt
>> import numpy as np
>>
>> np.random.seed(40040157) # Used to allow repeatable experiments (plots)
>>
>> fig = plt.figure()
>> ax = fig.gca(projection='3d')
>>
>> cc = [colorConverter.to_rgba(c,alpha=0.6) for c in
>> ('r','g','b','c','y','m','k')]
>> ncc = len(cc)
>>
>> nxs = 5      # Num of points to connect (nxs-1 line segments)
>> # Generate X values
>> xs = np.arange(1, nxs+1, 1)
>>
>> # Create array of Y values (to be updated)
>> ys = np.zeros(nxs)
>>
>> # Create list of Z values
>> nzs = 4      # Num of Z-planes
>> zs = [zs+1 for zs in range(nzs)]
>>
>> # Create list of colors (cyclic) for lines
>> colorlist = [cc[j%ncc] for j in range(nzs)]
>>
>> segs = []
>> # Generate line segments in each Z-plane
>> for j in zs:
>>     ys = np.random.rand(nxs)
>>     segs.append(zip(xs, ys))
>>
>> curves = LineCollection(segs, colors = colorlist)
>>
>> ax.add_collection3d(curves, zs=zs, zdir='y')
>>
>> ax.set_xlabel('X')         # points to right     -- X
>> ax.set_xlim3d(0, nxs+1)
>> ax.set_ylabel('Y')         # points into screen  -- Y
>> ax.set_ylim3d(0, nzs+1)
>> ax.set_zlabel('Z')         # points up           -- Z
>> ax.set_zlim3d(0, 1)
>>
>> plt.show()
>>
>> Have a Good Day
>> --V
>>
>>
> Virgil,
>
> Thanks for noticing this.  There are several missing methods in the various
> 3D collections and artists, and I am sure we haven't found them all yet.  I
> am currently too busy to investigate why this particular one was missing,
> but in about a month I will have some time to do so.
>
> Ben Root
>
>

Virgil,

I have verified your observations, and the patch was added to the master
branch.  I tried to attribute the patch to you, but I don't think I did it
correctly.

Thanks,
Ben Root

Based on this and some other comments I've made the minimum compatible 
version 1.0.3.

Anyone wishing to test can use the nightly builds here: 
http://www.pyside.org/files/nightly/ or just wait for next months 
release.  There's also compiling the PySide source or removing the 
version check too.

Gerald.

On 6/05/2011 4:32 PM, David Trémouilles wrote:
> Hello,
>
> This is not directly related to your patch but I would like to
> report here that I still have at least one issue on MacOs
> that prevent matplotlib to work with your pyside backend.
> Indeed current PySide version (1.0.2) have a bug on MacOS that seems to
> have been fixed recently:
> http://bugs.pyside.org/show_bug.cgi?id=809
> But I will have to wait for next PySide release to
> confirm your pyside patch works on MacOs.
> Will test as soon as next pyside version is out and available on
> macports. I do not have time nor will to test with the latest current
> pyside head.
>
> Regards,
>
> David
>
>
>
> Le 06/05/11 03:36, Gerald Storer a écrit :
>> Hi,
>> I was wondering if I could get a comment on this.  Its been 4 weeks
>> since I submitted the original version and it has been more or less
>> production ready since Monday.
>>
>> https://github.com/matplotlib/matplotlib/pull/80
>>
>> Thanks,
>> Gerald.
>>
>> On 11/04/2011 4:49 PM, Gerald Storer wrote:
>>> Hi,
>>> I've submitted a pull request with backend changes that (should) let
>>> all currently supported versions of PyQt work along side PySide.  I've
>>> tested with PyQt 4.8.3 and PySide 1.0.0.
>>>
>>> I haven't bothered chasing down old versions of PyQt as they seem
>>> elusive.
>>>
>>> Gerald.
>>>
>>> On 29/03/2011 3:25 AM, bu...@gm... wrote:
>>>> Looking forward, supporting the Python 3 compatible PyQt API is
>>>> likely the way to go.
>>>>
>>>> Le , Gerald Storer<gd...@mr...>   a écrit :
>>>>> On 28/03/2011 1:10 AM, Peter Butterworth wrote:
>>>>>
>>>>>
>>>>> Wouldn't it be possible to use a single backend compatible with both
>>>>>
>>>>> PyQt and Pyside ?
>>>>>
>>>>>
>>>>> The current Qt mpl backend uses the old PyQt slots/signals API
>>>> which PySide doesn't really support (there are some macros but they
>>>> don't work 100% the same).  From a quick glance at the IPython
>>>> implementation it looks like they are using the new API which means
>>>> older versions (<4.5) of PyQt won't be supported. This might be ok, I
>>>> don't know.
>>>>> If it isn't then, there will need to be some try...excepts around
>>>> the place or separate back ends.  If you ignore the PySide bugs I had
>>>> to work around I've only changed ~4 lines in the main backend.
>>>>>
>>>>>
>>>>> Pierre's formlayout is also using an obsolete method that isn't
>>>> present in PySide.  I've opted to emulate it, but it would be best to
>>>> change the code to use the alternative method available in both PyQt
>>>> and PySide.  formlayout also uses the old QString implementation of
>>>> PyQt, PySide only supports the new implementation where QString is
>>>> transparently convert to/from str/unicode.  Setting QString = unicode
>>>> seems to work though.
>>>>>
>>>>>
>>>>> Gerald.
>>>>>
>>
>>
>> ------------------------------------------------------------------------------
>> WhatsUp Gold - Download Free Network Management Software
>> The most intuitive, comprehensive, and cost-effective network
>> management toolset available today.  Delivers lowest initial
>> acquisition cost and overall TCO of any competing solution.
>> http://p.sf.net/sfu/whatsupgold-sd
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

I've been trying to run the matplotlib test suite but the docs seem  
incomplete on this subject.

>> http://matplotlib.github.com/devel/coding_guide.html#running-the-tests
Running the tests is simple. Make sure you have nose installed and type  
from within Python:
import matplotlib
matplotlib.test()
To run a single test from the command line, you can provide a dot-separated  
path to the module and function, eg. (this is assuming the test is  
installed):
nosetests matplotlib.tests.test_simplification:test_clipping



Most test fail when I do what is suggested because PIL is not installed and  
is a requirement for all image_comparison tests.

A bit more information in the docs would be helpful for first time testers.
IMO the optional dependencies required for running the test suite should be  
listed (possibly in the installation guide:
>> http://matplotlib.github.com/users/installing.html )
and info should be provided on how to run only the tests that don't require  
PIL.



>> matplotlib.test()
...
======================================================================
ERROR: matplotlib.tests.test_mathtext.test_mathtext_stixsans
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\Python26\lib\site-packages\nose-1.0.0-py2.6.egg\nose\case.py",  
line 187, in runTest
self.test(*self.arg)
File "C:\Python26\lib\site-packages\matplotlib\testing\decorators.py", line  
32, in failer
result = f(*args, **kwargs)
File "C:\Python26\lib\site-packages\matplotlib\testing\decorators.py", line  
122, in decorated_co
mpare_images
in_decorator=True )
File "C:\Python26\lib\site-packages\matplotlib\testing\compare.py", line  
187, in compare_images
raise NotImplementedError, e
NotImplementedError: No module named PIL

----------------------------------------------------------------------
Ran 150 tests in 143.964s

FAILED (KNOWNFAIL=2, errors=133)
Out[4]: False

On Tue, May 10, 2011 at 12:48 PM, Benjamin Root <ben...@ou...> wrote:

>
>
>
> The one thing I am confused about is what file to edit for the main page.
> I must be very dense because I just simply can not figure out where the main
> page is generated from.  I have been meaning to fix some things on the front
> page for a while now, but have been too afraid to ask.
>

see doc/_templates/*.html

After you have integrated the pull request into the 1.0.x branch (which is
what I build the website from) I'll build and push it to the sf site.

On Tue, May 10, 2011 at 12:42 PM, Jason Grout
<jas...@cr...>wrote:

> On 5/10/11 9:43 AM, Ben Gamari wrote:
> > The website is quite out of date. Not only does it claim that the latest
> > release is 1.0.0, but the link to the github repository appears to be
> > broken (has unneeded .git at the end of it).
> >
>
> Is the website itself in the git repository?  If so, I suppose someone
> could just fork it and make a pull request.
>
> Jason
>
>
The documentation is a part of the matplotlib package.  The website is
generated from that information and uploaded to the sourceforge site.  I
have been doing some work on other pages (see
https://github.com/matplotlib/matplotlib/pull/102 ).  Please use this branch
of mine to make small changes so that we can bring all of the changes into
the docs at once.

The one thing I am confused about is what file to edit for the main page.  I
must be very dense because I just simply can not figure out where the main
page is generated from.  I have been meaning to fix some things on the front
page for a while now, but have been too afraid to ask.

Ben Root

On 5/10/11 9:43 AM, Ben Gamari wrote:
> The website is quite out of date. Not only does it claim that the latest
> release is 1.0.0, but the link to the github repository appears to be
> broken (has unneeded .git at the end of it).
>

Is the website itself in the git repository?  If so, I suppose someone 
could just fork it and make a pull request.

Jason

The website is quite out of date. Not only does it claim that the latest
release is 1.0.0, but the link to the github repository appears to be
broken (has unneeded .git at the end of it).

Cheers,

- Ben

Michael Droettboom-3 wrote:
> 
> There is a fix in this pull request.
> 
> https://github.com/matplotlib/matplotlib/pull/106
> 
> Can you confirm it works for you?
> 

For me that only moved the problem further a little, I got the error:

AttributeError: FigureManagerGTKAgg instance has no attribute 'toolbar'

Which was solved by changing the line after your fix to be: 

if hasattr(self, 'toolbar') and self.toolbar:

This then seems to run fine.
-- 
View this message in context: http://old.nabble.com/figure-error-during-python-shutdown-tp31554255p31565516.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

I think this might have existed for a long time, but there just hasn't 
been much testing running Gtk without opening windows.

There is a fix in this pull request.

https://github.com/matplotlib/matplotlib/pull/106

Can you confirm it works for you?

Mike

On 05/05/2011 05:17 PM, Benjamin Root wrote:
> There seems to be an odd error that comes up when exiting python after 
> using matplotlib with gtkagg backend.  I only notice this error if I 
> do not display the figure (i.e., only saving figures in a headless 
> mode) and during the test.  Also, this is with matplotlib master 
> branch.  I have not tested this with any other branch.  Here is the 
> error message:
>
> Error in atexit._run_exitfuncs:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
>     func(*targs, **kargs)
>   File 
> "/home/bvr/Programs/matplotlib/lib/matplotlib/_pylab_helpers.py", line 
> 82, in destroy_all
>     manager.destroy()
>   File 
> "/home/bvr/Programs/matplotlib/lib/matplotlib/backends/backend_gtk.py", line 
> 552, in destroy
>     self.canvas.destroy()
> AttributeError: FigureManagerGTKAgg instance has no attribute 'canvas'
> Error in sys.exitfunc:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
>     func(*targs, **kargs)
>   File 
> "/home/bvr/Programs/matplotlib/lib/matplotlib/_pylab_helpers.py", line 
> 82, in destroy_all
>     manager.destroy()
>   File 
> "/home/bvr/Programs/matplotlib/lib/matplotlib/backends/backend_gtk.py", line 
> 552, in destroy
>     self.canvas.destroy()
> AttributeError: FigureManagerGTKAgg instance has no attribute 'canvas'
>
>
> This happens with both python 2.6 and 2.7.  I have not tested any 
> other version.
>
> Ben Root
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

I've added some comments and tested against PyQt4 4.7.3 -- I don't have 
PySide installed, so I'll just assume it works there, too.

Cheers,
Mike

On 05/05/2011 09:36 PM, Gerald Storer wrote:
> Hi,
> I was wondering if I could get a comment on this.  Its been 4 weeks
> since I submitted the original version and it has been more or less
> production ready since Monday.
>
> https://github.com/matplotlib/matplotlib/pull/80
>
> Thanks,
> Gerald.
>
> On 11/04/2011 4:49 PM, Gerald Storer wrote:
>    
>> Hi,
>> I've submitted a pull request with backend changes that (should) let
>> all currently supported versions of PyQt work along side PySide.  I've
>> tested with PyQt 4.8.3 and PySide 1.0.0.
>>
>> I haven't bothered chasing down old versions of PyQt as they seem
>> elusive.
>>
>> Gerald.
>>
>> On 29/03/2011 3:25 AM, bu...@gm... wrote:
>>      
>>> Looking forward, supporting the Python 3 compatible PyQt API is
>>> likely the way to go.
>>>
>>> Le , Gerald Storer<gd...@mr...>  a écrit :
>>>        
>>>> On 28/03/2011 1:10 AM, Peter Butterworth wrote:
>>>>
>>>>
>>>> Wouldn't it be possible to use a single backend compatible with both
>>>>
>>>> PyQt and Pyside ?
>>>>
>>>>
>>>> The current Qt mpl backend uses the old PyQt slots/signals API
>>>>          
>>> which PySide doesn't really support (there are some macros but they
>>> don't work 100% the same).  From a quick glance at the IPython
>>> implementation it looks like they are using the new API which means
>>> older versions (<4.5) of PyQt won't be supported. This might be ok, I
>>> don't know.
>>>        
>>>> If it isn't then, there will need to be some try...excepts around
>>>>          
>>> the place or separate back ends.  If you ignore the PySide bugs I had
>>> to work around I've only changed ~4 lines in the main backend.
>>>        
>>>>
>>>>
>>>> Pierre's formlayout is also using an obsolete method that isn't
>>>>          
>>> present in PySide.  I've opted to emulate it, but it would be best to
>>> change the code to use the alternative method available in both PyQt
>>> and PySide.  formlayout also uses the old QString implementation of
>>> PyQt, PySide only supports the new implementation where QString is
>>> transparently convert to/from str/unicode.  Setting QString = unicode
>>> seems to work though.
>>>        
>>>>
>>>>
>>>> Gerald.
>>>>
>>>>          
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>    


-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

Hello,

This is not directly related to your patch but I would like to
report here that I still have at least one issue on MacOs
that prevent matplotlib to work with your pyside backend.
Indeed current PySide version (1.0.2) have a bug on MacOS that seems to 
have been fixed recently:
http://bugs.pyside.org/show_bug.cgi?id=809
But I will have to wait for next PySide release to
confirm your pyside patch works on MacOs.
Will test as soon as next pyside version is out and available on 
macports. I do not have time nor will to test with the latest current
pyside head.

Regards,

David



Le 06/05/11 03:36, Gerald Storer a écrit :
> Hi,
> I was wondering if I could get a comment on this.  Its been 4 weeks
> since I submitted the original version and it has been more or less
> production ready since Monday.
>
> https://github.com/matplotlib/matplotlib/pull/80
>
> Thanks,
> Gerald.
>
> On 11/04/2011 4:49 PM, Gerald Storer wrote:
>> Hi,
>> I've submitted a pull request with backend changes that (should) let
>> all currently supported versions of PyQt work along side PySide.  I've
>> tested with PyQt 4.8.3 and PySide 1.0.0.
>>
>> I haven't bothered chasing down old versions of PyQt as they seem
>> elusive.
>>
>> Gerald.
>>
>> On 29/03/2011 3:25 AM, bu...@gm... wrote:
>>> Looking forward, supporting the Python 3 compatible PyQt API is
>>> likely the way to go.
>>>
>>> Le , Gerald Storer<gd...@mr...>  a écrit :
>>>> On 28/03/2011 1:10 AM, Peter Butterworth wrote:
>>>>
>>>>
>>>> Wouldn't it be possible to use a single backend compatible with both
>>>>
>>>> PyQt and Pyside ?
>>>>
>>>>
>>>> The current Qt mpl backend uses the old PyQt slots/signals API
>>> which PySide doesn't really support (there are some macros but they
>>> don't work 100% the same).  From a quick glance at the IPython
>>> implementation it looks like they are using the new API which means
>>> older versions (<4.5) of PyQt won't be supported. This might be ok, I
>>> don't know.
>>>>
>>>> If it isn't then, there will need to be some try...excepts around
>>> the place or separate back ends.  If you ignore the PySide bugs I had
>>> to work around I've only changed ~4 lines in the main backend.
>>>>
>>>>
>>>>
>>>> Pierre's formlayout is also using an obsolete method that isn't
>>> present in PySide.  I've opted to emulate it, but it would be best to
>>> change the code to use the alternative method available in both PyQt
>>> and PySide.  formlayout also uses the old QString implementation of
>>> PyQt, PySide only supports the new implementation where QString is
>>> transparently convert to/from str/unicode.  Setting QString = unicode
>>> seems to work though.
>>>>
>>>>
>>>>
>>>> Gerald.
>>>>
>
>
>
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network
> management toolset available today.  Delivers lowest initial
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Hi,
I was wondering if I could get a comment on this.  Its been 4 weeks 
since I submitted the original version and it has been more or less 
production ready since Monday.

https://github.com/matplotlib/matplotlib/pull/80

Thanks,
Gerald.

On 11/04/2011 4:49 PM, Gerald Storer wrote:
> Hi,
> I've submitted a pull request with backend changes that (should) let 
> all currently supported versions of PyQt work along side PySide.  I've 
> tested with PyQt 4.8.3 and PySide 1.0.0.
>
> I haven't bothered chasing down old versions of PyQt as they seem 
> elusive.
>
> Gerald.
>
> On 29/03/2011 3:25 AM, bu...@gm... wrote:
>> Looking forward, supporting the Python 3 compatible PyQt API is 
>> likely the way to go.
>>
>> Le , Gerald Storer <gd...@mr...> a écrit :
>> > On 28/03/2011 1:10 AM, Peter Butterworth wrote:
>> >
>> >
>> > Wouldn't it be possible to use a single backend compatible with both
>> >
>> > PyQt and Pyside ?
>> >
>> >
>> > The current Qt mpl backend uses the old PyQt slots/signals API 
>> which PySide doesn't really support (there are some macros but they 
>> don't work 100% the same).  From a quick glance at the IPython 
>> implementation it looks like they are using the new API which means 
>> older versions (<4.5) of PyQt won't be supported. This might be ok, I 
>> don't know.
>> >
>> > If it isn't then, there will need to be some try...excepts around 
>> the place or separate back ends.  If you ignore the PySide bugs I had 
>> to work around I've only changed ~4 lines in the main backend.
>> >
>> >
>> >
>> > Pierre's formlayout is also using an obsolete method that isn't 
>> present in PySide.  I've opted to emulate it, but it would be best to 
>> change the code to use the alternative method available in both PyQt 
>> and PySide.  formlayout also uses the old QString implementation of 
>> PyQt, PySide only supports the new implementation where QString is 
>> transparently convert to/from str/unicode.  Setting QString = unicode 
>> seems to work though.
>> >
>> >
>> >
>> > Gerald.
>> > 

There seems to be an odd error that comes up when exiting python after using
matplotlib with gtkagg backend.  I only notice this error if I do not
display the figure (i.e., only saving figures in a headless mode) and during
the test.  Also, this is with matplotlib master branch.  I have not tested
this with any other branch.  Here is the error message:

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/home/bvr/Programs/matplotlib/lib/matplotlib/_pylab_helpers.py",
line 82, in destroy_all
    manager.destroy()
  File
"/home/bvr/Programs/matplotlib/lib/matplotlib/backends/backend_gtk.py", line
552, in destroy
    self.canvas.destroy()
AttributeError: FigureManagerGTKAgg instance has no attribute 'canvas'
Error in sys.exitfunc:
Traceback (most recent call last):
  File "/usr/lib/python2.6/atexit.py", line 24, in _run_exitfuncs
    func(*targs, **kargs)
  File "/home/bvr/Programs/matplotlib/lib/matplotlib/_pylab_helpers.py",
line 82, in destroy_all
    manager.destroy()
  File
"/home/bvr/Programs/matplotlib/lib/matplotlib/backends/backend_gtk.py", line
552, in destroy
    self.canvas.destroy()
AttributeError: FigureManagerGTKAgg instance has no attribute 'canvas'


This happens with both python 2.6 and 2.7.  I have not tested any other
version.

Ben Root

See enclosed the python file of my code.
The code is not a professional one because i just start python and matplotlib.

Thanks,

Naga




________________________________
De : John Hunter <jd...@gm...>
À : Clyng11 <cou...@ya...>
Cc : mat...@li...
Envoyé le : Sam 30 avril 2011, 22h 45min 22s
Objet : Re: [matplotlib-devel] displaying ticklabels on a graph

On Wed, Apr 27, 2011 at 4:17 AM, Clyng11 <cou...@ya...> wrote:
>
> I run this code, but labels do not appear under the ticks.
>
>      # label the X ticks with years
>      self.mpl.canvas.ax.set_xticks(np.arange(len(years))+width/2,
> [int(year) for year in years])
>      self.mpl.canvas.ax.set_xticklabels([str(year) for year in years])
>
> I Need an help.


Could you post a complete, free-standing example that we can run that
exposes your problem?