matplotlib-devel Mailing List for matplotlib (Page 3)

On 2013年09月17日 4:14 PM, Damon McDougall wrote:
> On Tue, Sep 17, 2013 at 8:55 PM, Damon McDougall
> <dam...@gm...> wrote:
>> On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing <ef...@ha...> wrote:
>>> When I build mpl from master on python.org python 2.7, Mountain Lion,
>>> and try to plot anything with the macosx backend, I am now getting an
>>> Apple crash--the plot window flashes up and vanishes, and a big OS X
>>> crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have
>>> never seen anything like this before. Building from 1.3.0 works fine.
>>>
>>> Is anyone else seeing this?
>>>
>>> Master is also broken, at least on my machine, with other backends. The
>>> suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
>>>
>>> Eric
>>
>> Building from master produces a broken build of matplotlib for me.
>> After the build finishes, I get this warning from the linker:
>>
>> ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was
>> built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0
>> 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the
>> architecture being linked (i386): /opt/local/lib/libfreetype.dylib
>>
>> I don't know why it's compiling with -arch i386. It's also compiling
>> with -arch x86_64.
>>
>> When I install matplotlib, this is what happens from an ipython terminal:
>>
>> In [1]: import matplotlib
>> In [2]: print matplotlib.__version__
>> 1.4.x
>> In [3]: matplotlib.use('macosx')
>> In [4]: import matplotlib.pyplot as plt
>> In [5]: fig = plt.figure()
>> In [6]: ax = fig.add_subplot(1, 1, 1)
>> In [7]: ax.plot([1, 2, 3])
>> Out[7]: [<matplotlib.lines.Line2D at 0x107523250>]
>> In [8]: plt.show()
>> Trace/BPT trap: 5
>>
>> git bisecting says that f4adec7b569cfd0b30e0f8367ba8618b9e160f92 is
>> the first bad commit, which you can see the diff of
>> here<https://github.com/matplotlib/matplotlib/commit/f4adec7b569cfd0b30e0f8367ba8618b9e160f92>.
>> That's a pretty big commit so it'll take a while to track down.
>>
>> I'm kind of swamped with work right now (a colleague I work with
>> recently resigned) so I don't have as much time as I'd like to
>> dedicate to helping out.
>>
>> Eric, I hope that helps a little bit.
Damon,
More than a little bit, thank you!
Eric
>>
>> Best wishes,
>> Damon
>>
>> --
>> Damon McDougall
>> http://www.damon-is-a-geek.com
>> Institute for Computational Engineering Sciences
>> 201 E. 24th St.
>> Stop C0200
>> The University of Texas at Austin
>> Austin, TX 78712-1229
>
> Oh, and I get the linker warning both with last good commit, *and* the
> first bad commit. Just as another data point.
>

On 2013年09月17日 8:09 PM, Matt Terry wrote:
> My mac testing hasn't picked up on this, but I don't think we have any
> tests that actually draw to the screen. I have noticed a i386 linking
> error, but haven't gotten to it.
>
> Is there an automated way to test this? Something like:
> Make a simple plot
> show()
> close the window after 10s.
Matt,
I don't know--I would think it would be hard to make an automated test 
that can handle a full-on python crash. It leaves behind a screen with 
extensive diagnostics that it says are being sent to Apple.
Eric
>
> -matt
>
> On Sep 17, 2013 7:15 PM, "Damon McDougall" <dam...@gm...
> <mailto:dam...@gm...>> wrote:
>
> On Tue, Sep 17, 2013 at 8:55 PM, Damon McDougall
> <dam...@gm... <mailto:dam...@gm...>> wrote:
> > On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing <ef...@ha...
> <mailto:ef...@ha...>> wrote:
> >> When I build mpl from master on python.org <http://python.org>
> python 2.7, Mountain Lion,
> >> and try to plot anything with the macosx backend, I am now
> getting an
> >> Apple crash--the plot window flashes up and vanishes, and a big OS X
> >> crash report window pops up. Ipython shows "Trace/BPT trap: 5".
> I have
> >> never seen anything like this before. Building from 1.3.0 works
> fine.
> >>
> >> Is anyone else seeing this?
> >>
> >> Master is also broken, at least on my machine, with other
> backends. The
> >> suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
> >>
> >> Eric
> >
> > Building from master produces a broken build of matplotlib for me.
> > After the build finishes, I get this warning from the linker:
> >
> > ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was
> > built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0
> 0x 0
> > 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the
> > architecture being linked (i386): /opt/local/lib/libfreetype.dylib
> >
> > I don't know why it's compiling with -arch i386. It's also compiling
> > with -arch x86_64.
> >
> > When I install matplotlib, this is what happens from an ipython
> terminal:
> >
> > In [1]: import matplotlib
> > In [2]: print matplotlib.__version__
> > 1.4.x
> > In [3]: matplotlib.use('macosx')
> > In [4]: import matplotlib.pyplot as plt
> > In [5]: fig = plt.figure()
> > In [6]: ax = fig.add_subplot(1, 1, 1)
> > In [7]: ax.plot([1, 2, 3])
> > Out[7]: [<matplotlib.lines.Line2D at 0x107523250>]
> > In [8]: plt.show()
> > Trace/BPT trap: 5
> >
> > git bisecting says that f4adec7b569cfd0b30e0f8367ba8618b9e160f92 is
> > the first bad commit, which you can see the diff of
> >
> here<https://github.com/matplotlib/matplotlib/commit/f4adec7b569cfd0b30e0f8367ba8618b9e160f92>.
> > That's a pretty big commit so it'll take a while to track down.
> >
> > I'm kind of swamped with work right now (a colleague I work with
> > recently resigned) so I don't have as much time as I'd like to
> > dedicate to helping out.
> >
> > Eric, I hope that helps a little bit.
> >
> > Best wishes,
> > Damon
> >
> > --
> > Damon McDougall
> > http://www.damon-is-a-geek.com
> > Institute for Computational Engineering Sciences
> > 201 E. 24th St.
> > Stop C0200
> > The University of Texas at Austin
> > Austin, TX 78712-1229
>
> Oh, and I get the linker warning both with last good commit, *and* the
> first bad commit. Just as another data point.
>
> --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power
> Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

