Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Todd
On Wed, Jan 16, 2013 at 2:52 PM, Michael Droettboom wrote: > This seems like a good candidate for a MEP. We'd want to take a > graceful approach to transitioning to properties. > > See here for information about MEPs: > > https://github.com/matplotlib/matplotlib/wiki > > Mike > > > > I have cre

[matplotlib-devel] MEP13 - python containers

2013-01-16 Thread Todd
I have created a very preliminary MEP for the possible move to properties: https://github.com/matplotlib/matplotlib/wiki/MEP13 Please take a look at it and discuss. As I said, this is very preliminary. Everything is subject to change.

Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Joe Kington
On Jan 16, 2013 2:05 PM, "Todd" wrote: > > On Wed, Jan 16, 2013 at 2:55 PM, Benjamin Root wrote: >> >> >> On Wed, Jan 16, 2013 at 2:42 PM, Todd wrote: >>> >>> Currently matplotlib uses set_ and get_ functions for reading and writing values. However, since 2.6 python supports properties, which a

Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Benjamin Root
On Wed, Jan 16, 2013 at 3:05 PM, Todd wrote: > On Wed, Jan 16, 2013 at 2:55 PM, Benjamin Root wrote: > >> >> On Wed, Jan 16, 2013 at 2:42 PM, Todd wrote: >> >>> Currently matplotlib uses set_ and get_ functions for reading and >>> writing values. However, since 2.6 python supports properties,

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Damon McDougall
On Wed, Jan 16, 2013 at 10:54 AM, Todd wrote: > On Jan 16, 2013 9:30 AM, "Fernando Perez" wrote: >> >> On Wed, Jan 16, 2013 at 12:10 AM, Nelle Varoquaux >> wrote: >> >> > Last but not least, maybe we can see what numfocus has to offer. >> >> Absolutely! I'll be offline for two weeks, but others

Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Todd
On Wed, Jan 16, 2013 at 2:55 PM, Benjamin Root wrote: > > On Wed, Jan 16, 2013 at 2:42 PM, Todd wrote: > >> Currently matplotlib uses set_ and get_ functions for reading and writing >> values. However, since 2.6 python supports properties, which allow access >> to such values as attributes in a

Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Benjamin Root
On Wed, Jan 16, 2013 at 2:42 PM, Todd wrote: > Currently matplotlib uses set_ and get_ functions for reading and writing > values. However, since 2.6 python supports properties, which allow access > to such values as attributes in addition to using the functions directly. > Would it be worthwhil

Re: [matplotlib-devel] Matplotlib property support

2013-01-16 Thread Michael Droettboom
This seems like a good candidate for a MEP. We'd want to take a graceful approach to transitioning to properties. See here for information about MEPs: https://github.com/matplotlib/matplotlib/wiki Mike On 01/16/2013 02:42 PM, Todd wrote: Currently matplotlib uses set_ and get_ functions for

[matplotlib-devel] Matplotlib property support

2013-01-16 Thread Todd
Currently matplotlib uses set_ and get_ functions for reading and writing values. However, since 2.6 python supports properties, which allow access to such values as attributes in addition to using the functions directly. Would it be worthwhile implementing property support in matplotlib?

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Paulo César Pereira de Andrade
2013/1/16 Michael Droettboom : [...] >> $ ls /usr/lib64/python2.7/site-packages/matplotlib/mpl-data/fonts/ttf/ >> LICENSE_STIX STIXNonUniBol.ttf STIXSizOneSymBol.ttf >> STIXGeneralBolIta.ttf STIXNonUniIta.ttf STIXSizOneSymReg.ttf >> STIXGeneralBol.ttf STIXNonUni.ttf

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Michael Droettboom
On 01/16/2013 01:32 PM, Paulo César Pereira de Andrade wrote: > 2013/1/16 Michael Droettboom : > >> There was a very silly bug lurking in USE_FONTCONFIG=True mode, and I've >> made a PR with a fix here: >> >> https://github.com/matplotlib/matplotlib/pull/1666 >Updated test case with that patch:

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Paulo César Pereira de Andrade
2013/1/16 Michael Droettboom : > There was a very silly bug lurking in USE_FONTCONFIG=True mode, and I've > made a PR with a fix here: > > https://github.com/matplotlib/matplotlib/pull/1666 Updated test case with that patch: http://pcpa.fedorapeople.org/matplotlib-2.7+pull-1666.txt > However,

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Michael Droettboom
On 01/16/2013 12:22 PM, Paulo César Pereira de Andrade wrote: 2013/1/16 Michael Droettboom : -USE_FONTCONFIG = False +USE_FONTCONFIG = True [...] I think this is safe to be made a patch for Linux distros. I believe this could be the default for *Linux and *BSD in matplotlib. This will silen

