matplotlib-devel Mailing List for matplotlib

On 05/31/2012 11:16 AM, Benjamin Root wrote:
>
>
> On Thu, May 31, 2012 at 7:55 AM, John Hunter <jd...@gm... 
> <mailto:jd...@gm...>> wrote:
>
> Phil Elson has been making pull requests for some time now on matters
> great and small, from hairy transformations improvements to minor
> docstring cleanups to GUI fixes. Given his prolific work, I thought
> it would be suitable to recognize him as a core matplotlib developer
> by adding him to the github organization. While the distributed
> nature of the github system blurs the line between official and
> regular developers, it is helpful to recognize those who make frequent
> quality contributions and give them the permissions to merge pull
> requests into the main repo.
>
> Thanks for all your help Phil, and welcome aboard.
>
> JDH
>
>
> Welcom, Phil! Keep up the good work!
>
> Cheers!
> Ben Root
Agreed! Glad to have you on board!
Mike

On Thu, May 31, 2012 at 7:55 AM, John Hunter <jd...@gm...> wrote:
> Phil Elson has been making pull requests for some time now on matters
> great and small, from hairy transformations improvements to minor
> docstring cleanups to GUI fixes. Given his prolific work, I thought
> it would be suitable to recognize him as a core matplotlib developer
> by adding him to the github organization. While the distributed
> nature of the github system blurs the line between official and
> regular developers, it is helpful to recognize those who make frequent
> quality contributions and give them the permissions to merge pull
> requests into the main repo.
>
> Thanks for all your help Phil, and welcome aboard.
>
> JDH
>
>
Welcom, Phil! Keep up the good work!
Cheers!
Ben Root

2to3 is run on the source files in lib/matplotlib, which are then put 
under the build directory. Think of it like a compilation step -- the 
original source files should never be touched. You will need to install 
matplotlib (I recommend using virtualenv for this) in order to run it.
Mike
On 05/30/2012 10:30 PM, Tom Lippman wrote:
> Hi All,
>
> I've gotten it somewhat working. For some reason the build process 
> isn't pointing 2to3 at the files in lib/matplotlib. But it's 
> definitely running 2to3 on something..
>
> Like the linked solution, I changed setupext.py to look for the 
> dependencies in /usr/local. I also made a new makefile and setupeggs 
> which are changed in obvious ways. The changes are on my github 
> (tmlippman).
>
> Rather than copy folders manually, I ran make twice:
>
> sudo make -f make.py3.osx PREFIX=/usr/local fetch deps
>
> sudo make -f make.py3.osx 
> PREFIX=/Library/Frameworks/Python.framework/Versions/3.2 mpl_build 
> mpl_install_develop
>
> (outputs attached)
>
> Everything appeared to compile fine, but when I tried to import 
> matplotlib, I got errors like: ImportError: No module named cPickle.
>
> After running 2to3 on the lib/matplotlib directory (in my source 
> location) everything works.
>
>
> Tom
>
>
>
>
> On May 30, 2012, at 2:40 PM, Michael Droettboom wrote:
>
> > On 05/30/2012 03:32 PM, Thomas Kluyver wrote:
> >> On 30 May 2012 20:05, Tom Lippman<tom...@gm...> wrote:
> >>> I'm on OS X 10.7, using the python 3.2
> >> I saw someone recently who'd managed to get it built for Python 3 on
> >> OS X. I suggested he come here to help simplify the process - this is
> >> what he did: http://stackoverflow.com/a/10574470/434217
> >>
> >> Thomas
> >>
> > It would be great to convert that post in a pull request so it can be
> > included upstream. I'm not a Mac user myself, but I think there's
> > enough Mac users to test that and push it through to make things easier
> > on everyone else.
> >
> > 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
>

Phil Elson has been making pull requests for some time now on matters
great and small, from hairy transformations improvements to minor
docstring cleanups to GUI fixes. Given his prolific work, I thought
it would be suitable to recognize him as a core matplotlib developer
by adding him to the github organization. While the distributed
nature of the github system blurs the line between official and
regular developers, it is helpful to recognize those who make frequent
quality contributions and give them the permissions to merge pull
requests into the main repo.
Thanks for all your help Phil, and welcome aboard.
JDH

