On Tue, Nov 06, 2007 at 09:00:23PM -0500, Darren Dale wrote: > I have not committed my work to svn yet. I wanted to get some feedback on > points 1 and 2 first. Is it acceptable to use traits internally, but not > expose it to the end user? I think the answer is yes, and that this is even a > benefit. If we want to make it an external dependency we can strip the > package out without impacting any user code.
I agree that by itself this is a benefit. It might also be interesting to discuss this usecase on the enthought mailing list. If you tell these guys that this is an important usecase, that projects like ipython, matplotlib, would like to use traits as an internal dependency, but would still like to be able to use the benefit of traits when interfacing with other libraries, there might be a solution. 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
