On Feb 8, 2013 11:14 PM, "Benjamin Root" wrote:
>
> Just a crazy thought, but why are we trying to treat "title" and such as
properties? When I think of properties for matplotlib, I think of
edgecolors, fontsize, and linestyles. Why don't we solve that problem
first?
In my mind there are severa
Yes, I realize that this (or the += approach) was overdoing it. Separating
the stuff in two different properties is probably more the way to go (at
least, it's less crazy).
Even the ax.title += (string, options) approach has the problem that this
would imply ax.title (in the sense of ax.__dict__[
Just a crazy thought, but why are we trying to treat "title" and such as
properties? When I think of properties for matplotlib, I think of
edgecolors, fontsize, and linestyles. Why don't we solve that problem
first?
Cheers!
Ben Root
---
On Fri, Feb 8, 2013 at 2:40 AM, Antony Lee wrote:
> Hi,
>
> I saw that a discussion started on transitioning to the use of properties
> instead of explicit getters and setters, which seems like a very good idea
> to me... so I thought this would be a good idea to get involved in
> matplotlib-deve
On Fri, Feb 8, 2013 at 3:38 AM, Jason Grout wrote:
> On 2/7/13 8:08 PM, Erik Bray wrote:
> > A couple easier solutions: Allow
> > the `.title` (and other such attributes) to be assigned to with a
> > (value, options) tuple where the value is the title itself, and the
> > options is a dictionary or
On Fri, Feb 8, 2013 at 10:04 AM, Antony Lee wrote:
> 2013/2/7 Erik Bray
>
>> On Thu, Feb 7, 2013 at 8:40 PM, Antony Lee
>> wrote:
>> > Hi,
>> >
>> > I saw that a discussion started on transitioning to the use of
>> properties
>> > instead of explicit getters and setters, which seems like a very
Indeed, good catch. But another issue comes to my mind: should ax1.title
(that is, "ax1..title.__get__(ax1)" where ".." means no descriptor invoked)
return a string (like now) or something that contains all the properties of
the title? Returning a string copies the current behavior of get_title,
On 2/7/13 8:08 PM, Erik Bray wrote:
> A couple easier solutions: Allow
> the `.title` (and other such attributes) to be assigned to with a
> (value, options) tuple where the value is the title itself, and the
> options is a dictionary or tuple of supported options for the title.
Interesting. Just
On Thu, Feb 7, 2013 at 8:40 PM, Antony Lee wrote:
> Hi,
>
> I saw that a discussion started on transitioning to the use of properties
> instead of explicit getters and setters, which seems like a very good idea
> to me... so I thought this would be a good idea to get involved in
> matplotlib-devel
Hi,
I saw that a discussion started on transitioning to the use of properties
instead of explicit getters and setters, which seems like a very good idea
to me... so I thought this would be a good idea to get involved in
matplotlib-devel :)
Right now an issue raised is what to do with set_* that t
10 matches
Mail list logo