My mac testing hasn't picked up on this, but I don't think we have any
tests that actually draw to the screen. I have noticed a i386 linking
error, but haven't gotten to it.
Is there an automated way to test this? Something like:
Make a simple plot
show()
close the window after 10s.
-matt
On Sep 17, 2013 7:15 PM, "Damon McDougall" <dam...@gm...>
wrote:
> On Tue, Sep 17, 2013 at 8:55 PM, Damon McDougall
> <dam...@gm...> wrote:
> > On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing <ef...@ha...> wrote:
> >> When I build mpl from master on python.org python 2.7, Mountain Lion,
> >> and try to plot anything with the macosx backend, I am now getting an
> >> Apple crash--the plot window flashes up and vanishes, and a big OS X
> >> crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have
> >> never seen anything like this before. Building from 1.3.0 works fine.
> >>
> >> Is anyone else seeing this?
> >>
> >> Master is also broken, at least on my machine, with other backends. The
> >> suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
> >>
> >> Eric
> >
> > Building from master produces a broken build of matplotlib for me.
> > After the build finishes, I get this warning from the linker:
> >
> > ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was
> > built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0
> > 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the
> > architecture being linked (i386): /opt/local/lib/libfreetype.dylib
> >
> > I don't know why it's compiling with -arch i386. It's also compiling
> > with -arch x86_64.
> >
> > When I install matplotlib, this is what happens from an ipython terminal:
> >
> > In [1]: import matplotlib
> > In [2]: print matplotlib.__version__
> > 1.4.x
> > In [3]: matplotlib.use('macosx')
> > In [4]: import matplotlib.pyplot as plt
> > In [5]: fig = plt.figure()
> > In [6]: ax = fig.add_subplot(1, 1, 1)
> > In [7]: ax.plot([1, 2, 3])
> > Out[7]: [<matplotlib.lines.Line2D at 0x107523250>]
> > In [8]: plt.show()
> > Trace/BPT trap: 5
> >
> > git bisecting says that f4adec7b569cfd0b30e0f8367ba8618b9e160f92 is
> > the first bad commit, which you can see the diff of
> > here<
> https://github.com/matplotlib/matplotlib/commit/f4adec7b569cfd0b30e0f8367ba8618b9e160f92
> >.
> > That's a pretty big commit so it'll take a while to track down.
> >
> > I'm kind of swamped with work right now (a colleague I work with
> > recently resigned) so I don't have as much time as I'd like to
> > dedicate to helping out.
> >
> > Eric, I hope that helps a little bit.
> >
> > Best wishes,
> > Damon
> >
> > --
> > Damon McDougall
> > http://www.damon-is-a-geek.com
> > Institute for Computational Engineering Sciences
> > 201 E. 24th St.
> > Stop C0200
> > The University of Texas at Austin
> > Austin, TX 78712-1229
>
> Oh, and I get the linker warning both with last good commit, *and* the
> first bad commit. Just as another data point.
>
> --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Tue, Sep 17, 2013 at 8:55 PM, Damon McDougall
<dam...@gm...> wrote:
> On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing <ef...@ha...> wrote:
>> When I build mpl from master on python.org python 2.7, Mountain Lion,
>> and try to plot anything with the macosx backend, I am now getting an
>> Apple crash--the plot window flashes up and vanishes, and a big OS X
>> crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have
>> never seen anything like this before. Building from 1.3.0 works fine.
>>
>> Is anyone else seeing this?
>>
>> Master is also broken, at least on my machine, with other backends. The
>> suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
>>
>> Eric
>
> Building from master produces a broken build of matplotlib for me.
> After the build finishes, I get this warning from the linker:
>
> ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was
> built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0
> 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the
> architecture being linked (i386): /opt/local/lib/libfreetype.dylib
>
> I don't know why it's compiling with -arch i386. It's also compiling
> with -arch x86_64.
>
> When I install matplotlib, this is what happens from an ipython terminal:
>
> In [1]: import matplotlib
> In [2]: print matplotlib.__version__
> 1.4.x
> In [3]: matplotlib.use('macosx')
> In [4]: import matplotlib.pyplot as plt
> In [5]: fig = plt.figure()
> In [6]: ax = fig.add_subplot(1, 1, 1)
> In [7]: ax.plot([1, 2, 3])
> Out[7]: [<matplotlib.lines.Line2D at 0x107523250>]
> In [8]: plt.show()
> Trace/BPT trap: 5
>
> git bisecting says that f4adec7b569cfd0b30e0f8367ba8618b9e160f92 is
> the first bad commit, which you can see the diff of
> here<https://github.com/matplotlib/matplotlib/commit/f4adec7b569cfd0b30e0f8367ba8618b9e160f92>.
> That's a pretty big commit so it'll take a while to track down.
>
> I'm kind of swamped with work right now (a colleague I work with
> recently resigned) so I don't have as much time as I'd like to
> dedicate to helping out.
>
> Eric, I hope that helps a little bit.
>
> Best wishes,
> Damon
>
> --
> Damon McDougall
> http://www.damon-is-a-geek.com
> Institute for Computational Engineering Sciences
> 201 E. 24th St.
> Stop C0200
> The University of Texas at Austin
> Austin, TX 78712-1229
Oh, and I get the linker warning both with last good commit, *and* the
first bad commit. Just as another data point.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On Tue, Sep 17, 2013 at 3:49 PM, Eric Firing <ef...@ha...> wrote:
> When I build mpl from master on python.org python 2.7, Mountain Lion,
> and try to plot anything with the macosx backend, I am now getting an
> Apple crash--the plot window flashes up and vanishes, and a big OS X
> crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have
> never seen anything like this before. Building from 1.3.0 works fine.
>
> Is anyone else seeing this?
>
> Master is also broken, at least on my machine, with other backends. The
> suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
>
> Eric
Building from master produces a broken build of matplotlib for me.
After the build finishes, I get this warning from the linker:
ld: warning: ignoring file /opt/local/lib/libfreetype.dylib, file was
built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0
0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the
architecture being linked (i386): /opt/local/lib/libfreetype.dylib
I don't know why it's compiling with -arch i386. It's also compiling
with -arch x86_64.
When I install matplotlib, this is what happens from an ipython terminal:
In [1]: import matplotlib
In [2]: print matplotlib.__version__
1.4.x
In [3]: matplotlib.use('macosx')
In [4]: import matplotlib.pyplot as plt
In [5]: fig = plt.figure()
In [6]: ax = fig.add_subplot(1, 1, 1)
In [7]: ax.plot([1, 2, 3])
Out[7]: [<matplotlib.lines.Line2D at 0x107523250>]
In [8]: plt.show()
Trace/BPT trap: 5
git bisecting says that f4adec7b569cfd0b30e0f8367ba8618b9e160f92 is
the first bad commit, which you can see the diff of
here<https://github.com/matplotlib/matplotlib/commit/f4adec7b569cfd0b30e0f8367ba8618b9e160f92>.
 That's a pretty big commit so it'll take a while to track down.
