On 3/21/07, Eric Firing [EMAIL PROTECTED] wrote:
Properties would be OK for 2.3; I was thinking we might want to use
them. When a getter and setter already exist, all it takes is the one
extra line of code, plus a suitable (unused) name for the property. I
decided not to pursue traits (if
On 3/21/07, John Hunter [EMAIL PROTECTED] wrote:
On 3/21/07, Fernando Perez [EMAIL PROTECTED] wrote:
And yes, properties are actually OK even with 2.2, so there's no
reason to avoid them (and they do provide a nicer, claner user API).
Decorators are 2.4-only though.
I'm not opposed to
John Hunter wrote:
If you are using mpl svn, please read this as it describes
some fairly major changes.
Mike Lusignan has been working on adding units support, and as a
consequence, partial support for working with arbitrary types in mpl.
The support is not complete yet, but it is
On Tuesday 20 March 2007 3:50:07 am Eric Firing wrote:
John Hunter wrote:
If you are using mpl svn, please read this as it describes
some fairly major changes.
Mike Lusignan has been working on adding units support, and as a
consequence, partial support for working with arbitrary types
Actually, I like the idea of unit support quite a bit and could well
imagine that it makes sense
to support it explicitely in matplotlib.
I am using physical units very frequently in my computations. Lacking a
robust units package,
I simply define the units as numerical constants without checks
FYI The unit system John is working on will be a huge improvement for
the way we use MPL. Our users do a ton of plotting that involves
unitized numbers vs time. We have our own unit class and time class
and right now users have to convert the unitized numbers into floats
in the correct units