Hi All,
I've gotten it somewhat working. For some reason the build process isn't pointing 2to3 at the files in lib/matplotlib. But it's definitely running 2to3 on something..
Like the linked solution, I changed setupext.py to look for the dependencies in /usr/local. I also made a new makefile and setupeggs which are changed in obvious ways. The changes are on my github (tmlippman).
Rather than copy folders manually, I ran make twice:
	sudo make -f make.py3.osx PREFIX=/usr/local fetch deps
	sudo make -f make.py3.osx PREFIX=/Library/Frameworks/Python.framework/Versions/3.2 mpl_build mpl_install_develop
(outputs attached)
Everything appeared to compile fine, but when I tried to import matplotlib, I got errors like: ImportError: No module named cPickle.
After running 2to3 on the lib/matplotlib directory (in my source location) everything works.
Tom

On 05/30/2012 03:32 PM, Thomas Kluyver wrote:
> On 30 May 2012 20:05, Tom Lippman<tom...@gm...> wrote:
>> I'm on OS X 10.7, using the python 3.2
> I saw someone recently who'd managed to get it built for Python 3 on
> OS X. I suggested he come here to help simplify the process - this is
> what he did: http://stackoverflow.com/a/10574470/434217
>
> Thomas
>
It would be great to convert that post in a pull request so it can be 
included upstream. I'm not a Mac user myself, but I think there's 
enough Mac users to test that and push it through to make things easier 
on everyone else.
Mike

On 30 May 2012 19:49, Tom Lippman <tom...@gm...> wrote:
> I saw that matplotlib had been ported to python 3 (here), and that the
> matplotlib-py3 branch was merged back into the main branch. So I assumed
> matplotlib was compatible with python 3, and went ahead and tried to use it.
> It didn't work. Is there a different fork which is compatible with python
> 3? What happened?
How did you try to use it? The released version doesn't support Python
3, but the development version on Github does. For Ubuntu, I've got a
daily-build PPA which includes python3-matplotlib:
https://launchpad.net/~takluyver/+archive/matplotlib-daily
Thomas