I'm kind of swamped with work right now (a colleague I work with
recently resigned) so I don't have as much time as I'd like to
dedicate to helping out.
Eric, I hope that helps a little bit.
Best wishes,
Damon
-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On Tue, Sep 17, 2013 at 8:03 AM, Michael Droettboom <md...@st...> wrote:
> I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1
> release. We have 6 blocker and 12 known bugs on that branch still. I
> hope to devote some time to triaging and closing as many of these as I
> can this week, and then maybe tagging a 1.3.1 release candidate early
> next week. As this is a bugfix release, I'm not feeling extremely
> strict about closing all known bugs tagged 1.3.x -- it's worth closing
> those we can, but anything more complex can wait so as not to delay
> getting out the mass of existing bugfixes already on the branch.
>
> Any thoughts?
>
I like it!
> Mike
>
> --
> _
> |\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
> | ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
>
> http://www.droettboom.com
-- 
Damon McDougall
http://www.damon-is-a-geek.com
Institute for Computational Engineering Sciences
201 E. 24th St.
Stop C0200
The University of Texas at Austin
Austin, TX 78712-1229

On 2013年09月17日 3:03 AM, Michael Droettboom wrote:
> I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1
> release. We have 6 blocker and 12 known bugs on that branch still. I
> hope to devote some time to triaging and closing as many of these as I
> can this week, and then maybe tagging a 1.3.1 release candidate early
> next week. As this is a bugfix release, I'm not feeling extremely
> strict about closing all known bugs tagged 1.3.x -- it's worth closing
> those we can, but anything more complex can wait so as not to delay
> getting out the mass of existing bugfixes already on the branch.
>
> Any thoughts?
Sounds good to me.
Eric
>
> Mike
>

