[Nipy-devel] attributes vs. traits

[Jonathan Taylor]

i just want to add another of my $0.02: i don't think traits are hard to 
master, and the docs have enough examples that i was up and running 
quite quickly...

my guess about the reason that there is likely no built-in way to make a 
read-only trait (i.e. that all objects are over-writeable) is that they 
are thinking of "applications" instead of "library".

-- jonathan

Matthew Brett wrote:

> Hi,
>
> To jump in, in a state of extreme ignorance...
>
>> this is where the "traitsbridge" i mentioned would come in, allowing us
>> to leverage the best part of traits without having to implement it
>> ourselves.
>
>
> This seems to me to be a very important point.  The other key point
> for me is the one you make further down, that taking the extra layer
> of traits out of the basic building blocks of the code makes the code
> much easier for someone to pick up how the code works, without having
> to master Traits - and this seems to me to be huge advantage.  If we
> can benefit from the functionality of Traits while concealing them in
> a simple way from the user, this seems the ideal solution,
>
> Luv,
>
> Matthew
> _______________________________________________
> Nipy-devel mailing list
> Nipy-devel at neuroimaging.scipy.org
> http://neuroimaging.scipy.org/mailman/listinfo/nipy-devel


-- 
------------------------------------------------------------------------
I'm part of the Team in Training: please support our efforts for the
Leukemia and Lymphoma Society!

http://www.active.com/donate/tntsvmb/tntsvmbJTaylor

GO TEAM !!!

------------------------------------------------------------------------
Jonathan Taylor                           Tel:   650.723.9230
Dept. of Statistics                       Fax:   650.725.8977
Sequoia Hall, 137                         www-stat.stanford.edu/~jtaylo
390 Serra Mall
Stanford, CA 94305