The git master is compatible with Python 3, but it has not made it into 
a release.
Will be making at least one more 1.1.x bugfix release which will support 
Python 2.4 - 2.7 before making the next major release which will support 
Python 2.6 - 3.2.
Mike
On 05/30/2012 02:49 PM, Tom Lippman wrote:
> Hi All,
>
> I saw that matplotlib had been ported to python 3 (here 
> <http://pythonsprints.com/2011/04/8/matplotlib-python-3-thanks-cape-town-group/>), 
> and that the matplotlib-py3 branch was merged back into the main 
> branch. So I assumed matplotlib was compatible with python 3, and 
> went ahead and tried to use it. It didn't work. Is there a different 
> fork which is compatible with python 3? What happened?
>
> thanks,
>
> Tom
>
>
> ------------------------------------------------------------------------------
> 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

On 30 May 2012 20:05, Tom Lippman <tom...@gm...> wrote:
> I'm on OS X 10.7, using the python 3.2
I saw someone recently who'd managed to get it built for Python 3 on
OS X. I suggested he come here to help simplify the process - this is
what he did: http://stackoverflow.com/a/10574470/434217
Thomas

I cloned the master branch on github and built it. I'm on OS X 10.7, using the python 3.2 from python.org. I installed fresh dependencies like in the osx makefile. Then I had to run 2to3 on setupegg.py to get it to build. Now when I try to import matplotlib in python3 I get a bunch of errors - e.g. it's looking for cPickle instead of pickle.
Tom
On May 30, 2012, at 11:54 AM, Thomas Kluyver wrote:
> On 30 May 2012 19:49, Tom Lippman <tom...@gm...> wrote:
>> I saw that matplotlib had been ported to python 3 (here), and that the
>> matplotlib-py3 branch was merged back into the main branch. So I assumed
>> matplotlib was compatible with python 3, and went ahead and tried to use it.
>> It didn't work. Is there a different fork which is compatible with python
>> 3? What happened?
> 
> How did you try to use it? The released version doesn't support Python
> 3, but the development version on Github does. For Ubuntu, I've got a
> daily-build PPA which includes python3-matplotlib:
> https://launchpad.net/~takluyver/+archive/matplotlib-daily
> 
> Thomas

On Wed, May 30, 2012 at 2:49 PM, Tom Lippman <tom...@gm...> wrote:
> Hi All,
>
> I saw that matplotlib had been ported to python 3 (here<http://pythonsprints.com/2011/04/8/matplotlib-python-3-thanks-cape-town-group/>),
> and that the matplotlib-py3 branch was merged back into the main branch.
> So I assumed matplotlib was compatible with python 3, and went ahead and
> tried to use it. It didn't work. Is there a different fork which is
> compatible with python 3? What happened?
>
> thanks,
>
> Tom
>
>
We have not done an official release yet with py3k support. Only the
master branch has that. What did you test?
Ben Root

Hi All,
I saw that matplotlib had been ported to python 3 (here), and that the matplotlib-py3 branch was merged back into the main branch. So I assumed matplotlib was compatible with python 3, and went ahead and tried to use it. It didn't work. Is there a different fork which is compatible with python 3? What happened?
thanks,
Tom

On 2012年5月26日 at 03:30PM -1000, Eric Firing wrote:
> It is easy enough to remove the immediate roadblock in scale_range,
> but that just opens up a can of floating point worms. The axis spines
> start getting misplaced, for example, as the range being plotted gets
> too small relative to the offset. Straightening all this out, or even
> substantially improving it, is potentially tricky. To the extent that
> it can be done, it will have to be in master, which already includes
> one cleanup of a floating point kluge.
> 
> Note that part of the problem here is that in your example we are
> running out of precision. The best way to handle it is to subtract an
> offset first, and just plot the deviation from that offset. I think
> this is best done at the application level. We can probably make
> mpl's handling of the problem degrade more gracefully, however, than
> it does at present.
Thanks for your help. I'll look at your links and see what we can do.
Dan
--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------

On 05/25/2012 12:46 PM, Dan Drake wrote:
> Hello matplotlib developers,
>
> In Sage, we've run into a problem with plotting a sequence whose
> y-values change by very small amounts. Here's an example that doesn't
> use anything from Sage:
>
> import pylab
> pylab.plot([0, 1], [0, 1e-14])
> pylab.savefig("works.png")
> pylab.close()
> pylab.plot([0, 1], [1, 1+1e-14])
> pylab.savefig("fails.png")
> pylab.close()
>
> We're using matplotlib 1.1. Here's a trac ticket where we are working on
> this: http://trac.sagemath.org/sage_trac/ticket/11973. One of our
> developers suspects matplotlib.ticker.MaxNLocator.bin_boundaries but we
> don't really know.
See https://github.com/matplotlib/matplotlib/pull/904
Eric
>
> Thanks for any help or comments!
>
> Dan
>
> --
> --- Dan Drake
> ----- http://mathsci.kaist.ac.kr/~drake
> -------

On 05/25/2012 12:46 PM, Dan Drake wrote:
> Hello matplotlib developers,
>
> In Sage, we've run into a problem with plotting a sequence whose
> y-values change by very small amounts. Here's an example that doesn't
> use anything from Sage:
>
> import pylab
> pylab.plot([0, 1], [0, 1e-14])
> pylab.savefig("works.png")
> pylab.close()
> pylab.plot([0, 1], [1, 1+1e-14])
> pylab.savefig("fails.png")
> pylab.close()
>
> We're using matplotlib 1.1. Here's a trac ticket where we are working on
> this: http://trac.sagemath.org/sage_trac/ticket/11973. One of our
> developers suspects matplotlib.ticker.MaxNLocator.bin_boundaries but we
> don't really know.
Dan,
It is easy enough to remove the immediate roadblock in scale_range, but 
that just opens up a can of floating point worms. The axis spines start 
getting misplaced, for example, as the range being plotted gets too 
small relative to the offset. Straightening all this out, or even 
substantially improving it, is potentially tricky. To the extent that 
it can be done, it will have to be in master, which already includes one 
cleanup of a floating point kluge.
Note that part of the problem here is that in your example we are 
running out of precision. The best way to handle it is to subtract an 
offset first, and just plot the deviation from that offset. I think 
this is best done at the application level. We can probably make mpl's 
handling of the problem degrade more gracefully, however, than it does 
at present.
Eric
>
> Thanks for any help or comments!
>
> Dan
>
> --
> --- Dan Drake
> ----- http://mathsci.kaist.ac.kr/~drakes
> -------

On Saturday, May 26, 2012, Jason Grout wrote:
> I just noticed at the bottom of each message in a dozen or so that I
> checked from the last few days, I see an ad entitled "Live Security
> Virtual Conference". I don't see these ads on messages in the
> sourceforge archive [1], but I do see them on the gmane mirror [2]. I
> also see the ad in a reply on the sourceforge archive [3].
>
> I'm curious: Is this ad being put into outgoing messages by sourceforge,
> but not included in the archive (except when explicitly quoted in a
> reply)? Or is there some other source for the ad?
>
> Thanks,
>
> Jason
>
> [1] http://sourceforge.net/mailarchive/message.php?msg_id=29253604
>
> [2] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/11060
>
> [3] http://sourceforge.net/mailarchive/message.php?msg_id=29253751
>
>
Sourceforge does need to make money somehow, right? It doesnt go into
archives because most ads are time-sensitive.
Ben Root

I just noticed at the bottom of each message in a dozen or so that I 
checked from the last few days, I see an ad entitled "Live Security 
Virtual Conference". I don't see these ads on messages in the 
sourceforge archive [1], but I do see them on the gmane mirror [2]. I 
also see the ad in a reply on the sourceforge archive [3].
I'm curious: Is this ad being put into outgoing messages by sourceforge, 
but not included in the archive (except when explicitly quoted in a 
reply)? Or is there some other source for the ad?
Thanks,
Jason
[1] http://sourceforge.net/mailarchive/message.php?msg_id=29253604
[2] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/11060
[3] http://sourceforge.net/mailarchive/message.php?msg_id=29253751

On 05/25/2012 12:46 PM, Dan Drake wrote:
> Hello matplotlib developers,
>
> In Sage, we've run into a problem with plotting a sequence whose
> y-values change by very small amounts. Here's an example that doesn't
> use anything from Sage:
>
> import pylab
> pylab.plot([0, 1], [0, 1e-14])
> pylab.savefig("works.png")
> pylab.close()
> pylab.plot([0, 1], [1, 1+1e-14])
> pylab.savefig("fails.png")
> pylab.close()
>
> We're using matplotlib 1.1. Here's a trac ticket where we are working on
> this: http://trac.sagemath.org/sage_trac/ticket/11973. One of our
> developers suspects matplotlib.ticker.MaxNLocator.bin_boundaries but we
> don't really know.
Dan,
I think the behavior is coming from a threshold value of 1e-12 in 
ticker.scale_range. This needs more thought than I can give it at the 
moment, but perhaps you could file a ticket on the github mpl site.
Note that even if this threshold behavior is removed, there is another 
one waiting in the wings behind it, with a default value of 1e-16, used 
to decide whether a range is singular; if it is, then it gets expanded.
Eric
>
> Thanks for any help or comments!
>
> Dan

Hello matplotlib developers,
In Sage, we've run into a problem with plotting a sequence whose
y-values change by very small amounts. Here's an example that doesn't
use anything from Sage:
import pylab
pylab.plot([0, 1], [0, 1e-14])
pylab.savefig("works.png")
pylab.close()
pylab.plot([0, 1], [1, 1+1e-14])
pylab.savefig("fails.png")
pylab.close()
We're using matplotlib 1.1. Here's a trac ticket where we are working on
this: http://trac.sagemath.org/sage_trac/ticket/11973. One of our
developers suspects matplotlib.ticker.MaxNLocator.bin_boundaries but we
don't really know.
Thanks for any help or comments!
Dan
--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------

Please accept my apologies for this spam. I guess its time to get a
better email provider for my mailing lists.
Regards,

Make a profit with this strategy. http://ponto.kelly-systems.com.br/twitter.news.php?uffriend_id=07a4
 		 	 		 

On 05/20/2012 12:51 PM, Sandro Tosi wrote:
> Hello,
> I've been trying to fix this problem for hours, and it's getting me
> mad but to no conclusion, so I'm asking here.
>
> In Debian we build our packges in a chroot, with all the minimum
> dependecies needed to build the package (to guarantee reproducibility
> and avoid weird effect of local installed packages), and so also the
> unittests are runt here. While enabling the matplotlib unittest in
> that chroot, I'm getting this error:
>
> ======================================================================
> ERROR: matplotlib.tests.test_axes.test_arc_ellipse.test
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/usr/lib/python2.6/dist-packages/nose/case.py", line 197, in runTest
> self.test(*self.arg)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
> line 36, in failer
> result = f(*args, **kwargs)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
> line 128, in do_test
> figure.savefig(actual_fname)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/figure.py",
> line 1185, in savefig
> self.canvas.print_figure(*args, **kwargs)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backend_bases.py",
> line 2021, in print_figure
> **kwargs)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backend_bases.py",
> line 1789, in print_pdf
> return pdf.print_pdf(*args, **kwargs)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backends/backend_pdf.py",
> line 2180, in print_pdf
> file = PdfFile(filename)
> File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backends/backend_pdf.py",
> line 378, in __init__
> rcParams['datapath'], 'fonts', 'pdfcorefonts')
> File "/usr/lib/python2.6/posixpath.py", line 67, in join
> elif path == '' or path.endswith('/'):
> AttributeError: 'NoneType' object has no attribute 'endswith'
I'm not sure about this one. Could it be due to not having a font cache 
in ~/.matplotlib?
>
> (repeated for several times, it seems like a patter, given the output
> of the test execution is:
>
> ..K.............EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK..EK.EK.EK.EK.EK.EK.EKK...EK...EK.EK..EKEK..EK.EK.EK.EK.EK..EK.EK.EK[....]
>
> and so on) so it seems the code can't find the datapath location. In
> order to fix that, I'm calling the test suite like this:
This is most likely due to some of the testing dependencies not being 
present. matplotlib uses ghostscript for rendering PDF and inkscape for 
rendering SVG (but only when testing). See this documentation:
http://matplotlib.sourceforge.net/devel/coding_guide.html#testing
(Note the the PIL requirement goes away with matplotlib git master -- 
it's only required for the 1.1.x series).
>
> PYTHONPATH=build/lib.linux-x86_64-2.6 \
> MATPLOTLIBDATA=/tmp/buildd/matplotlib-1.1.1~rc1/lib/matplotlib/mpl-data/
> \
> MPLCONFIGDIR=. \
> python2.6 -c "import matplotlib as m ; m.test(verbosity=1)"
>
> and in . there's a matplotlibrc file with simply:
>
> datapath : /tmp/buildd/matplotlib-1.1.1~rc1/lib/matplotlib/mpl-data/
>
> in it; but still I got all of these failures. Anyone knows where I can
> look to fix that?
>
> Thanks in advance,
Cheers,
Mike

Hello,
I've been trying to fix this problem for hours, and it's getting me
mad but to no conclusion, so I'm asking here.
In Debian we build our packges in a chroot, with all the minimum
dependecies needed to build the package (to guarantee reproducibility
and avoid weird effect of local installed packages), and so also the
unittests are runt here. While enabling the matplotlib unittest in
that chroot, I'm getting this error:
======================================================================
ERROR: matplotlib.tests.test_axes.test_arc_ellipse.test
----------------------------------------------------------------------
Traceback (most recent call last):
 File "/usr/lib/python2.6/dist-packages/nose/case.py", line 197, in runTest
 self.test(*self.arg)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
line 36, in failer
 result = f(*args, **kwargs)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/testing/decorators.py",
line 128, in do_test
 figure.savefig(actual_fname)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/figure.py",
line 1185, in savefig
 self.canvas.print_figure(*args, **kwargs)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backend_bases.py",
line 2021, in print_figure
 **kwargs)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backend_bases.py",