When I build mpl from master on python.org python 2.7, Mountain Lion, 
and try to plot anything with the macosx backend, I am now getting an 
Apple crash--the plot window flashes up and vanishes, and a big OS X 
crash report window pops up. Ipython shows "Trace/BPT trap: 5". I have 
never seen anything like this before. Building from 1.3.0 works fine.
Is anyone else seeing this?
Master is also broken, at least on my machine, with other backends. The 
suggested fix is https://github.com/matplotlib/matplotlib/pull/2431.
Eric

I think there's enough good bug fixes on 1.3.x now to warrant a 1.3.1 
release. We have 6 blocker and 12 known bugs on that branch still. I 
hope to devote some time to triaging and closing as many of these as I 
can this week, and then maybe tagging a 1.3.1 release candidate early 
next week. As this is a bugfix release, I'm not feeling extremely 
strict about closing all known bugs tagged 1.3.x -- it's worth closing 
those we can, but anything more complex can wait so as not to delay 
getting out the mass of existing bugfixes already on the branch.
Any thoughts?
Mike
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Yes, it does appear that the fix needs to be on 1.3.x as well. I'll 
cherry-pick it.
In the meantime, Lorenzo, you can manually include the fix here:
https://github.com/matplotlib/matplotlib/pull/2319
but this will make it into the 1.3.1 release.
Mike
On 09/17/2013 08:36 AM, Thomas A Caswell wrote:
> This is addressed on the master branch via #2319, but the commit where 
> the problem was introduced is not included in 1.3.0, so I am not sure 
> what is going on.
>
> Although, it does look like the fix should be cherry picked to the 
> 1.3.x branch.
>
>
> On Tue, Sep 17, 2013 at 7:02 AM, Lorenzo Di Gregorio 
> <lor...@gm... <mailto:lor...@gm...>> 
> wrote:
>
> Hi,
>
> I've just installed matplotlib 1.3.0 and run into the following
> error when using the "home" button of a figure():
>
> Exception in Tkinter callback
> Traceback (most recent call last):
> File "C:\Python27\lib\lib-tk\Tkinter.py", line 1410, in __call__
> return self.func(*args)
> File
> "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
> 2745, in home
> self._update_view()
> File
> "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
> 3149, in _update_view
> self.draw_idle()
> AttributeError: 'NavigationToolbar2TkAgg' object has no attribute
> 'draw_idle'
>
> In fact NavigationToolbar2, inherited by NavigationToolbas2TkAgg,
> calls draw_idle(), in the update() method, but the definition of
> draw_idle() is missing, so this seems to be a bug.
>
> Best Regards,
> Lorenzo
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power
> Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> -- 
> Thomas A Caswell
> PhD Candidate University of Chicago
> Nagel and Gardel labs
> tca...@uc... <mailto:tca...@uc...>
> jfi.uchicago.edu/~tcaswell <http://jfi.uchicago.edu/%7Etcaswell>
> o: 773.702.7204
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

This is addressed on the master branch via #2319, but the commit where the
problem was introduced is not included in 1.3.0, so I am not sure what is
going on.
Although, it does look like the fix should be cherry picked to the 1.3.x
branch.
On Tue, Sep 17, 2013 at 7:02 AM, Lorenzo Di Gregorio <
lor...@gm...> wrote:
> Hi,
>
> I've just installed matplotlib 1.3.0 and run into the following error when
> using the "home" button of a figure():
>
> Exception in Tkinter callback
> Traceback (most recent call last):
> File "C:\Python27\lib\lib-tk\Tkinter.py", line 1410, in __call__
> return self.func(*args)
> File "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
> 2745, in home
> self._update_view()
> File "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
> 3149, in _update_view
> self.draw_idle()
> AttributeError: 'NavigationToolbar2TkAgg' object has no attribute
> 'draw_idle'
>
> In fact NavigationToolbar2, inherited by NavigationToolbas2TkAgg, calls
> draw_idle(), in the update() method, but the definition of draw_idle() is
> missing, so this seems to be a bug.
>
> Best Regards,
> Lorenzo
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
> SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
-- 
Thomas A Caswell
PhD Candidate University of Chicago
Nagel and Gardel labs
tca...@uc...
jfi.uchicago.edu/~tcaswell
o: 773.702.7204

Hi,
I've just installed matplotlib 1.3.0 and run into the following error when
using the "home" button of a figure():
Exception in Tkinter callback
Traceback (most recent call last):
 File "C:\Python27\lib\lib-tk\Tkinter.py", line 1410, in __call__
 return self.func(*args)
 File "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
2745, in home
 self._update_view()
 File "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
3149, in _update_view
 self.draw_idle()
AttributeError: 'NavigationToolbar2TkAgg' object has no attribute
'draw_idle'
In fact NavigationToolbar2, inherited by NavigationToolbas2TkAgg, calls
draw_idle(), in the update() method, but the definition of draw_idle() is
missing, so this seems to be a bug.
Best Regards,
Lorenzo

