matplotlib-users Mailing List for matplotlib (Page 9)

Thank you Christoph, and thank you for the extensive package builds!
I did update to matplotlib 1.5 and it seems to address the error; I get all
of my plots and they look correct, though I did get the following warning
on Python 2.7.10:
[c:\python\dev\homework1] python PHYS404-homework1-problem3-rev05.py
C:\Python27\lib\site-packages\numpy\core\fromnumeric.py:2648:
RuntimeWarning: invalid value encountered in rint
 return round(decimals, out)
... and the same on CPython 3.4 (do you think 3.5 is stable enough to move
to?):
[c:\python\dev\homework1] python PHYS404-homework1-problem3-rev05.py
C:\Python34\lib\site-packages\numpy\core\fromnumeric.py:2648:
RuntimeWarning: invalid value encountered in rint
 return round(decimals, out)
Many thanks again,
Bobby
On Thu, Sep 17, 2015 at 11:23 PM, <
mat...@li...> wrote:
> Today's Topics:
>
> 1. Re: bug report (Christoph Gohlke)
> 2. Re: bug report (Bobby Wilkins)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: 2015年9月17日 10:30:30 -0700
> From: Christoph Gohlke <cg...@uc...>
> Subject: Re: [Matplotlib-users] bug report
> To: mat...@li...
> Message-ID: <55F...@uc...>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> I can reproduce the AttributeError on all Python versions and the crash
> (in Python's _tkinter.pyd extension) on Python 3.4.
>
> As a workaround you might try to upgrade to matplotlib 1.5, which seems
> to work for me.
>
> Christoph
>
>

One more note: changing the plot type from loglog to just plot, the errors
also go away.
On Thu, Sep 17, 2015 at 11:23 PM, Bobby Wilkins <bob...@gm...>
wrote:
> I installed CPython 2.7.10, and the appropriate versions of the same
> packages, and I still get the same error:
>

I installed CPython 2.7.10, and the appropriate versions of the same
packages, and I still get the same error:
[c:\python\dev\homework1] pip list
backports.ssl-match-hostname (3.4.0.2)
certifi (2015年9月6日.2)
decorator (4.0.2)
functools32 (3.2.3.post2)
ipykernel (4.0.3)
ipyparallel (4.0.2)
ipython (4.0.0)
ipython-genutils (0.1.0)
ipywidgets (4.0.2)
Jinja2 (2.8)
jsonschema (2.5.1)
jupyter (1.0.0)
jupyter-client (4.0.0)
jupyter-console (4.0.2)
jupyter-core (4.0.5)
MarkupSafe (0.23)
matplotlib (1.4.3)
mistune (0.7.1)
nbconvert (4.0.0)
nbformat (4.0.0)
notebook (4.0.4)
numpy (1.9.2)
path.py (8.1.1)
pickleshare (0.5)
Pillow (2.9.0)
pip (7.1.2)
Pygments (2.0.2)
pyparsing (2.0.3)
pyreadline (2.1)
python-dateutil (2.4.2)
pytz (2015.4)
pyzmq (14.7.0)
qtconsole (4.0.0)
scipy (0.16.0)
setuptools (18.3)
simplegeneric (0.8.1)
six (1.9.0)
tornado (4.2.1)
traitlets (4.0.0)
Note: the program does not error if last "if" in the source reads:
if (maxTerm<32)#: or ((myFigBase<4) and (maxTerm<64)):
If I change it to something like this:
if (maxTerm<32) or ((myFigBase<4) and (maxTerm<64)):
... I get the below error:
[c:\python\dev\homework1] python PHYS404-homework1-problem3-rev05.py
Traceback (most recent call last):
 File "PHYS404-homework1-problem3-rev05.py", line 196, in <module>
 graphMyetoNegX(mySlices,myRuns,0,1,0)
 File "PHYS404-homework1-problem3-rev05.py", line 185, in graphMyetoNegX
plt.savefig(figStrName+str(myFigBase*3+3).zfill(2)+figStrExt,bbox_inches='tight')
 File "C:\Python27\lib\site-packages\matplotlib\pyplot.py", line 577, in
savefig
 res = fig.savefig(*args, **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\figure.py", line 1476, in
savefig
 self.canvas.print_figure(*args, **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\backend_bases.py", line
2158, in print_figure
 **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\backends\backend_agg.py",
line 521, in print_png
 FigureCanvasAgg.draw(self)
 File "C:\Python27\lib\site-packages\matplotlib\backends\backend_agg.py",
line 469, in draw
 self.figure.draw(self.renderer)
 File "C:\Python27\lib\site-packages\matplotlib\artist.py", line 59, in
draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\figure.py", line 1085, in
draw
 func(*args)
 File "C:\Python27\lib\site-packages\matplotlib\artist.py", line 59, in
draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\axes\_base.py", line 2110,
in draw
 a.draw(renderer)
 File "C:\Python27\lib\site-packages\matplotlib\artist.py", line 59, in
draw_wrapper
 draw(artist, renderer, *args, **kwargs)
 File "C:\Python27\lib\site-packages\matplotlib\text.py", line 642, in draw
 ismath=ismath, mtext=mtext)
 File "C:\Python27\lib\site-packages\matplotlib\backends\backend_agg.py",
line 206, in draw_text
 font.get_image(), np.round(x - xd), np.round(y + yd) + 1, angle, gc)
 File "C:\Python27\lib\site-packages\numpy\core\fromnumeric.py", line
2648, in round_
 return round(decimals, out)
 File "C:\Python27\lib\site-packages\numpy\ma\core.py", line 4903, in round
 result._mask = self._mask
AttributeError: 'numpy.float64' object has no attribute '_mask'
On Thu, Sep 17, 2015 at 6:46 AM, Bobby Wilkins <bob...@gm...>
wrote:
> Thank you all.
>
> I am using Python 3.4.3.
>
> I meant to include a pip list:
>
> Assimulo (2.8)
> decorator (4.0.2)
> gmpy2 (2.0.7)
> ipykernel (4.0.3)
> ipython (4.0.0)
> ipython-genutils (0.1.0)
> ipywidgets (4.0.2)
> Jinja2 (2.8)
> jsonschema (2.5.1)
> jupyter-client (4.0.0)
> jupyter-core (4.0.4)
> MarkupSafe (0.23)
> matplotlib (1.4.3)
> mistune (0.7.1)
> nbconvert (4.0.0)
> nbformat (4.0.0)
> nose (1.3.7)
> notebook (4.0.4)
> numpy (1.9.2)
> pandas (0.16.2)
> path.py (8.1)
> pickleshare (0.5)
> pip (7.1.2)
> Pygments (2.0.2)
> pyparsing (2.0.3)
> pyreadline (2.0)
> python-dateutil (2.4.2)
> pytz (2015.4)
> pyzmq (14.7.0)
> requests (2.7.0)
> scipy (0.16.0)
> setuptools (18.2)
> simplegeneric (0.8.1)
> six (1.9.0)
> sympy (0.7.6)
> testpath (0.2)
> tornado (4.2.1)
> traitlets (4.0.0)
>
> So, if the program works for Python 2.7 but not 3.4.3, maybe that is the
> problem? Let me try to install Python 2.7 tonight and see what that does.
>
> On Wed, Sep 16, 2015 at 8:39 AM, Sterling Smith <sm...@fu...>
> wrote:
>
>> Works fine for
>>
>> {{{
>> : python
>> Python 2.7.10 (default, Sep 15 2015, 11:26:42)
>> [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> /Users/smithsp/.pyhistory
>> >>> import matplotlib
>> >>> matplotlib.__version__
>> '1.4.3'
>> >>> import numpy
>> >>> numpy.__version__
>> '1.9.2'
>> >>> matplotlib.get_backend()
>> u’MacOSX'
>> }}}
>>
>> All are obtained through MacPorts on OSX 10.9.5.
>>
>> -Sterling
>>
>>
>>
>> On Sep 16, 2015, at 6:50AM, Benjamin Root <ben...@gm...> wrote:
>>
>> > Btw, I can't reproduce the problem using matplotlib master, numpy
>> master and linux. I know it isn't at all similar to your setup, but it is a
>> data point.
>> >
>> > On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...>
>> wrote:
>> > What version of numpy do you have installed?
>> >
>> > On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
>> wrote:
>> > OS: Windows 8.1 Pro
>> >
>> > matplotlib version: 1.4.3
>> >
>> > where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
>> >
>> > customizations: none
>> >
>> > Sample Program: attached py file; this is a Physics homework problem; I
>> have the answers I need, but would like to fix the errors to be able to
>> label all lines.
>> >
>> > Debug output in attached output.txt file
>> >
>> > If you uncomment line 180, the error is reported as if it came from
>> that line even though there is no float64 on that line (savefig). If
>> commented, it does not report a line from my .py file...
>> >
>> > If you make line 170 read as follows, the error goes away:
>> >
>> > if (maxTerm<32):
>> >
>> > This suggests to me that the additional labels for the 32, 64, 128, and
>> 154 term runs is what is triggering the bug, but I cannot figure out what
>> it is.
>> >
>> > Also, separate note, just about any time I make figures, when closing
>> the last figure I get a python.exe app crash and this message:
>> >
>> > alloc: invalid block: 00000000044E7680: 0 d
>> >
>> >
>> > Thank you for any help,
>> > Bobby
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> > Get real-time metrics from all of your servers, apps and tools
>> > in one place.
>> > SourceForge users - Click here to start your Free Trial of Datadog now!
>> > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>> > _______________________________________________
>> > Matplotlib-users mailing list
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> > Get real-time metrics from all of your servers, apps and tools
>> > in one place.
>> > SourceForge users - Click here to start your Free Trial of Datadog now!
>> >
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
>> > Matplotlib-users mailing list
>> > Mat...@li...
>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>

I can reproduce the AttributeError on all Python versions and the crash 
(in Python's _tkinter.pyd extension) on Python 3.4.
As a workaround you might try to upgrade to matplotlib 1.5, which seems 
to work for me.
Christoph
On 9/17/2015 6:46 AM, Bobby Wilkins wrote:
> Thank you all.
>
> I am using Python 3.4.3.
>
> I meant to include a pip list:
>
> Assimulo (2.8)
> decorator (4.0.2)
> gmpy2 (2.0.7)
> ipykernel (4.0.3)
> ipython (4.0.0)
> ipython-genutils (0.1.0)
> ipywidgets (4.0.2)
> Jinja2 (2.8)
> jsonschema (2.5.1)
> jupyter-client (4.0.0)
> jupyter-core (4.0.4)
> MarkupSafe (0.23)
> matplotlib (1.4.3)
> mistune (0.7.1)
> nbconvert (4.0.0)
> nbformat (4.0.0)
> nose (1.3.7)
> notebook (4.0.4)
> numpy (1.9.2)
> pandas (0.16.2)
> path.py (8.1)
> pickleshare (0.5)
> pip (7.1.2)
> Pygments (2.0.2)
> pyparsing (2.0.3)
> pyreadline (2.0)
> python-dateutil (2.4.2)
> pytz (2015.4)
> pyzmq (14.7.0)
> requests (2.7.0)
> scipy (0.16.0)
> setuptools (18.2)
> simplegeneric (0.8.1)
> six (1.9.0)
> sympy (0.7.6)
> testpath (0.2)
> tornado (4.2.1)
> traitlets (4.0.0)
>
> So, if the program works for Python 2.7 but not 3.4.3, maybe that is the
> problem? Let me try to install Python 2.7 tonight and see what that does.
>
> On Wed, Sep 16, 2015 at 8:39 AM, Sterling Smith <sm...@fu...
> <mailto:sm...@fu...>> wrote:
>
> Works fine for
>
> {{{
> : python
> Python 2.7.10 (default, Sep 15 2015, 11:26:42)
> [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> /Users/smithsp/.pyhistory
> >>> import matplotlib
> >>> matplotlib.__version__
> '1.4.3'
> >>> import numpy
> >>> numpy.__version__
> '1.9.2'
> >>> matplotlib.get_backend()
> u’MacOSX'
> }}}
>
> All are obtained through MacPorts on OSX 10.9.5.
>
> -Sterling
>
>
>
> On Sep 16, 2015, at 6:50AM, Benjamin Root <ben...@gm...
> <mailto:ben...@gm...>> wrote:
>
> > Btw, I can't reproduce the problem using matplotlib master, numpy master and linux. I know it isn't at all similar to your setup, but it is a data point.
> >
> > On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm... <mailto:ben...@gm...>> wrote:
> > What version of numpy do you have installed?
> >
> > On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm... <mailto:bob...@gm...>> wrote:
> > OS: Windows 8.1 Pro
> >
> > matplotlib version: 1.4.3
> >
> > where obtained:http://www.lfd.uci.edu/~gohlke/pythonlibs/
> <http://www.lfd.uci.edu/%7Egohlke/pythonlibs/>
> >
> > customizations: none
> >
> > Sample Program: attached py file; this is a Physics homework problem; I have the answers I need, but would like to fix the errors to be able to label all lines.
> >
> > Debug output in attached output.txt file
> >
> > If you uncomment line 180, the error is reported as if it came from that line even though there is no float64 on that line (savefig). If commented, it does not report a line from my .py file...
> >
> > If you make line 170 read as follows, the error goes away:
> >
> > if (maxTerm<32):
> >
> > This suggests to me that the additional labels for the 32, 64, 128, and 154 term runs is what is triggering the bug, but I cannot figure out what it is.
> >
> > Also, separate note, just about any time I make figures, when closing the last figure I get a python.exe app crash and this message:
> >
> > alloc: invalid block: 00000000044E7680: 0 d
> >
> >
> > Thank you for any help,
> > Bobby
> >
> >
> > ------------------------------------------------------------------------------
> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> > Get real-time metrics from all of your servers, apps and tools
> > in one place.
> > SourceForge users - Click here to start your Free Trial of Datadog now!
> >http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> > _______________________________________________
> > Matplotlib-users mailing list
> >Mat...@li...
> <mailto:Mat...@li...>
> >https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
> >
> > ------------------------------------------------------------------------------
> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> > Get real-time metrics from all of your servers, apps and tools
> > in one place.
> > SourceForge users - Click here to start your Free Trial of Datadog now!
> >http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
> > Matplotlib-users mailing list
> >Mat...@li...
> <mailto:Mat...@li...>
> >https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi,
I am trying to install matplotlib on my RedHat Linux 6.5 with Python33.
Unfortunately, 'matplotlib' rpm isn't available for python33. `python-matplotlib` is included only for python2.6 from Red Hat Linux 6.5.
So I try installing the latest module from matplotlib source using 'python easy_install'.
#*scl enable python33 'bash'*
#*easy_install -m matplotlib
*
The install finished fine, but I am still get this error when I tried to import matplotlib. Is there anything else that I need to config?
# scl enable python33 'python'
Python 3.3.2 (default, Mar 20 2014, 20:25:51)
[GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> import scipy
>>> import matplotlib
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
ImportError: No module named 'matplotlib'
Below is the console when I run "easy_install -m matplotlib".
*At the end, it says "Finished processing dependencies for matplotlib". 
Does that mean matplotlib is not really installed yet?*
Do I miss any steps?
****************************************************************************************************************** 
Searching for matplotlib
Reading https://pypi.python.org/simple/matplotlib/
Reading http://matplotlib.org
Reading http://matplotlib.sourceforge.net
Reading http://sourceforge.net/project/showfiles.php?group_id=80706
Reading 
http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474 
Reading 
http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.0/ 
Reading 
http://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ 
Reading 
https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194 
Reading 
https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474 
Reading 
https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/ 
Reading 
https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.3/ 
Reading 
https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.0
Reading 
https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.0.1/ 
Best match: matplotlib 1.4.3
Downloading 
https://pypi.python.org/packages/source/m/matplotlib/matplotlib-1.4.3.tar.gz#md5=86af2e3e3c61849ac7576a6f5ca44267 
Processing matplotlib-1.4.3.tar.gz
Writing /tmp/easy_install-uiv2i6/matplotlib-1.4.3/setup.cfg
Running matplotlib-1.4.3/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-uiv2i6/matplotlib-1.4.3/egg-dist-tmp-dn5itl
============================================================================ 
Edit setup.cfg to change the build options
BUILDING MATPLOTLIB
 matplotlib: yes [1.4.3]
 python: yes [3.3.2 (default, Mar 20 2014, 20:25:51) [GCC
 4.4.6 20120305 (Red Hat 4.4.6-4)]]
 platform: yes [linux]
REQUIRED DEPENDENCIES AND EXTENSIONS
 numpy: yes [version 1.7.1]
 six: yes [The installed version of six is 1.3.0 but 
a the minimum required version is 1.4. pip/easy install will attempt to 
install a newer version.]
 dateutil: yes [dateutil was not found. It is required for 
date axis support. pip/easy_install may attempt to install it after 
matplotlib.]
 pytz: yes [pytz was not found. pip will attempt to 
install it after matplotlib.]
 tornado: yes [tornado was not found. It is required for 
the WebAgg backend. pip/easy_install may attempt to install it after 
matplotlib.]
 pyparsing: yes [pyparsing was not found. It is required 
for mathtext support. pip/easy_install may attempt to install it after 
matplotlib.]
 pycxx: yes [Official versions of PyCXX are not 
compatible with matplotlib on Python 3.x, since they lack support for 
the buffer object. Using local copy]
 libagg: yes [pkg-config information for 'libagg' could 
not be found. Using local copy.]
 freetype: yes [version 2.3.11]
 png: yes [version 1.2.49]
 qhull: yes [pkg-config information for 'qhull' could 
not be
 found. Using local copy.]
OPTIONAL SUBPACKAGES
 sample_data: yes [installing]
 toolkits: yes [installing]
 tests: yes [using nose version 1.3.0 / using 
unittest.mock]
 toolkits_tests: yes [using nose version 1.3.0 / using 
unittest.mock]
OPTIONAL BACKEND EXTENSIONS
 macosx: no [Mac OS-X only]
 qt5agg: no [PyQt5 not found]
 qt4agg: no [PyQt4 not found]
 pyside: no [PySide not found]
 gtk3agg: no [Requires pygobject to be installed.]
 gtk3cairo: no [Requires cairocffi or pycairo to be 
installed.]
 gtkagg: no [Requires pygtk]
 tkagg: no [The C/C++ header for Tk (tk.h) could not 
be found. You may need to install the development package.]
 wxagg: no [requires wxPython]
 gtk: no [Requires pygtk]
 agg: yes [installing]
 cairo: no [cairocffi or pycairo not found]
 windowing: no [Microsoft Windows only]
OPTIONAL LATEX DEPENDENCIES
 dvipng: yes [version 1.11]
 ghostscript: yes [version 8.70]
 latex: yes [version 3.141592]
 pdftops: no
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from src/file_compat.h:7,
 from src/ft2font.cpp:7:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from src/ft2font.cpp:7:
src/file_compat.h: In function ���FILE* mpl_PyFile_Dup(PyObject*, char*, 
off_t*)���:
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h: In function ���int mpl_PyFile_DupClose(PyObject*, 
FILE*, off_t)���:
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/ft2font.h: In constructor 
���FT2Font::FT2Font(Py::PythonClassInstance*, Py::Tuple&, Py::Dict&)���:
src/ft2font.h:140: warning: ���FT2Font::face��� will be initialized after
src/ft2font.h:136: warning: ���Py::Object FT2Font::image���
src/ft2font.cpp:851: warning: when initialized here
src/ft2font.cpp: In member function ���Py::Object 
FT2Image::py_write_bitmap(const Py::Tuple&)���:
src/ft2font.cpp:184: warning: ���offset��� may be used uninitialized in 
this function
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/_png.cpp:28:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from src/_png.cpp:31:
src/file_compat.h: In function ���FILE* mpl_PyFile_Dup(PyObject*, char*, 
off_t*)���:
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h: In function ���int mpl_PyFile_DupClose(PyObject*, 
FILE*, off_t)���:
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/_png.cpp: In member function ���PyObject* 
_png_module::_read_png(const Py::Object&, bool, int)���:
src/_png.cpp:331: warning: deprecated conversion from string constant to 
���char*���
src/_png.cpp:316: warning: ���offset��� may be used uninitialized in 
this function
src/_png.cpp: In member function ���Py::Object 
_png_module::write_png(const Py::Tuple&)���:
src/_png.cpp:108: warning: ���offset��� may be used uninitialized in 
this function
/usr/bin/ld: skipping incompatible /usr/lib/libpng12.so when searching 
for -lpng12
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/_image.cpp:12:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
src/_image.cpp: In member function ���Py::Object 
_image_module::from_images(const Py::Tuple&)���:
src/_image.cpp:805: warning: ���alpha��� may be used uninitialized in 
this function
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
src/_ttconv.cpp: In member function ���virtual void 
PythonFileWriter::write(const char*)���:
src/_ttconv.cpp:57: warning: deprecated conversion from string constant 
to ���char*���
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/agg_py_path_iterator.h:7,
 from src/_path.cpp:3:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
src/_path.cpp: In function ���void point_in_path_impl(const void*, 
size_t, size_t, size_t, T&, npy_bool*) [with T = points_in_path(const 
void*, size_t, size_t, size_t, double, PathIterator&, const 
agg::trans_affine&, npy_bool*)::contour_t]���:
src/_path.cpp:302: instantiated from here
src/_path.cpp:168: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:302: instantiated from here
src/_path.cpp:196: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:196: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:246: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:246: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp: In function ���void point_in_path_impl(const void*, 
size_t, size_t, size_t, T&, npy_bool*) [with T = points_on_path(const 
void*, size_t, size_t, size_t, double, PathIterator&, const 
agg::trans_affine&, npy_bool*)::stroke_t]���:
src/_path.cpp:336: instantiated from here
src/_path.cpp:168: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:336: instantiated from here
src/_path.cpp:196: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:196: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:246: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
src/_path.cpp:246: warning: dereferencing type-punned pointer will break 
strict-aliasing rules
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/path_cleanup.cpp:5:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/agg_py_transforms.cpp:6:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/cntr.c:23:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from 
lib/matplotlib/delaunay/VoronoiDiagramGenerator.h:34,
 from lib/matplotlib/delaunay/_delaunay.cpp:6:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from 
lib/matplotlib/delaunay/VoronoiDiagramGenerator.cpp:38:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
lib/matplotlib/delaunay/VoronoiDiagramGenerator.cpp: In member function 
���bool VoronoiDiagramGenerator::voronoi(int)���:
lib/matplotlib/delaunay/VoronoiDiagramGenerator.cpp:923: warning: 
���newintstar.Point::y��� may be used uninitialized in this function
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/noprefix.h:9,
 from src/qhull_wrap.c:9:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from lib/matplotlib/tri/_tri.h:68,
 from lib/matplotlib/tri/_tri.cpp:8:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/agg_py_transforms.cpp:6:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarraytypes.h:1728,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/ndarrayobject.h:17,
 from 
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/arrayobject.h:15,
 from src/agg_py_path_iterator.h:7,
 from src/_backend_agg.h:43,
 from src/_backend_agg.cpp:12:
/opt/rh/python33/root/usr/lib64/python3.3/site-packages/numpy/core/include/numpy/npy_deprecated_api.h:11:2: 
warning: #warning "Using deprecated NumPy API, disable it by #defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
In file included from src/_backend_agg.cpp:44:
src/file_compat.h: In function ���FILE* mpl_PyFile_Dup(PyObject*, char*, 
off_t*)���:
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:66: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:82: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:109: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h: In function ���int mpl_PyFile_DupClose(PyObject*, 
FILE*, off_t)���:
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/file_compat.h:155: warning: deprecated conversion from string 
constant to ���char*���
src/_backend_agg.cpp: In member function ���Py::Object 
RendererAgg::draw_markers(const Py::Tuple&)���:
src/_backend_agg.cpp:791: warning: dereferencing type-punned pointer 
will break strict-aliasing rules
src/_backend_agg.cpp:791: warning: dereferencing type-punned pointer 
will break strict-aliasing rules
src/_backend_agg.cpp:829: warning: dereferencing type-punned pointer 
will break strict-aliasing rules
src/_backend_agg.cpp:829: warning: dereferencing type-punned pointer 
will break strict-aliasing rules
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching 
for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
Installed 
/opt/rh/python33/root/usr/lib/python3.3/site-packages/matplotlib-1.4.3-py3.3-linux-x86_64.egg
Because this distribution was installed --multi-version, before you can
import modules from this package in an application, you will need to
'import pkg_resources' and then use a 'require()' call similar to one of
these examples, in order to select the desired version:
 pkg_resources.require("matplotlib") # latest installed version
 pkg_resources.require("matplotlib==1.4.3") # this exact version
 pkg_resources.require("matplotlib>=1.4.3") # this version or higher
Processing dependencies for matplotlib
Searching for pyparsing>=1.5.6,!=2.0.0
Reading https://pypi.python.org/simple/pyparsing/
Reading http://pyparsing.sourceforge.net/
Reading http://pyparsing.wikispaces.com/
Reading http://sourceforge.net/project/showfiles.php?group_id=97203
Reading http://sourceforge.net/projects/pyparsing
Best match: pyparsing 2.0.3
Downloading 
https://pypi.python.org/packages/source/p/pyparsing/pyparsing-2.0.3.zip#md5=0a5ec41bb650aed802751a311b5d820d 
Processing pyparsing-2.0.3.zip
Writing /tmp/easy_install-8vc0lc/pyparsing-2.0.3/setup.cfg
Running pyparsing-2.0.3/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-8vc0lc/pyparsing-2.0.3/egg-dist-tmp-bdgu2g
zip_safe flag not set; analyzing archive contents...
__pycache__.pyparsing.cpython-33: module MAY be using inspect.stack
Installed 
/opt/rh/python33/root/usr/lib/python3.3/site-packages/pyparsing-2.0.3-py3.3.egg
Because this distribution was installed --multi-version, before you can
import modules from this package in an application, you will need to
'import pkg_resources' and then use a 'require()' call similar to one of
these examples, in order to select the desired version:
 pkg_resources.require("pyparsing") # latest installed version
 pkg_resources.require("pyparsing==2.0.3") # this exact version
 pkg_resources.require("pyparsing>=2.0.3") # this version or higher
Searching for pytz
Reading https://pypi.python.org/simple/pytz/
Best match: pytz 2015.4
Downloading 
https://pypi.python.org/packages/3.3/p/pytz/pytz-2015.4-py3.3.egg#md5=e21dada2b1eaff746d21b2ac6f76f034 
Processing pytz-2015.4-py3.3.egg
Moving pytz-2015.4-py3.3.egg to 
/opt/rh/python33/root/usr/lib/python3.3/site-packages
Installed 
/opt/rh/python33/root/usr/lib/python3.3/site-packages/pytz-2015.4-py3.3.egg
Because this distribution was installed --multi-version, before you can
import modules from this package in an application, you will need to
'import pkg_resources' and then use a 'require()' call similar to one of
these examples, in order to select the desired version:
 pkg_resources.require("pytz") # latest installed version
 pkg_resources.require("pytz==2015.4") # this exact version
 pkg_resources.require("pytz>=2015.4") # this version or higher
Searching for python-dateutil!=2.1
Reading https://pypi.python.org/simple/python-dateutil/
Reading http://labix.org/python-dateutil
Reading https://dateutil.readthedocs.org
Best match: python-dateutil 2.4.2
Downloading 
https://pypi.python.org/packages/source/p/python-dateutil/python-dateutil-2.4.2.tar.gz#md5=4ef68e1c485b09e9f034e10473e5add2 
Processing python-dateutil-2.4.2.tar.gz
Writing /tmp/easy_install-ugb9nf/python-dateutil-2.4.2/setup.cfg
Running python-dateutil-2.4.2/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-ugb9nf/python-dateutil-2.4.2/egg-dist-tmp-7bb_lh
Installed 
/opt/rh/python33/root/usr/lib/python3.3/site-packages/python_dateutil-2.4.2-py3.3.egg
Because this distribution was installed --multi-version, before you can
import modules from this package in an application, you will need to
'import pkg_resources' and then use a 'require()' call similar to one of
these examples, in order to select the desired version:
 pkg_resources.require("python-dateutil") # latest installed version
 pkg_resources.require("python-dateutil==2.4.2") # this exact version
 pkg_resources.require("python-dateutil>=2.4.2") # this version or 
higher
Searching for six>=1.4
Reading https://pypi.python.org/simple/six/
Best match: six 1.9.0
Downloading 
https://pypi.python.org/packages/source/s/six/six-1.9.0.tar.gz#md5=476881ef4012262dfc8adc645ee786c4 
Processing six-1.9.0.tar.gz
Writing /tmp/easy_install-5oq3yv/six-1.9.0/setup.cfg
Running six-1.9.0/setup.py -q bdist_egg --dist-dir 
/tmp/easy_install-5oq3yv/six-1.9.0/egg-dist-tmp-q7x1ha
no previously-included directories found matching 'documentation/_build'
zip_safe flag not set; analyzing archive contents...
__pycache__.six.cpython-33: module references __path__
Installed 
/opt/rh/python33/root/usr/lib/python3.3/site-packages/six-1.9.0-py3.3.egg
Because this distribution was installed --multi-version, before you can
import modules from this package in an application, you will need to
'import pkg_resources' and then use a 'require()' call similar to one of
these examples, in order to select the desired version:
 pkg_resources.require("six") # latest installed version
 pkg_resources.require("six==1.9.0") # this exact version
 pkg_resources.require("six>=1.9.0") # this version or higher
*Finished processing dependencies for matplotlib *
************************************************************************************************************** 
Thanks,
Zaiwen

Thank you all.
I am using Python 3.4.3.
I meant to include a pip list:
Assimulo (2.8)
decorator (4.0.2)
gmpy2 (2.0.7)
ipykernel (4.0.3)
ipython (4.0.0)
ipython-genutils (0.1.0)
ipywidgets (4.0.2)
Jinja2 (2.8)
jsonschema (2.5.1)
jupyter-client (4.0.0)
jupyter-core (4.0.4)
MarkupSafe (0.23)
matplotlib (1.4.3)
mistune (0.7.1)
nbconvert (4.0.0)
nbformat (4.0.0)
nose (1.3.7)
notebook (4.0.4)
numpy (1.9.2)
pandas (0.16.2)
path.py (8.1)
pickleshare (0.5)
pip (7.1.2)
Pygments (2.0.2)
pyparsing (2.0.3)
pyreadline (2.0)
python-dateutil (2.4.2)
pytz (2015.4)
pyzmq (14.7.0)
requests (2.7.0)
scipy (0.16.0)
setuptools (18.2)
simplegeneric (0.8.1)
six (1.9.0)
sympy (0.7.6)
testpath (0.2)
tornado (4.2.1)
traitlets (4.0.0)
So, if the program works for Python 2.7 but not 3.4.3, maybe that is the
problem? Let me try to install Python 2.7 tonight and see what that does.
On Wed, Sep 16, 2015 at 8:39 AM, Sterling Smith <sm...@fu...>
wrote:
> Works fine for
>
> {{{
> : python
> Python 2.7.10 (default, Sep 15 2015, 11:26:42)
> [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> /Users/smithsp/.pyhistory
> >>> import matplotlib
> >>> matplotlib.__version__
> '1.4.3'
> >>> import numpy
> >>> numpy.__version__
> '1.9.2'
> >>> matplotlib.get_backend()
> u’MacOSX'
> }}}
>
> All are obtained through MacPorts on OSX 10.9.5.
>
> -Sterling
>
>
>
> On Sep 16, 2015, at 6:50AM, Benjamin Root <ben...@gm...> wrote:
>
> > Btw, I can't reproduce the problem using matplotlib master, numpy master
> and linux. I know it isn't at all similar to your setup, but it is a data
> point.
> >
> > On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...>
> wrote:
> > What version of numpy do you have installed?
> >
> > On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
> wrote:
> > OS: Windows 8.1 Pro
> >
> > matplotlib version: 1.4.3
> >
> > where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
> >
> > customizations: none
> >
> > Sample Program: attached py file; this is a Physics homework problem; I
> have the answers I need, but would like to fix the errors to be able to
> label all lines.
> >
> > Debug output in attached output.txt file
> >
> > If you uncomment line 180, the error is reported as if it came from that
> line even though there is no float64 on that line (savefig). If commented,
> it does not report a line from my .py file...
> >
> > If you make line 170 read as follows, the error goes away:
> >
> > if (maxTerm<32):
> >
> > This suggests to me that the additional labels for the 32, 64, 128, and
> 154 term runs is what is triggering the bug, but I cannot figure out what
> it is.
> >
> > Also, separate note, just about any time I make figures, when closing
> the last figure I get a python.exe app crash and this message:
> >
> > alloc: invalid block: 00000000044E7680: 0 d
> >
> >
> > Thank you for any help,
> > Bobby
> >
> >
> >
> ------------------------------------------------------------------------------
> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> > Get real-time metrics from all of your servers, apps and tools
> > in one place.
> > SourceForge users - Click here to start your Free Trial of Datadog now!
> > http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> > Get real-time metrics from all of your servers, apps and tools
> > in one place.
> > SourceForge users - Click here to start your Free Trial of Datadog now!
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Works fine for
{{{
 : python 
Python 2.7.10 (default, Sep 15 2015, 11:26:42) 
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
/Users/smithsp/.pyhistory
>>> import matplotlib
>>> matplotlib.__version__
'1.4.3'
>>> import numpy
>>> numpy.__version__
'1.9.2'
>>> matplotlib.get_backend()
u’MacOSX'
}}}
All are obtained through MacPorts on OSX 10.9.5.
-Sterling
On Sep 16, 2015, at 6:50AM, Benjamin Root <ben...@gm...> wrote:
> Btw, I can't reproduce the problem using matplotlib master, numpy master and linux. I know it isn't at all similar to your setup, but it is a data point.
> 
> On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...> wrote:
> What version of numpy do you have installed?
> 
> On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...> wrote:
> OS: Windows 8.1 Pro
> 
> matplotlib version: 1.4.3
> 
> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
> 
> customizations: none
> 
> Sample Program: attached py file; this is a Physics homework problem; I have the answers I need, but would like to fix the errors to be able to label all lines.
> 
> Debug output in attached output.txt file
> 
> If you uncomment line 180, the error is reported as if it came from that line even though there is no float64 on that line (savefig). If commented, it does not report a line from my .py file...
> 
> If you make line 170 read as follows, the error goes away:
> 
> if (maxTerm<32):
> 
> This suggests to me that the additional labels for the 32, 64, 128, and 154 term runs is what is triggering the bug, but I cannot figure out what it is. 
> 
> Also, separate note, just about any time I make figures, when closing the last figure I get a python.exe app crash and this message:
> 
> alloc: invalid block: 00000000044E7680: 0 d
> 
> 
> Thank you for any help,
> Bobby
> 
> 
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
> 
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140_______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Btw, I can't reproduce the problem using matplotlib master, numpy master
and linux. I know it isn't at all similar to your setup, but it is a data
point.
On Wed, Sep 16, 2015 at 9:43 AM, Benjamin Root <ben...@gm...> wrote:
> What version of numpy do you have installed?
>
> On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
> wrote:
>
>> OS: Windows 8.1 Pro
>>
>> matplotlib version: 1.4.3
>>
>> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
>>
>> customizations: none
>>
>> Sample Program: attached py file; this is a Physics homework problem; I
>> have the answers I need, but would like to fix the errors to be able to
>> label all lines.
>>
>> Debug output in attached output.txt file
>>
>> If you uncomment line 180, the error is reported as if it came from that
>> line even though there is no float64 on that line (savefig). If commented,
>> it does not report a line from my .py file...
>>
>> If you make line 170 read as follows, the error goes away:
>>
>> if (maxTerm<32):
>>
>> This suggests to me that the additional labels for the 32, 64, 128, and
>> 154 term runs is what is triggering the bug, but I cannot figure out what
>> it is.
>>
>> Also, separate note, just about any time I make figures, when closing the
>> last figure I get a python.exe app crash and this message:
>>
>> alloc: invalid block: 00000000044E7680: 0 d
>>
>>
>> Thank you for any help,
>> Bobby
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> Get real-time metrics from all of your servers, apps and tools
>> in one place.
>> SourceForge users - Click here to start your Free Trial of Datadog now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>

What version of numpy do you have installed?
On Wed, Sep 16, 2015 at 5:35 AM, Bobby Wilkins <bob...@gm...>
wrote:
> OS: Windows 8.1 Pro
>
> matplotlib version: 1.4.3
>
> where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
>
> customizations: none
>
> Sample Program: attached py file; this is a Physics homework problem; I
> have the answers I need, but would like to fix the errors to be able to
> label all lines.
>
> Debug output in attached output.txt file
>
> If you uncomment line 180, the error is reported as if it came from that
> line even though there is no float64 on that line (savefig). If commented,
> it does not report a line from my .py file...
>
> If you make line 170 read as follows, the error goes away:
>
> if (maxTerm<32):
>
> This suggests to me that the additional labels for the 32, 64, 128, and
> 154 term runs is what is triggering the bug, but I cannot figure out what
> it is.
>
> Also, separate note, just about any time I make figures, when closing the
> last figure I get a python.exe app crash and this message:
>
> alloc: invalid block: 00000000044E7680: 0 d
>
>
> Thank you for any help,
> Bobby
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

OS: Windows 8.1 Pro
matplotlib version: 1.4.3
where obtained: http://www.lfd.uci.edu/~gohlke/pythonlibs/
customizations: none
Sample Program: attached py file; this is a Physics homework problem; I
have the answers I need, but would like to fix the errors to be able to
label all lines.
Debug output in attached output.txt file
If you uncomment line 180, the error is reported as if it came from that
line even though there is no float64 on that line (savefig). If commented,
it does not report a line from my .py file...
If you make line 170 read as follows, the error goes away:
if (maxTerm<32):
This suggests to me that the additional labels for the 32, 64, 128, and 154
term runs is what is triggering the bug, but I cannot figure out what it
is.
Also, separate note, just about any time I make figures, when closing the
last figure I get a python.exe app crash and this message:
alloc: invalid block: 00000000044E7680: 0 d
Thank you for any help,
Bobby

What might be more generally useful is to make it easier to specify which
coordinate system you wish some spec to apply to. To be frank, I can never
keep the transform names straight, and it isn't possible to specify it at
all in some places.
On Sep 9, 2015 6:04 PM, "Thomas Robitaille" <tho...@gm...>
wrote:
> I managed to write an Axes sub-class to do this:
>
> https://gist.github.com/astrofrog/8d579ea83e578a9cdb99
>
> Try running this then resize the figure and the margin between axes
> and figure edge will stay constant.
>
> Is this something that would be useful to have in Matplotlib itself? I
> could foresee something like:
>
> fig.add_axes([0.1, 0.1, 0.8, 0.8], preserve_absolute_margins=True)
>
> If this would be useful, I can open a pull request.
>
> Cheers,
> Tom
>
> On 9 September 2015 at 23:29, Thomas Robitaille
> <tho...@gm...> wrote:
> > Thanks Eric - unfortunately I need to be able to resize the figure
> > interactively and have the axes follow.
> >
> > So an alternative that would be equally useful for me would be to
> > specify axes using add_subplot or add_axes but then essentially have
> > an option to say that the distance to the edge of the figure should be
> > preserved when resizing. In other words, I'm not too concerned about
> > whether I specify the original axes position in relative units or in
> > inches, but the important thing is that the distance to the edge of
> > the figure stays constant in absolute terms.
> >
> > Is this something that would be easy to build as an Axes subclass?
> >
> > Cheers,
> > Tom
> >
> >
> >
> > On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote:
> >> On 2015年09月09日 11:01 AM, Thomas Robitaille wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> I am interested in creating axes in an interactive figure where the
> >>> distance from the spines of the axes to the figure edge are constant
> >>> in absolute terms.
> >>>
> >>> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the
> >>> spines of the axes are always located a distance from the edge of the
> >>> figure that is 10% of the size of the figure. However, in my case,
> >>> since the font size is constant, I want to be able to say that the
> >>> spines should always be e.g. 0.5" from the edge of the figure, which
> >>> would avoid wasting space when making the figure larger.
> >>>
> >>> Is there a way to do this currently?
> >>
> >>
> >> This is what I use for positioning in inches:
> >>
> >> def axes_inches(fig, rect, **kw):
> >> """
> >> Wrapper for Figure.add_axes in which *rect* is given in inches.
> >> The translation to normalized coordinates is done immediately
> >> based on the present figsize.
> >>
> >> *rect* is left, bottom, width, height in inches
> >> *kw* are passed to Figure.add_axes
> >>
> >> """
> >>
> >> fw = fig.get_figwidth()
> >> fh = fig.get_figheight()
> >> l, b, w, h = rect
> >> relrect = [l / fw, b / fh, w / fw, h / fh]
> >> ax = fig.add_axes(relrect, **kw)
> >> return ax
> >>
> >> Note, however, that this works correctly only if you don't change
> figsize
> >> after calling it, so maybe it is not what you are looking for.
> >>
> >> Eric
> >>
> >>>
> >>> (I am aware of set_tight_layout which would result in something
> >>> similar, but this is not what I am after - I would like to be able to
> >>> specify the exact absolute distance from the figure edge)
> >>>
> >>> Thanks!
> >>> Tom
> >>>
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> >>> Get real-time metrics from all of your servers, apps and tools
> >>> in one place.
> >>> SourceForge users - Click here to start your Free Trial of Datadog now!
> >>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> >>> _______________________________________________
> >>> Matplotlib-users mailing list
> >>> Mat...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >>>
> >>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

I managed to write an Axes sub-class to do this:
https://gist.github.com/astrofrog/8d579ea83e578a9cdb99
Try running this then resize the figure and the margin between axes
and figure edge will stay constant.
Is this something that would be useful to have in Matplotlib itself? I
could foresee something like:
fig.add_axes([0.1, 0.1, 0.8, 0.8], preserve_absolute_margins=True)
If this would be useful, I can open a pull request.
Cheers,
Tom
On 9 September 2015 at 23:29, Thomas Robitaille
<tho...@gm...> wrote:
> Thanks Eric - unfortunately I need to be able to resize the figure
> interactively and have the axes follow.
>
> So an alternative that would be equally useful for me would be to
> specify axes using add_subplot or add_axes but then essentially have
> an option to say that the distance to the edge of the figure should be
> preserved when resizing. In other words, I'm not too concerned about
> whether I specify the original axes position in relative units or in
> inches, but the important thing is that the distance to the edge of
> the figure stays constant in absolute terms.
>
> Is this something that would be easy to build as an Axes subclass?
>
> Cheers,
> Tom
>
>
>
> On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote:
>> On 2015年09月09日 11:01 AM, Thomas Robitaille wrote:
>>>
>>> Hi everyone,
>>>
>>> I am interested in creating axes in an interactive figure where the
>>> distance from the spines of the axes to the figure edge are constant
>>> in absolute terms.
>>>
>>> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the
>>> spines of the axes are always located a distance from the edge of the
>>> figure that is 10% of the size of the figure. However, in my case,
>>> since the font size is constant, I want to be able to say that the
>>> spines should always be e.g. 0.5" from the edge of the figure, which
>>> would avoid wasting space when making the figure larger.
>>>
>>> Is there a way to do this currently?
>>
>>
>> This is what I use for positioning in inches:
>>
>> def axes_inches(fig, rect, **kw):
>> """
>> Wrapper for Figure.add_axes in which *rect* is given in inches.
>> The translation to normalized coordinates is done immediately
>> based on the present figsize.
>>
>> *rect* is left, bottom, width, height in inches
>> *kw* are passed to Figure.add_axes
>>
>> """
>>
>> fw = fig.get_figwidth()
>> fh = fig.get_figheight()
>> l, b, w, h = rect
>> relrect = [l / fw, b / fh, w / fw, h / fh]
>> ax = fig.add_axes(relrect, **kw)
>> return ax
>>
>> Note, however, that this works correctly only if you don't change figsize
>> after calling it, so maybe it is not what you are looking for.
>>
>> Eric
>>
>>>
>>> (I am aware of set_tight_layout which would result in something
>>> similar, but this is not what I am after - I would like to be able to
>>> specify the exact absolute distance from the figure edge)
>>>
>>> Thanks!
>>> Tom
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>>> Get real-time metrics from all of your servers, apps and tools
>>> in one place.
>>> SourceForge users - Click here to start your Free Trial of Datadog now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>>
>>

Thanks Eric - unfortunately I need to be able to resize the figure
interactively and have the axes follow.
So an alternative that would be equally useful for me would be to
specify axes using add_subplot or add_axes but then essentially have
an option to say that the distance to the edge of the figure should be
preserved when resizing. In other words, I'm not too concerned about
whether I specify the original axes position in relative units or in
inches, but the important thing is that the distance to the edge of
the figure stays constant in absolute terms.
Is this something that would be easy to build as an Axes subclass?
Cheers,
Tom
On 9 September 2015 at 23:12, Eric Firing <ef...@ha...> wrote:
> On 2015年09月09日 11:01 AM, Thomas Robitaille wrote:
>>
>> Hi everyone,
>>
>> I am interested in creating axes in an interactive figure where the
>> distance from the spines of the axes to the figure edge are constant
>> in absolute terms.
>>
>> To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the
>> spines of the axes are always located a distance from the edge of the
>> figure that is 10% of the size of the figure. However, in my case,
>> since the font size is constant, I want to be able to say that the
>> spines should always be e.g. 0.5" from the edge of the figure, which
>> would avoid wasting space when making the figure larger.
>>
>> Is there a way to do this currently?
>
>
> This is what I use for positioning in inches:
>
> def axes_inches(fig, rect, **kw):
> """
> Wrapper for Figure.add_axes in which *rect* is given in inches.
> The translation to normalized coordinates is done immediately
> based on the present figsize.
>
> *rect* is left, bottom, width, height in inches
> *kw* are passed to Figure.add_axes
>
> """
>
> fw = fig.get_figwidth()
> fh = fig.get_figheight()
> l, b, w, h = rect
> relrect = [l / fw, b / fh, w / fw, h / fh]
> ax = fig.add_axes(relrect, **kw)
> return ax
>
> Note, however, that this works correctly only if you don't change figsize
> after calling it, so maybe it is not what you are looking for.
>
> Eric
>
>>
>> (I am aware of set_tight_layout which would result in something
>> similar, but this is not what I am after - I would like to be able to
>> specify the exact absolute distance from the figure edge)
>>
>> Thanks!
>> Tom
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> Get real-time metrics from all of your servers, apps and tools
>> in one place.
>> SourceForge users - Click here to start your Free Trial of Datadog now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>

Hi everyone,
I am interested in creating axes in an interactive figure where the
distance from the spines of the axes to the figure edge are constant
in absolute terms.
To clarify what I mean, when using add_axes([0.1, 0.1, 0.8, 0.8]), the
spines of the axes are always located a distance from the edge of the
figure that is 10% of the size of the figure. However, in my case,
since the font size is constant, I want to be able to say that the
spines should always be e.g. 0.5" from the edge of the figure, which
would avoid wasting space when making the figure larger.
Is there a way to do this currently?
(I am aware of set_tight_layout which would result in something
similar, but this is not what I am after - I would like to be able to
specify the exact absolute distance from the figure edge)
Thanks!
Tom

Thales,
Sorry for the delay in responding. This mailing list has actually moved to
https://mail.python.org/mailman/listinfo/matplotlib-users
Let's start up a new thread there with this information, plus also which
version of matplotlib you are using and which backend.
Cheers!
Ben Root
On Wed, Aug 26, 2015 at 6:12 PM, Thales Maia <tha...@gm...> wrote:
> Hello,
>
> I am migrating from octave to python and found matplotlib as an useful and
> powerful resource.
> I played with many animations examples and tried to build my own.
>
> The objective is to build a live plot from data coming from an arduino.
> The serial is working perfect (I can receive and plot data without
> problem).
>
> Unfortunately, when I resize my animation windows, I get curves
> overlapped.
>
> I must use blit because I have 6 subplots.
>
> Please, check the attached files:
> Python:
> -> animationR00.py (main)
> -> lib/
> -> AnalogPlot.py
> -> RingBuffer.py
> -> crc8.py
>
> Arduino:
> Teste.cpp (main)
> Teste.h
> ComSerial.cpp
> ComSerial.h
> OneWire.cpp
> OneWire.h
> I appreciate any help.
> -
> Thales Alexandre Carvalho Maia
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

This appears to be DPI dependent.
Changing the last line of Richard's example to
plt.savefig("grap.png")
gives a PNG with a shadow similar to that generated by TkAgg.
--Mark
On 09/03/2015 01:17 PM, Sterling Smith wrote:
> For those who wonder what he means:
> on the left is TkAgg; on the right is png.
>
> -Sterling
>
> On Sep 3, 2015, at 1:13PM, Richard Stanton <st...@ha...
> <mailto:st...@ha...>> wrote:
>
>> A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I
>> export to a PDF file, the shadow looks much more like it does on the screen.
>>
>>
>>> On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha...
>>> <mailto:st...@ha...>> wrote:
>>>
>>> I’m trying to create a pie chart for a presentation. If I turn on shadows,
>>> they look fine on the screen (in an IPython notebook), but when I export the
>>> file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this
>>> a bug? And is there a way to shrink the size of the shadow?
>>>
>>> Here’s some sample code that shows the problem:
>>>
>>> import matplotlib.pyplot as plt
>>> numbers = [4380.0, 2474.0, 158]
>>> explode=(0, 0, 0.5)
>>> plt.pie(numbers, explode=explode,shadow=True)
>>> plt.axis('equal')
>>> plt.savefig(‘grap.png’, dpi=400)
>>>
>>> Thanks for any suggestions.
>>>
>>> By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution
>>> under OS X.
>>>
>>> Richard Stanton
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
>> Get real-time metrics from all of your servers, apps and tools
>> in one place.
>> SourceForge users - Click here to start your Free Trial of Datadog now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

For those who wonder what he means: 
on the left is TkAgg; on the right is png.
-Sterling
On Sep 3, 2015, at 1:13PM, Richard Stanton <st...@ha...> wrote:
> A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I export to a PDF file, the shadow looks much more like it does on the screen.
> 
> 
>> On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha...> wrote:
>> 
>> I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? 
>> 
>> Here’s some sample code that shows the problem:
>> 
>> import matplotlib.pyplot as plt
>> numbers = [4380.0, 2474.0, 158]
>> explode=(0, 0, 0.5)
>> plt.pie(numbers, explode=explode,shadow=True)
>> plt.axis('equal')
>> plt.savefig(‘grap.png’, dpi=400)
>> 
>> Thanks for any suggestions.
>> 
>> By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X.
>> 
>> Richard Stanton
> 
> 
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

A quick follow-up: if I export to a jpg file, I get the same huge shadow. If I export to a PDF file, the shadow looks much more like it does on the screen.
> On Sep 3, 2015, at 1:07 PM, Richard Stanton <st...@ha...> wrote:
> 
> I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? 
> 
> Here’s some sample code that shows the problem:
> 
> import matplotlib.pyplot as plt
> numbers = [4380.0, 2474.0, 158]
> explode=(0, 0, 0.5)
> plt.pie(numbers, explode=explode,shadow=True)
> plt.axis('equal')
> plt.savefig(‘grap.png’, dpi=400)
> 
> Thanks for any suggestions.
> 
> By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X.
> 
> Richard Stanton

I’m trying to create a pie chart for a presentation. If I turn on shadows, they look fine on the screen (in an IPython notebook), but when I export the file to a PNG file, the shadow is way larger, and looks pretty ugly. Is this a bug? And is there a way to shrink the size of the shadow? 
Here’s some sample code that shows the problem:
import matplotlib.pyplot as plt
numbers = [4380.0, 2474.0, 158]
explode=(0, 0, 0.5)
plt.pie(numbers, explode=explode,shadow=True)
plt.axis('equal')
plt.savefig(‘grap.png’, dpi=400)
Thanks for any suggestions.
By the way, I’m using Matplotlib version 1.4.3 with the Anaconda distribution under OS X.
Richard Stanton

Neal,
This is possible, but I suspect requires managing the visibility flipping
and resizing your self.
This does seem like a useful thing to build out and couples well with an
open issue about changing the gird size after the fact.
Tom
On Tue, May 26, 2015 at 3:26 PM Neal Becker <ndb...@gm...> wrote:
> I'm plotting 1 figure with 8 subplots. They are 8 channels, and I want to
> see if there is some interaction.
>
> I wish that the 'configure subplots' menu allowed me to choose just some
> subplots to display (resizing when I turn some off), so I could get a
> better view at the selected subplots.
>
>
> --
> Those who fail to understand recursion are doomed to repeat it
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Great, thanks!
Rgds
marcus
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/boxplot-behaviour-in-an-extreme-scenario-tp46027p46034.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Even though I'm familiar with the boxplot source code, I largely use
IPython for quick investigations like this.
In IPython, doing something like "matplotlib.Axes.boxplot??" shows the full
source code for that functions\.
Then I saw/remembered that boxplot now just calls
matplotlib.cbook.boxplot_stats and passes the results to
matplotlib.Axes.bxp.
So then I did "matplotlib.cbook.boxplot_stats" to see how the whiskers were
computed.
-paul
On Wed, Aug 26, 2015 at 8:43 PM, chtan <ch...@un...> wrote:
> Uh, now I understand why it's behaving this way. Tx Paul.
>
> >From the documentation, it seems natural to expect the behaviour to be
> uniform throughout the meaningful range for IQR.
>
> How may I go about searching for the responsible code on my own in
> situations like this?
> >From the perplexing behaviour to the little nugget in
> matplotlib.cbook.boxplot_stats, the path isn't clear to me.
>
> Any general advice?
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/boxplot-behaviour-in-an-extreme-scenario-tp46027p46032.html
> Sent from the matplotlib - users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Uh, now I understand why it's behaving this way. Tx Paul.
>From the documentation, it seems natural to expect the behaviour to be
uniform throughout the meaningful range for IQR.
How may I go about searching for the responsible code on my own in
situations like this?
>From the perplexing behaviour to the little nugget in
matplotlib.cbook.boxplot_stats, the path isn't clear to me.
Any general advice?
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/boxplot-behaviour-in-an-extreme-scenario-tp46027p46032.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

I'm on python 2.
I get the same outputs after adding "from __future__ import division".
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/boxplot-behaviour-in-an-extreme-scenario-tp46027p46031.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hello,
I am migrating from octave to python and found matplotlib as an useful and
powerful resource.
I played with many animations examples and tried to build my own.
The objective is to build a live plot from data coming from an arduino.
The serial is working perfect (I can receive and plot data without problem).
Unfortunately, when I resize my animation windows, I get curves overlapped.
I must use blit because I have 6 subplots.
Please, check the attached files:
Python:
-> animationR00.py (main)
-> lib/
 -> AnalogPlot.py
 -> RingBuffer.py
 -> crc8.py
Arduino:
Teste.cpp (main)
Teste.h
ComSerial.cpp
ComSerial.h
OneWire.cpp
OneWire.h
I appreciate any help.
-
Thales Alexandre Carvalho Maia