line 1789, in print_pdf
 return pdf.print_pdf(*args, **kwargs)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backends/backend_pdf.py",
line 2180, in print_pdf
 file = PdfFile(filename)
 File "/tmp/buildd/matplotlib-1.1.1~rc1/build/lib.linux-x86_64-2.6/matplotlib/backends/backend_pdf.py",
line 378, in __init__
 rcParams['datapath'], 'fonts', 'pdfcorefonts')
 File "/usr/lib/python2.6/posixpath.py", line 67, in join
 elif path == '' or path.endswith('/'):
AttributeError: 'NoneType' object has no attribute 'endswith'
(repeated for several times, it seems like a patter, given the output
of the test execution is:
..K.............EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK.EK..EK.EK.EK.EK.EK.EK.EKK...EK...EK.EK..EKEK..EK.EK.EK.EK.EK..EK.EK.EK[....]
and so on) so it seems the code can't find the datapath location. In
order to fix that, I'm calling the test suite like this:
PYTHONPATH=build/lib.linux-x86_64-2.6 \
 MATPLOTLIBDATA=/tmp/buildd/matplotlib-1.1.1~rc1/lib/matplotlib/mpl-data/
\
 MPLCONFIGDIR=. \
 python2.6 -c "import matplotlib as m ; m.test(verbosity=1)"