Wow. It definitely should be private, or at the very least excluded 
from the docs, through whatever mechanism Sphinx gives us. I really 
hope no one is using that as a public API -- I think it's ok to just 
privatize this post haste without a deprecation period.
Mike
On 09/16/2013 12:39 PM, Benjamin Root wrote:
> While looking up some information, I came across this hideousness:
>
> http://matplotlib.org/api/artist_api.html?highlight=text#matplotlib.text.Text.cached
>
> Why is this member made public? I would have thought it should be 
> "private"?
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just 49ドル.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Hey folks,
While I'm primarily a Vim/Sublime Text kind of guy, my employer provides me
with a Windows machine with Visual Studio and whatnot. So I've been giving
PTVS a shot (https://pytools.codeplex.com/). Seems perfectly nice so far.
But the point is that I just wanted the dev team to know that they've got
an open ticket about their Intellisense/code completion with the pyplot
module:
https://pytools.codeplex.com/workitem/1841
Basic summary is the autogenerated docstrings maybe the culprit.
I'm not suggesting any wholesale changes to MPL to accommodate this. It
just seemed like something y'all might want to know about in case any big
decisions in that area come up.
Note: that in my experience, you get good code completion and tooltips when
working directly with axes objects. So maybe that's all the more reason to
push users away from pyplot?
Cheers and as always, many thanks for the great tools!
-paul

While looking up some information, I came across this hideousness:
http://matplotlib.org/api/artist_api.html?highlight=text#matplotlib.text.Text.cached
Why is this member made public? I would have thought it should be "private"?

On 2013年09月11日 8:49 AM, Filipe Saraiva wrote:
> Em Ter 10 Set 2013 19:21:01 BRT, Christoph Gohlke escreveu:
>> On 9/10/2013 1:54 PM, Eric Firing wrote:
>>> On 2013年09月10日 5:43 AM, Michael Droettboom wrote:
>>>> Do any of those use ctypes? Try creating a minimal ctypes example and
>>>> see if that works.
>>>
>>> Mike,
>>>
>>> I was a bit horrified to see that ctypes import and usage in mpl;
>>> fortunately it is a workaround for a PySide bug, and should only be
>>> temporary, if it should be there at all.
>>>
>>> Eric
>>>
>>
>> Don't be horrified. The Ctypes workaround went trough the mailing list,
>> a PR with discussions including most core developers, testing, several
>> beta/rc/final versions, and real word usage. It fixes a problem that is
>> still present today without it: the Qt4Agg backend is practically
>> unusable with any recent version of PySide on CPython 3.x. Anyway, the
>> Ctypes code could be put in a try/except statement for environments that
>> don't support Ctypes or Python's C API.
>
> If I understood correctly is there a problem with Qt4Agg in matplotlib
> 1.3?
>
> Another KDE developer typed:
>
> import matplotlib
> from matplotlib import pyplot as plt
>
> In my software (Cantor backend for python) and he got the error below:
>
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib/python2.7/site-packages/matplotlib/pyplot.py", line 98,
> in
> _backend_mod, new_figure_manager, draw_if_interactive, _show =
> pylab_setup()
> File
> "/usr/lib/python2.7/site-packages/matplotlib/backends/__init__.py", line
> 25, in pylab_setup
> globals(),locals(),[backend_name])
> File
> "/usr/lib/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
> line 13, in
> from backend_qt4 import QtCore, QtGui, FigureManagerQT, FigureCanvasQT,\
> File
> "/usr/lib/python2.7/site-packages/matplotlib/backends/backend_qt4.py",
> line 25, in
> from qt4_compat import QtCore, QtGui, _getSaveFileName, __version__
> File
> "/usr/lib/python2.7/site-packages/matplotlib/backends/qt4_compat.py",
> line 36, in
> import sip
> ImportError: /usr/lib/python2.7/site-packages/sip.so: undefined symbol:
> PyExc_SystemError
Again, this is a failure of a module to find a Python API symbol. In 
this case, it is not a matplotlib module, it is sip, part of pyqt4. It 
seems like some sort of linking problem.
>
> One more info, I removed matplotlib 1.3 and installed matplotlib 1.2
> using pip and it worked properly. I can use matplotlib in this version.
I'm glad you found something that works; but I don't know why it does.
Eric
>
> Thank you;
>
> --
> Filipe Saraiva
> http://filipesaraiva.info/
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Em Ter 10 Set 2013 19:21:01 BRT, Christoph Gohlke escreveu:
> On 9/10/2013 1:54 PM, Eric Firing wrote:
>> On 2013年09月10日 5:43 AM, Michael Droettboom wrote:
>>> Do any of those use ctypes? Try creating a minimal ctypes example and
>>> see if that works.
>>
>> Mike,
>>
>> I was a bit horrified to see that ctypes import and usage in mpl;
>> fortunately it is a workaround for a PySide bug, and should only be
>> temporary, if it should be there at all.
>>
>> Eric
>>
>
> Don't be horrified. The Ctypes workaround went trough the mailing list,
> a PR with discussions including most core developers, testing, several
> beta/rc/final versions, and real word usage. It fixes a problem that is
> still present today without it: the Qt4Agg backend is practically
> unusable with any recent version of PySide on CPython 3.x. Anyway, the
> Ctypes code could be put in a try/except statement for environments that
> don't support Ctypes or Python's C API.
If I understood correctly is there a problem with Qt4Agg in matplotlib 
1.3?
Another KDE developer typed:
import matplotlib
from matplotlib import pyplot as plt
In my software (Cantor backend for python) and he got the error below:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/matplotlib/pyplot.py", line 98, 
in
_backend_mod, new_figure_manager, draw_if_interactive, _show = 
pylab_setup()
File 
"/usr/lib/python2.7/site-packages/matplotlib/backends/__init__.py", line
25, in pylab_setup
globals(),locals(),[backend_name])
File 
"/usr/lib/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
line 13, in
from backend_qt4 import QtCore, QtGui, FigureManagerQT, FigureCanvasQT,\
File 
"/usr/lib/python2.7/site-packages/matplotlib/backends/backend_qt4.py",
line 25, in
from qt4_compat import QtCore, QtGui, _getSaveFileName, __version__
File 
"/usr/lib/python2.7/site-packages/matplotlib/backends/qt4_compat.py",
line 36, in
import sip
ImportError: /usr/lib/python2.7/site-packages/sip.so: undefined symbol:
PyExc_SystemError
One more info, I removed matplotlib 1.3 and installed matplotlib 1.2 
using pip and it worked properly. I can use matplotlib in this version.
Thank you;
--
Filipe Saraiva
http://filipesaraiva.info/

