Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)
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 -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)
On 05/12/2012 05:56 AM, Sandro Tosi wrote: > Hello, > as you may be aware of, in 1 month (more or less) Debian will freeze, > that means that no new upstream releases will be allowed in the > upcoming release, only fixex for important bugs. > > Currently in Debian archive we have 1.1.1rc1 . Recent mails have > mentioned that the next release will be py3k enabled. Well, what are > you're plans to release such version? :) I don't think we have a timeframe on that yet. Getting out a solid, stable 1.1.1 (without Py3k support) I think is a higher priority right now. > > It would be really awesome to have a python3 matplotlib in Debian, and > i'd be happy to test any new RC you'd like to release. > To get this going, perhaps I'll go ahead and make a branch off of master for 1.2.x and we could start testing it on all the platforms and see how far it feels from releasable state. There are few PRs in the queue that are simple yet critical that should get in there first. 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)
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 -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Plans for matplotlib py3k/final release (and impact on Debian)
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 -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