and in . there's a matplotlibrc file with simply:
 datapath : /tmp/buildd/matplotlib-1.1.1~rc1/lib/matplotlib/mpl-data/
in it; but still I got all of these failures. Anyone knows where I can
look to fix that?
Thanks in advance,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On 05/14/2012 12:58 PM, Christoph Gohlke wrote:
>
> On 5/14/2012 7:43 AM, Michael Droettboom wrote:
>> On 05/12/2012 01:33 PM, Christoph Gohlke wrote:
>>>
>>> On 5/12/2012 6:16 AM, Michael Droettboom wrote:
>>>> On 05/12/2012 07:21 AM, Mark Lawrence wrote:
>>>>> My original offer (made several months ago) to help test this on
>>>>> Windows
>>>>> still stands :)
>>>>>
>>>> Thanks. Does git master build and pass the unit tests on Windows?
>>>>
>>>> Mike
>>>>
>>> git master builds and tests OK on win32-py2.7.
>>>
>>> With the attached patch git master builds and works (in practice) OK
>>> on win-amd64-py3.2 but there are many test errors of type
>>> "RuntimeError: Could not open facefile X:\Python32\...\ttf\Vera.ttf;
>>> Cannot_Open_Resource". I do delete the ~\.matplotlib folder before
>>> running the tests and can verify that
>>> FT2Font(r"X:\Python32\lib\site-packages\matplotlib\mpl-data\fonts\ttf\Vera.ttf")
>>> works.
>> That looks like the same issue we were having on the 1.1.x branch --
>> that it's running out of file handles -- that I thought was fixed by
>> this PR:
>>
>> https://github.com/matplotlib/matplotlib/pull/798
>>
>>
>> PR798 works for Python 2.7. But under Python 3.2 the tests are still
>> running out of file handles. Manually increasing the open files limit
>> helps (only one test fails).
>>
Ah, I guess that makes sense given how destructors are handled 
differently on Python 3. I have some thoughts on this that I might put 
into a PR. I don't have access to a Windows box at the moment, so I may 
need some help testing.
Mike