On 9/10/2013 1:54 PM, Eric Firing wrote:
> On 2013年09月10日 5:43 AM, Michael Droettboom wrote:
>> Do any of those use ctypes? Try creating a minimal ctypes example and
>> see if that works.
>
> Mike,
>
> I was a bit horrified to see that ctypes import and usage in mpl;
> fortunately it is a workaround for a PySide bug, and should only be
> temporary, if it should be there at all.
>
> Eric
>
Don't be horrified. The Ctypes workaround went trough the mailing list, 
a PR with discussions including most core developers, testing, several 
beta/rc/final versions, and real word usage. It fixes a problem that is 
still present today without it: the Qt4Agg backend is practically 
unusable with any recent version of PySide on CPython 3.x. Anyway, the 
Ctypes code could be put in a try/except statement for environments that 
don't support Ctypes or Python's C API.
Christoph

On 2013年09月10日 5:43 AM, Michael Droettboom wrote:
> Do any of those use ctypes? Try creating a minimal ctypes example and
> see if that works.
Mike,
I was a bit horrified to see that ctypes import and usage in mpl; 
fortunately it is a workaround for a PySide bug, and should only be 
temporary, if it should be there at all.
Eric

On 09/10/2013 10:05 AM, Filipe Saraiva wrote:
> Em Ter 10 Set 2013 09:33:37 BRT, Michael Droettboom escreveu:
>> On 09/10/2013 08:23 AM, Filipe Saraiva wrote:
>>> Em Ter 03 Set 2013 17:02:28 BRT, Benjamin Root escreveu:
>>>> On Mon, Sep 2, 2013 at 12:27 AM, Filipe Saraiva
>>>> <ma...@fi... <mailto:ma...@fi...>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> First, thanks for this great library.
>>>>
>>>> My name is Filipe Saraiva, I am developing a python backend for
>>>> Cantor, the KDE mathematical software. More infos can be read in
>>>> http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend (in
>>>> portuguese and english).
>>>>
>>>> Currently I have a problem when I try import pyplot in Cantor. I
>>>> am using Python 2.7.5 and matplotlib 1.3.0. The error is below:
>>>>
>>>> import matplotlib.pyplot as plt
>>>> Traceback (most recent call last):
>>>> File "<string>", line 1, in <module>
>>>> File 
>>>> "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py",
>>>> line 98, in <module>
>>>> _backend_mod, new_figure_manager, draw_if_interactive, 
>>>> _show =
>>>> pylab_setup()
>>>> File
>>>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py",
>>>> line 25, in pylab_setup
>>>> globals(),locals(),[backend_name])
>>>> File
>>>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
>>>> line 19, in <module>
>>>> _decref = ctypes.pythonapi.Py_DecRef
>>>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 378, in
>>>> __getattr__
>>>> func = self.__getitem__(name)
>>>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 383, in
>>>> __getitem__
>>>> func = self._FuncPtr((name_or_ordinal, self))
>>>> AttributeError: kde/bin/cantor: undefined symbol: Py_DecRef
>>>>
>>>> Well, anyone have any idea about how can I fix it?
>>>>
>>>> Thank you,
>>>>
>>>>
>>>> My only guess is that there is some sort of linking/build error.
>>>> Perhaps the python-qt4 library was built and linked against a
>>>> different python on your system?
>>>>
>>>> Cheers!
>>>> Ben Root
>>> Really I don't know. I will question it to matplotlib maintainer.
>>>
>>> The pyplot import in python iteractive mode (python terminal) is
>>> working properly. I can run a matplotlib example using pyplot in this
>>> mode. I get the error just in Python/C API.
>>>
>>
>> It looks like it's failing inside of ctypes. How are you including
>> Python in your application. Perhaps the ctypes module (which is a C
>> extension module that comes in the Python standard library) is not being
>> included or found. I'm at a bit of a loss, but this seems like more of
>> a general "embedding python in a C application" question, which you
>> might try asking on the Python mailing list.
>>
>> Mike
>>
>
> I am using my code with several python modules and I can not get any 
> error. I tried scipy, numpy, Spade, matplotlib... interesting, I don't 
> get error when I import matplotlib.animation.
Do any of those use ctypes? Try creating a minimal ctypes example and 
see if that works.
Mike
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Em Ter 10 Set 2013 09:33:37 BRT, Michael Droettboom escreveu:
> On 09/10/2013 08:23 AM, Filipe Saraiva wrote:
>> Em Ter 03 Set 2013 17:02:28 BRT, Benjamin Root escreveu:
>>> On Mon, Sep 2, 2013 at 12:27 AM, Filipe Saraiva
>>> <ma...@fi... <mailto:ma...@fi...>> wrote:
>>>
>>> Hello,
>>>
>>> First, thanks for this great library.
>>>
>>> My name is Filipe Saraiva, I am developing a python backend for
>>> Cantor, the KDE mathematical software. More infos can be read in
>>> http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend (in
>>> portuguese and english).
>>>
>>> Currently I have a problem when I try import pyplot in Cantor. I
>>> am using Python 2.7.5 and matplotlib 1.3.0. The error is below:
>>>
>>> import matplotlib.pyplot as plt
>>> Traceback (most recent call last):
>>> File "<string>", line 1, in <module>
>>> File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py",
>>> line 98, in <module>
>>> _backend_mod, new_figure_manager, draw_if_interactive, _show =
>>> pylab_setup()
>>> File
>>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py",
>>> line 25, in pylab_setup
>>> globals(),locals(),[backend_name])
>>> File
>>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
>>> line 19, in <module>
>>> _decref = ctypes.pythonapi.Py_DecRef
>>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 378, in
>>> __getattr__
>>> func = self.__getitem__(name)
>>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 383, in
>>> __getitem__
>>> func = self._FuncPtr((name_or_ordinal, self))
>>> AttributeError: kde/bin/cantor: undefined symbol: Py_DecRef
>>>
>>> Well, anyone have any idea about how can I fix it?
>>>
>>> Thank you,
>>>
>>>
>>> My only guess is that there is some sort of linking/build error.
>>> Perhaps the python-qt4 library was built and linked against a
>>> different python on your system?
>>>
>>> Cheers!
>>> Ben Root
>> Really I don't know. I will question it to matplotlib maintainer.
>>
>> The pyplot import in python iteractive mode (python terminal) is
>> working properly. I can run a matplotlib example using pyplot in this
>> mode. I get the error just in Python/C API.
>>
>
> It looks like it's failing inside of ctypes. How are you including
> Python in your application. Perhaps the ctypes module (which is a C
> extension module that comes in the Python standard library) is not being
> included or found. I'm at a bit of a loss, but this seems like more of
> a general "embedding python in a C application" question, which you
> might try asking on the Python mailing list.
>
> Mike
>
I am using my code with several python modules and I can not get any 
error. I tried scipy, numpy, Spade, matplotlib... interesting, I don't 
get error when I import matplotlib.animation.
You can see reports of several uses of python commands and modules in 
my software accessing my blog in 
http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend
Interesting, I used with success pyplot in the first version of this 
backend, last year. The blogpost have a picture of this 
http://blog.filipesaraiva.info/?p=779.
Well, I ask to another KDE developers for test my code and verify if 
the pyplot error that I am getting is reproducible.
Thank you,
--
Filipe Saraiva
http://filipesaraiva.info/