[matplotlib-devel] Upcoming release schedule thoughts

2013-01-16 Thread Michael Droettboom
There have been bits and pieces of discussion about future releases on PRs, and I thought I'd bring it over here to tie loose ends together. There have been 83 commits since 1.2.0 -- it's probably time to start thinking about a 1.2.1. The release candidate cycle shouldn't be as long for this,

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Paulo César Pereira de Andrade
2013/1/16 Michael Droettboom : >> -USE_FONTCONFIG = False >> +USE_FONTCONFIG = True [...] >> I think this is safe to be made a patch for Linux distros. I believe this >> could >> be the default for *Linux and *BSD in matplotlib. >> > This will silence things, and I agree it probably should be the

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Todd
On Jan 16, 2013 9:30 AM, "Fernando Perez" wrote: > > On Wed, Jan 16, 2013 at 12:10 AM, Nelle Varoquaux > wrote: > > > Last but not least, maybe we can see what numfocus has to offer. > > Absolutely! I'll be offline for two weeks, but others on the list can > certainly propose this to numfocus on

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Michael Droettboom
On 01/16/2013 10:38 AM, Paulo César Pereira de Andrade wrote: > 2012/12/8 Paulo César Pereira de Andrade > : >>Hi, >> >>Recently I asked to become comaintainer of matplotlib in Fedora and >> did update to 1.2.0 > [...] > >> doctest:1214: UserWarning: findfont: Font family ['STIXGenera

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Ryan May
On Tue, Jan 15, 2013 at 6:20 PM, Damon McDougall wrote: > Hi all, > > Recently, it has become more and more common that the travis builds > fail. They fail not because the test suite fails but because of some > inherent issues with travis itself. Usually, either the git clone > fails or some oth

Re: [matplotlib-devel] Font issues in fedora 18 and rawhide

2013-01-16 Thread Paulo César Pereira de Andrade
2012/12/8 Paulo César Pereira de Andrade : > Hi, > > Recently I asked to become comaintainer of matplotlib in Fedora and > did update to 1.2.0 [...] > doctest:1214: UserWarning: findfont: Font family ['STIXGeneral'] > not found. Falling back to Bitstream Vera Sans [...] > I opened tw

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Michael Droettboom
On 01/16/2013 07:15 AM, Thomas Kluyver wrote: On 16 January 2013 08:35, Nathaniel Smith > wrote: When this has come up on the numfocus list before the status was, sure, they can provide resources/funding if you can find someone to do the actual work :-). If any

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Thomas Kluyver
On 16 January 2013 08:35, Nathaniel Smith wrote: > When this has come up on the numfocus list before the status was, sure, > they can provide resources/funding if you can find someone to do the actual > work :-). If anyone is interested in putting in the time to solve this > problem properly then

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Nathaniel Smith
On 16 Jan 2013 09:30, "Fernando Perez" wrote: > > On Wed, Jan 16, 2013 at 12:10 AM, Nelle Varoquaux > wrote: > > > Last but not least, maybe we can see what numfocus has to offer. > > Absolutely! I'll be offline for two weeks, but others on the list can > certainly propose this to numfocus on th

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Fernando Perez
On Wed, Jan 16, 2013 at 12:10 AM, Nelle Varoquaux wrote: > Last but not least, maybe we can see what numfocus has to offer. Absolutely! I'll be offline for two weeks, but others on the list can certainly propose this to numfocus on the list and we can look into what can be done, esp. in a way t

Re: [matplotlib-devel] Usefulness of Travis-CI

2013-01-16 Thread Nelle Varoquaux
>> Hi all, >> >> Recently, it has become more and more common that the travis builds >> fail. They fail not because the test suite fails but because of some >> inherent issues with travis itself. Usually, either the git clone >> fails or some other simple shell command fails. I consider these >>