On 5/14/2012 7:43 AM, Michael Droettboom wrote:
> On 05/12/2012 01:33 PM, Christoph Gohlke wrote:
>>
>>
>> On 5/12/2012 6:16 AM, Michael Droettboom wrote:
>>> On 05/12/2012 07:21 AM, Mark Lawrence wrote:
>>>>
>>>> My original offer (made several months ago) to help test this on
>>>> Windows
>>>> still stands :)
>>>>
>>> Thanks. Does git master build and pass the unit tests on Windows?
>>>
>>> Mike
>>>
>>
>> git master builds and tests OK on win32-py2.7.
>>
>> With the attached patch git master builds and works (in practice) OK
>> on win-amd64-py3.2 but there are many test errors of type
>> "RuntimeError: Could not open facefile X:\Python32\...\ttf\Vera.ttf;
>> Cannot_Open_Resource". I do delete the ~\.matplotlib folder before
>> running the tests and can verify that
>> FT2Font(r"X:\Python32\lib\site-packages\matplotlib\mpl-data\fonts\ttf\Vera.ttf")
>> works.
> That looks like the same issue we were having on the 1.1.x branch --
> that it's running out of file handles -- that I thought was fixed by
> this PR:
>
> https://github.com/matplotlib/matplotlib/pull/798
>
> Or are we seeing something else here?
>
> Mike
>
PR798 works for Python 2.7. But under Python 3.2 the tests are still 
running out of file handles. Manually increasing the open files limit 
helps (only one test fails).
Christoph