On 09/10/2013 08:23 AM, Filipe Saraiva wrote:
> Em Ter 03 Set 2013 17:02:28 BRT, Benjamin Root escreveu:
>> On Mon, Sep 2, 2013 at 12:27 AM, Filipe Saraiva
>> <ma...@fi... <mailto:ma...@fi...>> wrote:
>>
>> Hello,
>>
>> First, thanks for this great library.
>>
>> My name is Filipe Saraiva, I am developing a python backend for
>> Cantor, the KDE mathematical software. More infos can be read in
>> http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend (in
>> portuguese and english).
>>
>> Currently I have a problem when I try import pyplot in Cantor. I
>> am using Python 2.7.5 and matplotlib 1.3.0. The error is below:
>>
>> import matplotlib.pyplot as plt
>> Traceback (most recent call last):
>> File "<string>", line 1, in <module>
>> File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py",
>> line 98, in <module>
>> _backend_mod, new_figure_manager, draw_if_interactive, _show =
>> pylab_setup()
>> File
>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py",
>> line 25, in pylab_setup
>> globals(),locals(),[backend_name])
>> File
>> "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
>> line 19, in <module>
>> _decref = ctypes.pythonapi.Py_DecRef
>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 378, in
>> __getattr__
>> func = self.__getitem__(name)
>> File "/usr/lib64/python2.7/ctypes/__init__.py", line 383, in
>> __getitem__
>> func = self._FuncPtr((name_or_ordinal, self))
>> AttributeError: kde/bin/cantor: undefined symbol: Py_DecRef
>>
>> Well, anyone have any idea about how can I fix it?
>>
>> Thank you,
>>
>>
>> My only guess is that there is some sort of linking/build error.
>> Perhaps the python-qt4 library was built and linked against a
>> different python on your system?
>>
>> Cheers!
>> Ben Root
> Really I don't know. I will question it to matplotlib maintainer.
>
> The pyplot import in python iteractive mode (python terminal) is
> working properly. I can run a matplotlib example using pyplot in this
> mode. I get the error just in Python/C API.
>
It looks like it's failing inside of ctypes. How are you including 
Python in your application. Perhaps the ctypes module (which is a C 
extension module that comes in the Python standard library) is not being 
included or found. I'm at a bit of a loss, but this seems like more of 
a general "embedding python in a C application" question, which you 
might try asking on the Python mailing list.
Mike
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Em Ter 03 Set 2013 17:02:28 BRT, Benjamin Root escreveu:
>
> On Mon, Sep 2, 2013 at 12:27 AM, Filipe Saraiva
> <ma...@fi... <mailto:ma...@fi...>> wrote:
>
> Hello,
>
> First, thanks for this great library.
>
> My name is Filipe Saraiva, I am developing a python backend for
> Cantor, the KDE mathematical software. More infos can be read in
> http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend (in
> portuguese and english).
>
> Currently I have a problem when I try import pyplot in Cantor. I
> am using Python 2.7.5 and matplotlib 1.3.0. The error is below:
>
> import matplotlib.pyplot as plt
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py",
> line 98, in <module>
> _backend_mod, new_figure_manager, draw_if_interactive, _show =
> pylab_setup()
> File
> "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py",
> line 25, in pylab_setup
> globals(),locals(),[backend_name])
> File
> "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
> line 19, in <module>
> _decref = ctypes.pythonapi.Py_DecRef
> File "/usr/lib64/python2.7/ctypes/__init__.py", line 378, in
> __getattr__
> func = self.__getitem__(name)
> File "/usr/lib64/python2.7/ctypes/__init__.py", line 383, in
> __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: kde/bin/cantor: undefined symbol: Py_DecRef
>
> Well, anyone have any idea about how can I fix it?
>
> Thank you,
>
>
> My only guess is that there is some sort of linking/build error.
> Perhaps the python-qt4 library was built and linked against a
> different python on your system?
>
> Cheers!
> Ben Root
Really I don't know. I will question it to matplotlib maintainer.
The pyplot import in python iteractive mode (python terminal) is 
working properly. I can run a matplotlib example using pyplot in this 
mode. I get the error just in Python/C API.
--
Filipe Saraiva
http://filipesaraiva.info/

Hi everyone!
I'm trying to build matplotlib 1.1.0 using Python-2.7.3 on CentOS 6.4. I
constantly keep getting the following error:
/usr/bin/ld: /usr/local/lib/libpython2.7.a(parsetok.o): relocation
R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared
object; recompile with -fPIC
/usr/local/lib/libpython2.7.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
error: command 'g++' failed with exit status 1
Can anyone please advice on what is going on and how I can resolve the
issue? Thanks a lot.
Regards,
Ali
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/Error-in-building-Matplotlib-tp41968.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

On Mon, Sep 2, 2013 at 12:27 AM, Filipe Saraiva <ma...@fi...>wrote:
> Hello,
>
> First, thanks for this great library.
>
> My name is Filipe Saraiva, I am developing a python backend for Cantor,
> the KDE mathematical software. More infos can be read in
> http://blog.filipesaraiva.info/?tag=gsoc2013-python-backend (in
> portuguese and english).
>
> Currently I have a problem when I try import pyplot in Cantor. I am using
> Python 2.7.5 and matplotlib 1.3.0. The error is below:
>
> import matplotlib.pyplot as plt
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/usr/lib64/python2.7/site-packages/matplotlib/pyplot.py", line 98,
> in <module>
> _backend_mod, new_figure_manager, draw_if_interactive, _show =
> pylab_setup()
> File
> "/usr/lib64/python2.7/site-packages/matplotlib/backends/__init__.py", line
> 25, in pylab_setup
> globals(),locals(),[backend_name])
> File
> "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_qt4agg.py",
> line 19, in <module>
> _decref = ctypes.pythonapi.Py_DecRef
> File "/usr/lib64/python2.7/ctypes/__init__.py", line 378, in __getattr__
> func = self.__getitem__(name)
> File "/usr/lib64/python2.7/ctypes/__init__.py", line 383, in __getitem__
> func = self._FuncPtr((name_or_ordinal, self))
> AttributeError: kde/bin/cantor: undefined symbol: Py_DecRef
>
> Well, anyone have any idea about how can I fix it?
>
> Thank you,
>
>
My only guess is that there is some sort of linking/build error. Perhaps
the python-qt4 library was built and linked against a different python on
your system?
Cheers!
Ben Root