SourceForge logo
SourceForge logo
Menu

matplotlib-devel — matplotlib developers

You can subscribe to this list here.

2003 Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
(1)
Nov
(33)
Dec
(20)
2004 Jan
(7)
Feb
(44)
Mar
(51)
Apr
(43)
May
(43)
Jun
(36)
Jul
(61)
Aug
(44)
Sep
(25)
Oct
(82)
Nov
(97)
Dec
(47)
2005 Jan
(77)
Feb
(143)
Mar
(42)
Apr
(31)
May
(93)
Jun
(93)
Jul
(35)
Aug
(78)
Sep
(56)
Oct
(44)
Nov
(72)
Dec
(75)
2006 Jan
(116)
Feb
(99)
Mar
(181)
Apr
(171)
May
(112)
Jun
(86)
Jul
(91)
Aug
(111)
Sep
(77)
Oct
(72)
Nov
(57)
Dec
(51)
2007 Jan
(64)
Feb
(116)
Mar
(70)
Apr
(74)
May
(53)
Jun
(40)
Jul
(519)
Aug
(151)
Sep
(132)
Oct
(74)
Nov
(282)
Dec
(190)
2008 Jan
(141)
Feb
(67)
Mar
(69)
Apr
(96)
May
(227)
Jun
(404)
Jul
(399)
Aug
(96)
Sep
(120)
Oct
(205)
Nov
(126)
Dec
(261)
2009 Jan
(136)
Feb
(136)
Mar
(119)
Apr
(124)
May
(155)
Jun
(98)
Jul
(136)
Aug
(292)
Sep
(174)
Oct
(126)
Nov
(126)
Dec
(79)
2010 Jan
(109)
Feb
(83)
Mar
(139)
Apr
(91)
May
(79)
Jun
(164)
Jul
(184)
Aug
(146)
Sep
(163)
Oct
(128)
Nov
(70)
Dec
(73)
2011 Jan
(235)
Feb
(165)
Mar
(147)
Apr
(86)
May
(74)
Jun
(118)
Jul
(65)
Aug
(75)
Sep
(162)
Oct
(94)
Nov
(48)
Dec
(44)
2012 Jan
(49)
Feb
(40)
Mar
(88)
Apr
(35)
May
(52)
Jun
(69)
Jul
(90)
Aug
(123)
Sep
(112)
Oct
(120)
Nov
(105)
Dec
(116)
2013 Jan
(76)
Feb
(26)
Mar
(78)
Apr
(43)
May
(61)
Jun
(53)
Jul
(147)
Aug
(85)
Sep
(83)
Oct
(122)
Nov
(18)
Dec
(27)
2014 Jan
(58)
Feb
(25)
Mar
(49)
Apr
(17)
May
(29)
Jun
(39)
Jul
(53)
Aug
(52)
Sep
(35)
Oct
(47)
Nov
(110)
Dec
(27)
2015 Jan
(50)
Feb
(93)
Mar
(96)
Apr
(30)
May
(55)
Jun
(83)
Jul
(44)
Aug
(8)
Sep
(5)
Oct
Nov
(1)
Dec
(1)
2016 Jan
Feb
Mar
(1)
Apr
May
Jun
(2)
Jul
Aug
(3)
Sep
(1)
Oct
(3)
Nov
Dec
2017 Jan
Feb
(5)
Mar
Apr
May
Jun
Jul
(3)
Aug
Sep
(7)
Oct
Nov
Dec
2018 Jan
Feb
Mar
Apr
May
Jun
Jul
(2)
Aug
Sep
Oct
Nov
Dec
S M T W T F S



1
(10)
2
(4)
3
(11)
4
(4)
5
(6)
6
(8)
7
(7)
8
(9)
9
(6)
10
11
12
(7)
13
(6)
14
(18)
15
(13)
16
(7)
17
(15)
18
(1)
19
20
(1)
21
(2)
22
(5)
23
(3)
24
(4)
25
(1)
26
27
(8)
28
(2)
29
(5)
30


Showing 4 results of 4

From: Fernando P. <fpe...@gm...> - 2010年09月04日 03:28:31
On Fri, Sep 3, 2010 at 6:57 PM, Eric Firing <ef...@ha...> wrote:
> It's not quite that simple. After some initial thrashing around, I
> installed zmq from source, and then pyzmq--but I can't import zmq:
>
Mhh, sorry to see you burn up on this, Eric. Brian is the zmq expert,
not me, but it *may* be a version compatibility issue, perhaps? I am
using these versions of zmq/pyzmq:
- zmq 2.0.8: http://www.zeromq.org/local--files/area:download/zeromq-2.0.8.tar.gz
- pyzmq 2.0.7: http://github.com/downloads/zeromq/pyzmq/pyzmq-2.0.7.tar.gz
These two worked fine for me, with:
- for zmq:
./configure --prefix=$HOME/usr/opt
make && make install
note that $HOME/usr/opt/lib is in my LD_LIBRARY_PATH, and the include/
dir in my include path, etc.
- for pyzmq:
python setup.py install --prefix=$HOME/usr/opt
And at that point it just worked. A few questions:
- is it possible that you did a build from the head of either
zmq/pyzmq git tree? that might cause an incompatibility.
- could it be that /usr/local/lib isn in your LD_LIBRARY_PATH?
I'll be available over the weekend and will be more than happy to try
and help sort this out.
Regards, and sorry for the hassle
f
From: Brian G. <ell...@gm...> - 2010年09月04日 03:25:45
Eric,
Looks like you are on Linux. If so, you will have to make sure you do
two things before doing python setup.py install on pyzmq:
1. Edit the setup.cfg (copy the template) to point to your zeromq install.
2. Use the --rpath option:
python setup.py build_ext --rpath=/opt/zeromq-dev/lib --inplace
Alternatively, you can set the LD_LIBRARY_PATH to point to your zeromq lib path.
Also, for now, we suggest using the stable 2.0.7 releases of both
pyzmq and zeromq.
Sorry about the hitches, parts of this are definitely still rough and
we hope to iron out these things. I should mention that zeromq/pyzmq
are only required for the new Qt gui, the old terminal ipython doesn't
require them.
Let us know if you run into any other issues.
Cheers,
Brian
On Fri, Sep 3, 2010 at 6:57 PM, Eric Firing <ef...@ha...> wrote:
> On 09/03/2010 12:37 PM, Brian Granger wrote:
>> Hello all,
>>
>> I would like to submit the following branch on github for review and
>> merging into matplotlib trunk:
>>
>> http://github.com/ellisonbg/matplotlib/commits/guisupport
>>
>> This branch implements the logic needed for the qt4 and wx backends to
>> fully work with the upcoming IPython 0.11 release. In our testing we
>> have run many of the mpl examples (including the new animation
>> examples) in both qt4/wx in both the terminal based IPython and the
>> new IPython Qt GUI. For background on these changes please see this
>> thread:
>>
>> http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTik2SNtXMaezCc0UiMnCYg6LxwEL1eN9YASnmOua%40mail.gmail.com&forum_name=matplotlib-devel
>>
>> It is important to note that we have not updated the other matplotlib
>> backends (gtk, tk, etc.) to have this logic. This is mainly because
>> we know almost nothing about these toolkits and could really use some
>> help from folks who are experts at the respective toolkits. We have
>> done some minimal testing and these other backends do work for simple
>> examples in the terminal IPython, but they won't work in all cases and
>> will definitely not work in the new IPython Qt based GUI.
>>
>> We would love feedback and help testing as these changes are
>> significant (even though only a few lines of code). To test this
>> stuff you will need to grab the following IPython development branch:
>>
>> http://github.com/ipython/ipython/tree/newkernel
>>
>> You should be able to run the examples in regular ipython:
>>
>> ipython --pylab qt4|wx
>>
>> Or the new GUI
>>
>> ipythonqt --pylab qt4|wx
>>
>
> Brian and others,
>
> It's not quite that simple. After some initial thrashing around, I
> installed zmq from source, and then pyzmq--but I can't import zmq:
>
> In [1]: import zmq
> ---------------------------------------------------------------------------
> ImportError                Traceback (most recent call last)
> /home/efiring/<ipython console> in <module>()
>
> /usr/local/lib/python2.6/dist-packages/zmq/__init__.py in <module>()
>   24
> #-----------------------------------------------------------------------------
>
>   25
> ---> 26 from zmq import _zmq
>   27 from zmq._zmq import *
>   28
>
> ImportError: libzmq.so.0: cannot open shared object file: No such file
> or directory
>
> But it is right where it should be:
>
> efiring@manini:~/programs/py/ipython/pyzmq_git$ ll /usr/local/lib/libzmq*
> -rw-r--r-- 1 root root 4736930 2010年09月03日 14:35 /usr/local/lib/libzmq.a
> -rwxr-xr-x 1 root root   825 2010年09月03日 14:35 /usr/local/lib/libzmq.la
> lrwxrwxrwx 1 root root   15 2010年09月03日 14:35 /usr/local/lib/libzmq.so
> -> libzmq.so.0.0.0
> lrwxrwxrwx 1 root root   15 2010年09月03日 14:35
> /usr/local/lib/libzmq.so.0 -> libzmq.so.0.0.0
> -rwxr-xr-x 1 root root 1993116 2010年09月03日 14:35
> /usr/local/lib/libzmq.so.0.0.0
>
> And it looks like the extension was built OK, complete with linking:
>
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -I/usr/local/include -I/usr/include/python2.6
> -c zmq/_zmq.c -o build/temp.linux-x86_64-2.6/zmq/_zmq.o
> zmq/_zmq.c:1995: warning: ‘__pyx_doc_3zmq_4_zmq_7Message___len__’
> defined but not used
> gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
> build/temp.linux-x86_64-2.6/zmq/_zmq.o -L/usr/local/lib -lzmq -o
> build/lib.linux-x86_64-2.6/zmq/_zmq.so
>
>
> I'm stumped.
>
> Eric
>
>> Cheers,
>>
>> Brian
>
>
> ------------------------------------------------------------------------------
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
-- 
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
bgr...@ca...
ell...@gm...
From: Jae-Joon L. <lee...@gm...> - 2010年09月04日 03:20:35
On Fri, Sep 3, 2010 at 4:14 AM, Benjamin Root <ben...@ou...> wrote:
> I think there are multiple issues here. Primarially, there is the issue
> that Axes3D is attaching itself to a figure. However, in the interest of
> backwards-compatibility, we can't just fix this outright. There is also the
> issue that there are multiple places in the Figure class that are adding
> axes to the figure object. Ideally, shouldn't we have a single function
> that performs proper checks and adds an axes? Then that function should be
> used in the other class functions to perform this action. In my opinion,
> there is too much duplicated code here.
While I agree that we need to do something with the duplicated code, I
think our priority should be fixing a bug.
The easiest solution (that is backward compatible) seems to be
registering an Axes class that does not add itself to the figure.
For example,
class Axes3DBase(Axes):
 # All of the original Axes3D stuff, but do not add itself to the
