On Wed, Jul 25, 2007 at 12:09:01PM -0500, John Hunter wrote: > As for code readability, I'll also add that as a traits newbie, I am > probably making things harder than necessary. But there are a lot of > gotchas with traits usage, particularly in the area of instantiation, > because you can easily get bitten by shared class level data > structures, especially in the presence of sync_traits.
One thing that is convenient when working with Traits, is that there already are established coding conventions. The problem when coding with metaclasses is that it is easy to prduce very beautiful code that is hard to read for the newcomer (I have fallen in that trap). Traits are nothing more but a metaclass, they also have this problem. But if they become wildy used this problem goes away. Gaƫl ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel