matplotlib-devel Mailing List for matplotlib (Page 4)

In article <505...@st...>,
 Michael Droettboom <md...@st...> 
 wrote:
> I have tagged and created a tarball for 1.2.0rc1. The githash is 
> bda6dd9feab8. The tarball is on the github download page here:
> 
> https://github.com/matplotlib/matplotlib/downloads
I have a Mac OS X 10.6, python.org 64-bit python 2.7 version ready. 
I have uploaded it here:
<http://www.astro.washington.edu/users/rowen/python/matplotlib-1.2.0rc1-p
y2.7-python.org-macosx10.6.dmg>
since I could not figure out how to upload it to the github page (I am 
logged in as r-owen but no sign of upload capability).
The test results look good to me, though the warning is a pity:
localhost$ python -c "import matplotlib as m ; m.test(verbosity=1)"
.........................................................................
.........................................................................
.........SSS.K...............................K...........................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.............................................................../Library/F
rameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matpl
otlib/gridspec.py:298: UserWarning: This figure includes Axes that are 
not compatible with tight_layout, so its results might be incorrect.
 warnings.warn("This figure includes Axes that are not "
..............................
----------------------------------------------------------------------
Ran 1188 tests in 474.571s
OK (KNOWNFAIL=2, SKIP=3)
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pack
ages/matplotlib/__init__.py:997: UserWarning: This call to 
matplotlib.use() has no effect
because the the backend has already been chosen;
matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
or matplotlib.backends is imported for the first time.
 warnings.warn(_use_error_msg)
I also tried to build a Mac OS X 10.3, python.org 32-bit python, but 
that failed. Any advice on how to proceed would be welcome. I have 
appended the build log.
-- Russell
Log of failed build for Mac OS X 10.3 (on Mac OS X 10.4) for python.org 
32-bit python 2.7.
d-173-250-206-120:/Archives/PythonPackages/matplotlib-1.2.0rc1 rowen$ 
python setup.py build
basedirlist is: ['/usr/local/', '/usr', '/usr/X11']
=========================================================================
===
BUILDING MATPLOTLIB
 matplotlib: 1.2.0rc1
 python: 2.7.2 (v2.7.2:8527427914a2, Jun 11 2011, 14:13:39)
 [GCC 4.0.1 (Apple Inc. build 5493)]
 platform: darwin
REQUIRED DEPENDENCIES
 numpy: 1.6.2
 freetype2: found, but unknown version (no pkg-config)
OPTIONAL BACKEND DEPENDENCIES
 libpng: found, but unknown version (no pkg-config)
 Tkinter: Tkinter: version not identified, Tk: 8.4, Tcl: 8.4
 Gtk+: no
 * Building for Gtk+ requires pygtk; you must be 
able
 * to "import gtk" in your build/install 
environment
 Mac OS X native: yes
 Qt: no
 Qt4: no
 PySide: no
 Cairo: no
OPTIONAL DATE/TIMEZONE DEPENDENCIES
 dateutil: matplotlib will provide
 pytz: matplotlib will provide
adding pytz
OPTIONAL USETEX DEPENDENCIES
 dvipng: no
 ghostscript: /bin/sh: line 1: gs: command not found
 latex: no
[Edit setup.cfg to suppress the above messages]
=========================================================================
===
pymods ['pylab']
packages ['matplotlib', 'matplotlib.backends', 
'matplotlib.backends.qt4_editor', 'matplotlib.projections', 
'matplotlib.testing', 'matplotlib.testing.jpl_units', 
'matplotlib.tests', 'mpl_toolkits', 'mpl_toolkits.mplot3d', 
'mpl_toolkits.axes_grid', 'mpl_toolkits.axes_grid1', 
'mpl_toolkits.axisartist', 'matplotlib.sphinxext', 'matplotlib.tri', 
'matplotlib.delaunay', 'pytz', 'dateutil', 'dateutil.zoneinfo']
running build
running build_py
creating build
creating build/lib.macosx-10.3-fat-2.7
copying lib/pylab.py -> build/lib.macosx-10.3-fat-2.7
creating build/lib.macosx-10.3-fat-2.7/matplotlib
copying lib/matplotlib/__init__.py -> 
build/lib.macosx-10.3-fat-2.7/matplotlib
...
copying lib/dateutil_py2/zoneinfo/zoneinfo-2010g.tar.gz -> 
build/lib.macosx-10.3-fat-2.7/dateutil/zoneinfo
running build_ext
building 'matplotlib.ft2font' extension
creating build/temp.macosx-10.3-fat-2.7
creating build/temp.macosx-10.3-fat-2.7/src
creating build/temp.macosx-10.3-fat-2.7/CXX
gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -g -O2 -DNDEBUG -g 
-O3 -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 
-I/usr/local/include -I/usr/include -I/usr/X11/include 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include -I/usr/local/include -I/usr/include -I. 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 
-I/usr/X11/include/freetype2 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include/freetype2 -I/usr/local/include/freetype2 
-I/usr/include/freetype2 -I./freetype2 
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c 
src/ft2font.cpp -o build/temp.macosx-10.3-fat-2.7/src/ft2font.o
...
building 'matplotlib.backends._tkagg' extension
gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -g -O2 -DNDEBUG -g 
-O3 -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 
-I/usr/local/include -I/usr/include -I/usr/X11/include 
-I/Library/Frameworks/Tcl.framework/Headers 
-I/Library/Frameworks/Tcl.framework/Versions/Current/PrivateHeaders 
-I/Library/Frameworks/Tk.framework/Headers 
-I/Library/Frameworks/Tk.framework/Versions/Current/PrivateHeaders 
-I/usr/local/include -I/usr/include -I. 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include -Isrc -Iagg24/include -I. 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include -I/usr/local/include -I/usr/include -I. 
-I/usr/local/include/freetype2 -I/usr/include/freetype2 
-I/usr/X11/include/freetype2 
-I/Library/Frameworks/Tcl.framework/Headers/freetype2 
-I/Library/Frameworks/Tcl.framework/Versions/Current/PrivateHeaders/freet
ype2 -I/Library/Frameworks/Tk.framework/Headers/freetype2 
-I/Library/Frameworks/Tk.framework/Versions/Current/PrivateHeaders/freety
pe2 -I/usr/local/include/freetype2 -I/usr/include/freetype2 
-I./freetype2 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include/freetype2 -Isrc/freetype2 
-Iagg24/include/freetype2 -I./freetype2 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include/freetype2 -I/usr/local/include/freetype2 
-I/usr/include/freetype2 -I./freetype2 
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c 
src/agg_py_transforms.cpp -o 
build/temp.macosx-10.3-fat-2.7/src/agg_py_transforms.o -framework Tcl 
-framework Tk
powerpc-apple-darwin8-gcc-4.0.1: -framework: linker input file unused 
because linking not done
powerpc-apple-darwin8-gcc-4.0.1: Tcl: linker input file unused because 
linking not done
powerpc-apple-darwin8-gcc-4.0.1: -framework: linker input file unused 
because linking not done
powerpc-apple-darwin8-gcc-4.0.1: Tk: linker input file unused because 
linking not done
i686-apple-darwin8-gcc-4.0.1: -framework: linker input file unused 
because linking not done
i686-apple-darwin8-gcc-4.0.1: Tcl: linker input file unused because 
linking not done
i686-apple-darwin8-gcc-4.0.1: -framework: linker input file unused 
because linking not done
i686-apple-darwin8-gcc-4.0.1: Tk: linker input file unused because 
linking not done
...(five more compiles with these same warnings elided)...
c++ -bundle -undefined dynamic_lookup -arch ppc -arch i386 -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -g 
build/temp.macosx-10.3-fat-2.7/src/agg_py_transforms.o 
build/temp.macosx-10.3-fat-2.7/src/_tkagg.o 
build/temp.macosx-10.3-fat-2.7/CXX/cxx_extensions.o 
build/temp.macosx-10.3-fat-2.7/CXX/cxxsupport.o 
build/temp.macosx-10.3-fat-2.7/CXX/IndirectPythonInterface.o 
build/temp.macosx-10.3-fat-2.7/CXX/cxxextensions.o -L/usr/local/lib 
-L/usr/lib -L/usr/local/lib -L/usr/lib -lstdc++ -lm -lfreetype -lz 
-lstdc++ -lm -o 
build/lib.macosx-10.3-fat-2.7/matplotlib/backends/_tkagg.so -framework 
Tcl -framework Tk
building 'matplotlib.backends._macosx' extension
gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 -g -O2 -DNDEBUG -g 
-O3 -DPY_ARRAY_UNIQUE_SYMBOL=MPL_ARRAY_API -DPYCXX_ISO_CPP_LIB=1 
-I/usr/local/include -I/usr/include -I/usr/X11/include 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include -I/usr/local/include -I/usr/include -I. 
-I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-pa
ckages/numpy/core/include -Isrc -Iagg24/include -I. 
-I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c 
src/_macosx.m -o build/temp.macosx-10.3-fat-2.7/src/_macosx.o
src/_macosx.m: In function 'show':
src/_macosx.m:5763: error: nested functions are disabled, use 
-fnested-functions to re-enable
src/_macosx.m:5763: error: syntax error before 'in'
src/_macosx.m: At top level:
src/_macosx.m:5768: error: parse error before 'PyObject'
src/_macosx.m: In function 'show':
src/_macosx.m:5763: error: nested functions are disabled, use 
-fnested-functions to re-enable
src/_macosx.m:5763: error: syntax error before 'in'
src/_macosx.m: At top level:
src/_macosx.m:5768: error: parse error before 'PyObject'
lipo: can't figure out the architecture type of: /var/tmp//ccI9WUN2.out
error: command 'gcc-4.0' failed with exit status 1
d-173-250-206-120:/Archives/PythonPackages/matplotlib-1.2.0rc1

> I was just wondering if I should preferably post such messages about a
> possible bug report on matplotlib-users mailing list instead of the
> devel ml
Hi Pierre,
Thanks for bringing this to our attention.
You've posted to the right mailing list - I'm sorry nobody has replied, we
have all been focussing on the latest 1.2 release and this has fallen
through the net.
Your issue looks legit, I have looked through the axes.py Axes.draw method,
and there is no filtering based on the visibility toggle for anything but
images. Seems like it could be a very easy fix, would you be willing to
open an issue on the github tracker?
https://github.com/matplotlib/matplotlib/issues/new
Thanks again for raising this,
All the best,
Phil

On 9/12/12 7:49 PM, Michael Droettboom wrote:
> I believe I've now fixed this.
>
> Mike
Yep, it's good now. Thanks Michael.
-Jeff
>
> On 09/12/2012 09:28 PM, Jeff Whitaker wrote:
>> The link points to matplotlib.org/basemap (which doesn't exist), should
>> be matplotlib.github.com/basemap. Either that, or
>> matplotlib.org/basemap should redirect there.
>>
>> -Jeff
>>
>> ------------------------------------------------------------------------------ 
>>
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. 
>> Discussions
>> will include endpoint security, mobile security and the latest in 
>> malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

The link points to matplotlib.org/basemap (which doesn't exist), should 
be matplotlib.github.com/basemap. Either that, or 
matplotlib.org/basemap should redirect there.
-Jeff

On 9/12/2012 10:31 AM, Christoph Gohlke wrote:
> On 9/12/2012 7:44 AM, Michael Droettboom wrote:
>> I have tagged and created a tarball for 1.2.0rc1. The githash is
>> bda6dd9feab8. The tarball is on the github download page here:
>>
>> https://github.com/matplotlib/matplotlib/downloads
>>
>> I have created a new branch, v1.2.x, for continuing 1.2.x development.
>> The feature freeze on master is now lifted and big experimental changes
>> can be merged into master. Any bugfixes that need to go into 1.2.x
>> should be merged into both places. Please mark any PRs for the 1.2.x
>> branch with the 1.2.x milestone so we can verify that things are merged
>> in both places.
>>
>> For those creating the Windows and Macintosh builds, let's try using the
>> github download page rather than the one at Sourceforge this time. It
>> is a lot simpler.
>>
>> For those creating distro packages, now is a good time to let us know
>> what can be done to make the inclusion of matplotlib 1.2.0 as smooth as
>> possible.
>>
>> Once the binaries are available, I will make an announcement to
>> matplotlib-users.
>>
>> Mike
>>
>>
>
> Can we hold the Windows binaries until rc2? Setup.py corrupts the pytz
> package, leading to stack-overflows on Python 3 and other problems on
> Python 2.
>
> Christoph
>
Sorry, I meant the dateutil package, not pytz.
Christoph

Le 10/09/2012 19:19, Pierre Haessig a écrit :
> Hello,
>
> This may be a silly question, but I'm wondering what happens in
> Matplotlib rendering when there is a "big" Line2D object (say 10**7
> points) added to an Axes, with *visibility set to false*.
>
> [...]
Hello,
I was just wondering if I should preferably post such messages about a
possible bug report on matplotlib-users mailing list instead of the
devel ml. I'm not familiar with the community convention of how to spit
topics between those two. Or is it better if I just report directly an
issue on GitHub and start discussion from there ?
Best,
Pierre
PS : an unrelated question about mailing list : I noticed that the
matplotlib-users ml archive on sourceforge seems to stop from recording
starting around July 16th 2012
http://sourceforge.net/mailarchive/forum.php?forum_name=matplotlib-users
(on the other hand, the devel archive seems fine). No messages appear
for August and September

On 9/12/2012 7:44 AM, Michael Droettboom wrote:
> I have tagged and created a tarball for 1.2.0rc1. The githash is
> bda6dd9feab8. The tarball is on the github download page here:
>
> https://github.com/matplotlib/matplotlib/downloads
>
> I have created a new branch, v1.2.x, for continuing 1.2.x development.
> The feature freeze on master is now lifted and big experimental changes
> can be merged into master. Any bugfixes that need to go into 1.2.x
> should be merged into both places. Please mark any PRs for the 1.2.x
> branch with the 1.2.x milestone so we can verify that things are merged
> in both places.
>
> For those creating the Windows and Macintosh builds, let's try using the
> github download page rather than the one at Sourceforge this time. It
> is a lot simpler.
>
> For those creating distro packages, now is a good time to let us know
> what can be done to make the inclusion of matplotlib 1.2.0 as smooth as
> possible.
>
> Once the binaries are available, I will make an announcement to
> matplotlib-users.
>
> Mike
>
>
Can we hold the Windows binaries until rc2? Setup.py corrupts the pytz 
package, leading to stack-overflows on Python 3 and other problems on 
Python 2.
Christoph

On 12 September 2012 15:44, Michael Droettboom <md...@st...> wrote:
> For those creating distro packages, now is a good time to let us know what
> can be done to make the inclusion of matplotlib 1.2.0 as smooth as possible.
I think I've mentioned before, but whoever does the Debian packages is
welcome to use code from my bzr branch here:
https://code.launchpad.net/~takluyver/matplotlib/debian-daily
It's successfully building packages from master, including Python 3
packages, using the Launchpad recipe system:
https://code.launchpad.net/~takluyver/+recipe/matplotlib-daily
Thanks,
Thomas

I have tagged and created a tarball for 1.2.0rc1. The githash is 
bda6dd9feab8. The tarball is on the github download page here:
https://github.com/matplotlib/matplotlib/downloads
I have created a new branch, v1.2.x, for continuing 1.2.x development. 
The feature freeze on master is now lifted and big experimental changes 
can be merged into master. Any bugfixes that need to go into 1.2.x 
should be merged into both places. Please mark any PRs for the 1.2.x 
branch with the 1.2.x milestone so we can verify that things are merged 
in both places.
For those creating the Windows and Macintosh builds, let's try using the 
github download page rather than the one at Sourceforge this time. It 
is a lot simpler.
For those creating distro packages, now is a good time to let us know 
what can be done to make the inclusion of matplotlib 1.2.0 as smooth as 
possible.
Once the binaries are available, I will make an announcement to 
matplotlib-users.
Mike

Hello,
This may be a silly question, but I'm wondering what happens in
Matplotlib rendering when there is a "big" Line2D object (say 10**7
points) added to an Axes, with *visibility set to false*.
Here is an tiny script meant to be run interactively (say with Python in
pylab mode) step by step :
https://gist.github.com/3638471
I'm experiencing a strange slowdown of Axes rendering when such a "big
line" is added to the Axes, despite the fact it is invisible. So I'm
wondering if this is an expected behavior or a some kind of bug. Or
maybe it's a well known fact, already fixed in the upcoming 1.2 release
and in that case sorry for the duplicate.
Best,
Pierre
PS: I'm using Matplotlib version 1.1.1rc2, from Debian Testing. Today
TkAgg backend, but the other day same problem happened with Qt.

On 9/10/2012 10:08 AM, Michael Droettboom wrote:
> On 09/10/2012 12:49 PM, Mark Lawrence wrote:
>> My offer to test on Windows still holds. The question is test what?
>> Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then
>> different versions of Visual Studio are needed as detailed here
>> http://bugs.python.org/issue13210. I can't see much sense in me trying
>> to build and test all that lot while other volunteers are doing exactly
>> the same thing at the same time. Is there a cunning plan somewhere to
>> cover this that I've missed?
>>
>
> The process is usually that the release is tagged in github, a tarball
> is created, and then various platform specialists create the binary
> releases. For the last release Christoph Gohlke did the Windows builds,
> and I assume he is able to do that again this time. Perhaps it makes
> sense to coordinate with him to share some of that work? Anything we
> can do to lessen the burden on any one person is always appreciated.
>
> Even leading up to the tagging of the release candidate, it's always
> helpful to build from github periodically and test on the platform and
> version of Python that's most important to you, and report back into the
> issue tracker any test failures or other glitches.
>
> Mike
>
Hello,
sure, I can provide the Windows binaries and run tests. I have not tried 
recent master, but I am using a ~2 month old build on Python 3.2 and 3.3 
without any issues. As for Python 3.3, there were no problems building 
matplotlib with Visual Studio 2010, but there is no official numpy 
release supporting Python 3.3 yet. I also have a PIL fork that works on 
Python 3, which is good for testing.
Christoph

On Mon, Sep 10, 2012 at 5:00 PM, Michael Droettboom <md...@st...> wrote:
> We have a few outstanding issues, which I'll categorize below:
>
> Critical things that need just a little more work:
>
> #1223 dpi= for bitmaps not handled correctly
I don't believe this is release critical. It only affects metadata.
Eric has fixed this for TIFFs but there may be outstanding issues with
other bitmap types. My feeling is that the below issues should receive
more attention.
> #1209 Pass linewidth to Mac context properly
> #786 savefig() renders paths and text differently than show()
> #113 dpi= doesn't seem to have any effect with MacOS X backend
Michiel has provided great feedback regarding the previously proposed
solution to part of this problem, and this has been reflected in the
updated pull request.
-- 
Damon McDougall
http://www.damon.is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

On 09/10/2012 12:49 PM, Mark Lawrence wrote:
> My offer to test on Windows still holds. The question is test what?
> Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then
> different versions of Visual Studio are needed as detailed here
> http://bugs.python.org/issue13210. I can't see much sense in me trying
> to build and test all that lot while other volunteers are doing exactly
> the same thing at the same time. Is there a cunning plan somewhere to
> cover this that I've missed?
>
The process is usually that the release is tagged in github, a tarball 
is created, and then various platform specialists create the binary 
releases. For the last release Christoph Gohlke did the Windows builds, 
and I assume he is able to do that again this time. Perhaps it makes 
sense to coordinate with him to share some of that work? Anything we 
can do to lessen the burden on any one person is always appreciated.
Even leading up to the tagging of the release candidate, it's always 
helpful to build from github periodically and test on the platform and 
version of Python that's most important to you, and report back into the 
issue tracker any test failures or other glitches.
Mike

On 10/09/2012 17:00, Michael Droettboom wrote:
> Today is the scheduled day for release candidate 1.2rc1.
>
> We seem to be in really good shape. Thanks to everyone that has been
> working so hard to squash bugs, particularly ones that turned out to be
> bottomless rabbit holes.
>
> We have a few outstanding issues, which I'll categorize below:
>
> Critical things that need just a little more work:
>
> #1223 dpi= for bitmaps not handled correctly
> #1209 Pass linewidth to Mac context properly
> #786 savefig() renders paths and text differently than show()
> #113 dpi= doesn't seem to have any effect with MacOS X backend
>
> #1208 FAIL: matplotlib.tests.test_text.test_contains.test
> release_critical
> #1176 Reverted a previous change to artist transform setting. Fixes
> legend bug.
>
> Non-critical features that are near completion -- just needing some
> confirmation or testing:
>
> #847 Add stacked kwarg to hist and implement stacked hists for step
> histtype
> #751 Building on osx with python 3.2 OSX
>
> Problems requiring a fix in another project:
>
> #1126 Qt4 save dialog not functional on CentOS-5
>
> Things that are probably too big to fix now, but deserve warnings in the
> release notes:
>
> #854 Bug in Axes.relim when the first line is y_isdata=False and
> possible fix
> #740 plt.pcolormesh and shape mismatch
> #162 twinx and plot_date confirmed
>
> Reminders for the release manager:
>
> #1207 Add contributor and git stats to documentation
> #1070 Use github for downloads
>
> I will write prose for the "too big to fix now" stuff, and I trust the
> other close things will get done by their respective authors. Then we're
> very close to getting a release candidate out.
>
> Congratulations to everyone for a job well done!
>
> Mike
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
My offer to test on Windows still holds. The question is test what? 
Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then 
different versions of Visual Studio are needed as detailed here 
http://bugs.python.org/issue13210. I can't see much sense in me trying 
to build and test all that lot while other volunteers are doing exactly 
the same thing at the same time. Is there a cunning plan somewhere to 
cover this that I've missed?
-- 
Cheers.
Mark Lawrence.

I'd certainly like to see that work continue, but I don't know if it's 
worth holding up the release candidate for. We probably won't get it 
out today given the other critical things yet to go in -- but once the 
release candidate is cut, I'd prefer to be really conservative about 
what changes go in before the final release. We can continue your great 
PEP8 work on master (after the 1.2.x maintenance branch is created), of 
course.
Mike
On 09/10/2012 12:10 PM, Nelle Varoquaux wrote:
> Hello,
>
> Do you still accept pep8 cleaning up ? I've got a couple of important 
> deadlines coming up soon, but I might be able to clean up the whole code.
>
> Thanks,
> N
>
> On 10 September 2012 18:00, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
> Today is the scheduled day for release candidate 1.2rc1.
>
> We seem to be in really good shape. Thanks to everyone that has been
> working so hard to squash bugs, particularly ones that turned out
> to be
> bottomless rabbit holes.
>
> We have a few outstanding issues, which I'll categorize below:
>
> Critical things that need just a little more work:
>
> #1223 dpi= for bitmaps not handled correctly
> #1209 Pass linewidth to Mac context properly
> #786 savefig() renders paths and text differently than show()
> #113 dpi= doesn't seem to have any effect with MacOS X backend
>
> #1208 FAIL: matplotlib.tests.test_text.test_contains.test
> release_critical
> #1176 Reverted a previous change to artist transform setting. Fixes
> legend bug.
>
> Non-critical features that are near completion -- just needing some
> confirmation or testing:
>
> #847 Add stacked kwarg to hist and implement stacked hists for step
> histtype
> #751 Building on osx with python 3.2 OSX
>
> Problems requiring a fix in another project:
>
> #1126 Qt4 save dialog not functional on CentOS-5
>
> Things that are probably too big to fix now, but deserve warnings
> in the
> release notes:
>
> #854 Bug in Axes.relim when the first line is y_isdata=False and
> possible fix
> #740 plt.pcolormesh and shape mismatch
> #162 twinx and plot_date confirmed
>
> Reminders for the release manager:
>
> #1207 Add contributor and git stats to documentation
> #1070 Use github for downloads
>
> I will write prose for the "too big to fix now" stuff, and I trust the
> other close things will get done by their respective authors. Then
> we're
> very close to getting a release candidate out.
>
> Congratulations to everyone for a job well done!
>
> Mike
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions
> will include endpoint security, mobile security and the latest in
> malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Hello,
Do you still accept pep8 cleaning up ? I've got a couple of important
deadlines coming up soon, but I might be able to clean up the whole code.
Thanks,
N
On 10 September 2012 18:00, Michael Droettboom <md...@st...> wrote:
> Today is the scheduled day for release candidate 1.2rc1.
>
> We seem to be in really good shape. Thanks to everyone that has been
> working so hard to squash bugs, particularly ones that turned out to be
> bottomless rabbit holes.
>
> We have a few outstanding issues, which I'll categorize below:
>
> Critical things that need just a little more work:
>
> #1223 dpi= for bitmaps not handled correctly
> #1209 Pass linewidth to Mac context properly
> #786 savefig() renders paths and text differently than show()
> #113 dpi= doesn't seem to have any effect with MacOS X backend
>
> #1208 FAIL: matplotlib.tests.test_text.test_contains.test
> release_critical
> #1176 Reverted a previous change to artist transform setting. Fixes
> legend bug.
>
> Non-critical features that are near completion -- just needing some
> confirmation or testing:
>
> #847 Add stacked kwarg to hist and implement stacked hists for step
> histtype
> #751 Building on osx with python 3.2 OSX
>
> Problems requiring a fix in another project:
>
> #1126 Qt4 save dialog not functional on CentOS-5
>
> Things that are probably too big to fix now, but deserve warnings in the
> release notes:
>
> #854 Bug in Axes.relim when the first line is y_isdata=False and
> possible fix
> #740 plt.pcolormesh and shape mismatch
> #162 twinx and plot_date confirmed
>
> Reminders for the release manager:
>
> #1207 Add contributor and git stats to documentation
> #1070 Use github for downloads
>
> I will write prose for the "too big to fix now" stuff, and I trust the
> other close things will get done by their respective authors. Then we're
> very close to getting a release candidate out.
>
> Congratulations to everyone for a job well done!
>
> Mike
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Today is the scheduled day for release candidate 1.2rc1.
We seem to be in really good shape. Thanks to everyone that has been 
working so hard to squash bugs, particularly ones that turned out to be 
bottomless rabbit holes.
We have a few outstanding issues, which I'll categorize below:
Critical things that need just a little more work:
#1223 dpi= for bitmaps not handled correctly
#1209 Pass linewidth to Mac context properly
#786 savefig() renders paths and text differently than show()
#113 dpi= doesn't seem to have any effect with MacOS X backend
#1208 FAIL: matplotlib.tests.test_text.test_contains.test 
release_critical
#1176 Reverted a previous change to artist transform setting. Fixes 
legend bug.
Non-critical features that are near completion -- just needing some 
confirmation or testing:
#847 Add stacked kwarg to hist and implement stacked hists for step 
histtype
#751 Building on osx with python 3.2 OSX
Problems requiring a fix in another project:
#1126 Qt4 save dialog not functional on CentOS-5
Things that are probably too big to fix now, but deserve warnings in the 
release notes:
#854 Bug in Axes.relim when the first line is y_isdata=False and 
possible fix
#740 plt.pcolormesh and shape mismatch
#162 twinx and plot_date confirmed
Reminders for the release manager:
#1207 Add contributor and git stats to documentation
#1070 Use github for downloads
I will write prose for the "too big to fix now" stuff, and I trust the 
other close things will get done by their respective authors. Then we're 
very close to getting a release candidate out.
Congratulations to everyone for a job well done!
Mike

On Sun, Sep 9, 2012 at 3:24 PM, Benjamin Root <ben...@ou...> wrote:
>
>
> On Tue, Apr 17, 2012 at 10:02 AM, Jostein Bø Fløystad <
> jos...@gm...> wrote:
>
>> Ben,
>>
>> That sounds great, especially regarding the test images. I don't know
>> how the image comparison tests work, that's why I kept it very
>> fundamental.
>>
>> Thanks!
>>
>> Jostein.
>>
>>
> Just rediscovered this. I will go ahead and create the PR so that this
> gets included in v1.2.0.
>
> Ben Root
>
Submitted as PR #1224: https://github.com/matplotlib/matplotlib/pull/1224
Cheers!
Ben Root

On Tue, Apr 17, 2012 at 10:02 AM, Jostein Bø Fløystad <
jos...@gm...> wrote:
> Ben,
>
> That sounds great, especially regarding the test images. I don't know
> how the image comparison tests work, that's why I kept it very
> fundamental.
>
> Thanks!
>
> Jostein.
>
>
Just rediscovered this. I will go ahead and create the PR so that this
gets included in v1.2.0.
Ben Root

On 2012年09月09日 9:01 AM, Benjamin Root wrote:
> Did we remember to put in a deprecation notice for Qt3 support?
I don't think so. Presumably it should be a deprecation warning upon 
importing backend_qt, and a note in whats_new.
Eric
>
> Ben Root
>
> On Tue, Jul 10, 2012 at 11:44 AM, Darren Dale <dsd...@gm...
> <mailto:dsd...@gm...>> wrote:
>
> On Tue, Jul 10, 2012 at 8:54 AM, Benjamin Root <ben...@ou...
> <mailto:ben...@ou...>> wrote:
> >
> >
> > On Tue, Jul 10, 2012 at 3:54 AM, Eric Firing <ef...@ha...
> <mailto:ef...@ha...>> wrote:
> >>
> >> Is there any good reason *not* to delete support for Qt3 from
> master?
> >> Is anyone who is using it likely to be able to upgrade to the
> next mpl
> >> release, and yet *not* be able to install Qt4 and its bindings?
> Note
> >> that ipython no longer supports Qt3.
> >>
> >> Eric
> >>
> >
> > CentOS5 and RHEL5 both have qt3 as part of the stock install
> (although it
> > does look like qt4 is available). CentOS6 and RHEL6 seem to have
> qt4 as
> > default, with pyqt as well.
> >
> > Personally, I see no real reason to get rid of it quite yet as it
> doesn't
> > seem to be much of a support burden -- yet. If anything, we
> might want to
> > consider putting deprecation notices for that backend in the next
> release.
>
> I also think its coming up on time to retire the Qt-3 backend, but
> perhaps a deprecation notice in mpl-1.2 and removal in mpl-1.3 would
> be appropriate. Then again, if mpl-1.2 supports python3, maybe that
> would be a good time to delete the Qt3 backend, since there is no
> python-3 binding for Qt3.
>
> By the way, Qt-5 is expected in September. Hopefully it won't require
> a dedicated backend, it sounds like PyQt4 will support Qt5's QtCore
> and QtGui libraries.
>
> Darren
>
>

Did we remember to put in a deprecation notice for Qt3 support?
Ben Root
On Tue, Jul 10, 2012 at 11:44 AM, Darren Dale <dsd...@gm...> wrote:
> On Tue, Jul 10, 2012 at 8:54 AM, Benjamin Root <ben...@ou...> wrote:
> >
> >
> > On Tue, Jul 10, 2012 at 3:54 AM, Eric Firing <ef...@ha...> wrote:
> >>
> >> Is there any good reason *not* to delete support for Qt3 from master?
> >> Is anyone who is using it likely to be able to upgrade to the next mpl
> >> release, and yet *not* be able to install Qt4 and its bindings? Note
> >> that ipython no longer supports Qt3.
> >>
> >> Eric
> >>
> >
> > CentOS5 and RHEL5 both have qt3 as part of the stock install (although it
> > does look like qt4 is available). CentOS6 and RHEL6 seem to have qt4 as
> > default, with pyqt as well.
> >
> > Personally, I see no real reason to get rid of it quite yet as it doesn't
> > seem to be much of a support burden -- yet. If anything, we might want
> to
> > consider putting deprecation notices for that backend in the next
> release.
>
> I also think its coming up on time to retire the Qt-3 backend, but
> perhaps a deprecation notice in mpl-1.2 and removal in mpl-1.3 would
> be appropriate. Then again, if mpl-1.2 supports python3, maybe that
> would be a good time to delete the Qt3 backend, since there is no
> python-3 binding for Qt3.
>
> By the way, Qt-5 is expected in September. Hopefully it won't require
> a dedicated backend, it sounds like PyQt4 will support Qt5's QtCore
> and QtGui libraries.
>
> Darren
>

On 2012年09月07日 6:56 AM, Daniel Hyams wrote:
> I do, but I'm not wedded to it; I'll use whatever is there. The
> convenience of it is that it downloaded dependencies and built them for
> you. Will setup.py do the same?
No, it won't. The problem with make.osx in that regard is that the 
dependencies and their urls are version-dependent and ever-changing, so 
a single make.osx would need to be much more complex than the present 
one is, and to be maintained, which the present one mostly was not.
Eric
>
> On Fri, Sep 7, 2012 at 12:32 PM, Michael Droettboom <md...@st...
> <mailto:md...@st...>> wrote:
>
> There is a discussion in a pull request about whether it is still
> needed.
>
> https://github.com/matplotlib/matplotlib/issues/751
>
> It would be nice to have one obvious way to build on OS-X, so it makes
> sense to remove this file in that case. However, I thought it might be
> worth casting this question out before doing so.
>
> Cheers,
> Mike
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions
> will include endpoint security, mobile security and the latest in
> malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
>
> --
> Daniel Hyams
> dh...@gm... <mailto:dh...@gm...>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

I do, but I'm not wedded to it; I'll use whatever is there. The
convenience of it is that it downloaded dependencies and built them for
you. Will setup.py do the same?
On Fri, Sep 7, 2012 at 12:32 PM, Michael Droettboom <md...@st...> wrote:
> There is a discussion in a pull request about whether it is still needed.
>
> https://github.com/matplotlib/matplotlib/issues/751
>
> It would be nice to have one obvious way to build on OS-X, so it makes
> sense to remove this file in that case. However, I thought it might be
> worth casting this question out before doing so.
>
> Cheers,
> Mike
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
-- 
Daniel Hyams
dh...@gm...

There is a discussion in a pull request about whether it is still needed.
https://github.com/matplotlib/matplotlib/issues/751
It would be nice to have one obvious way to build on OS-X, so it makes 
sense to remove this file in that case. However, I thought it might be 
worth casting this question out before doing so.
Cheers,
Mike

Hi all,
I have just received the following information from John's family
regarding the memorial service:
John's memorial service will be held on Monday, October 1, 2012, at
11.a.m. at Rockefeller Chapel at the University of Chicago. The exact
address is 5850 S. Woodlawn Ave, Chicago, IL 60615. The service is
open to the public. The service will be fully planned and scripted
with no room for people to eulogize, however, we will have a reception
after the service, hosted by Tradelink, where people can talk.
Regards,
f