figure during the initialization
class Axes3D(Axes3DBase):
 def __init__(self, ...)
 Axes3DBase.__init__(self, ...)
 self.fig.add_axes(self)
# And register Axes3DBase instead of Axes3D
import matplotlib.projections as proj
proj.projection_registry.register(Axes3DBase)
Regards,
-JJ
From: Eric F. <ef...@ha...> - 2010年09月04日 01:57:40
On 09/03/2010 12:37 PM, Brian Granger wrote:
> Hello all,
>
> I would like to submit the following branch on github for review and
> merging into matplotlib trunk:
>
> http://github.com/ellisonbg/matplotlib/commits/guisupport
>
> This branch implements the logic needed for the qt4 and wx backends to
> fully work with the upcoming IPython 0.11 release. In our testing we
> have run many of the mpl examples (including the new animation
> examples) in both qt4/wx in both the terminal based IPython and the
> new IPython Qt GUI. For background on these changes please see this
> thread:
>
> http://sourceforge.net/mailarchive/forum.php?thread_name=AANLkTik2SNtXMaezCc0UiMnCYg6LxwEL1eN9YASnmOua%40mail.gmail.com&forum_name=matplotlib-devel
>
> It is important to note that we have not updated the other matplotlib
> backends (gtk, tk, etc.) to have this logic. This is mainly because
> we know almost nothing about these toolkits and could really use some
> help from folks who are experts at the respective toolkits. We have
> done some minimal testing and these other backends do work for simple
> examples in the terminal IPython, but they won't work in all cases and
> will definitely not work in the new IPython Qt based GUI.
>
> We would love feedback and help testing as these changes are
> significant (even though only a few lines of code). To test this
> stuff you will need to grab the following IPython development branch:
>
> http://github.com/ipython/ipython/tree/newkernel
>
> You should be able to run the examples in regular ipython:
>
> ipython --pylab qt4|wx
>
> Or the new GUI
>
> ipythonqt --pylab qt4|wx
>
Brian and others,
It's not quite that simple. After some initial thrashing around, I 
installed zmq from source, and then pyzmq--but I can't import zmq:
In [1]: import zmq
---------------------------------------------------------------------------
ImportError Traceback (most recent call last)
/home/efiring/<ipython console> in <module>()
/usr/local/lib/python2.6/dist-packages/zmq/__init__.py in <module>()
 24 
#-----------------------------------------------------------------------------
 25
---> 26 from zmq import _zmq
 27 from zmq._zmq import *
 28
ImportError: libzmq.so.0: cannot open shared object file: No such file 
or directory
But it is right where it should be:
efiring@manini:~/programs/py/ipython/pyzmq_git$ ll /usr/local/lib/libzmq*
-rw-r--r-- 1 root root 4736930 2010年09月03日 14:35 /usr/local/lib/libzmq.a
-rwxr-xr-x 1 root root 825 2010年09月03日 14:35 /usr/local/lib/libzmq.la
lrwxrwxrwx 1 root root 15 2010年09月03日 14:35 /usr/local/lib/libzmq.so 
-> libzmq.so.0.0.0
lrwxrwxrwx 1 root root 15 2010年09月03日 14:35 
/usr/local/lib/libzmq.so.0 -> libzmq.so.0.0.0
-rwxr-xr-x 1 root root 1993116 2010年09月03日 14:35 
/usr/local/lib/libzmq.so.0.0.0
And it looks like the extension was built OK, complete with linking:
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -fPIC -I/usr/local/include -I/usr/include/python2.6 
-c zmq/_zmq.c -o build/temp.linux-x86_64-2.6/zmq/_zmq.o
zmq/_zmq.c:1995: warning: ‘__pyx_doc_3zmq_4_zmq_7Message___len__’ 
defined but not used
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
build/temp.linux-x86_64-2.6/zmq/_zmq.o -L/usr/local/lib -lzmq -o 
build/lib.linux-x86_64-2.6/zmq/_zmq.so
I'm stumped.
Eric
> Cheers,
>
> Brian

Showing 4 results of 4

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /