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
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
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,
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
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
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
