Why does matplotlib use setters and getters instead of properties?

Question

Why does matplotlib use setters and getters instead of properties?

I think this sounds like a historical question, so I would like to introduce it as: coding a library like matplotlib if I have setters and getters, or should I stick with properties?

+4

python matplotlib

user3557216 Nov 21 '14 at 21:33

source share

No one has answered this question yet.

See similar questions:

644

Using @property against getters and setters

or similar:

1675

Why is reading strings from stdin much slower in C ++ than Python?

1646

Why is it string.join (list) instead of list.join (string)?

1062

Why does string comparison using '==' or 'is' sometimes give a different result?

1015

Save the image to an image file instead of displaying it using Matplotlib

866

How does the @property decorator work?

775

list compared to lambda + filter

644

Using @property against getters and setters

400

In Matplotlib, what does this argument mean in fig.add_subplot (111)?

62

why is conspiracy with matplotlib so slow?

0

Replacing getters and setters with properties in a subclass

Why does matplotlib use setters and getters instead of properties?

More articles: