On 7/26/07, Darren Dale <[EMAIL PROTECTED]> wrote: > On Thursday 26 July 2007 10:30:34 am Ted Drain wrote: > > Darren, > > Well it wasn't one of your questions but... > > > > Why do you need an api file at all? Why not have config be a python > > package and let config/__init__.py take care of importing > > everything? The __init__ file of a package is responsible for > > configuring the api of a package so it seems redundent to have > > another filed named api. > > Good suggestion. I was emulating the way traits and IPython1 are doing it, but > probably __init__ is better and cleaner.
I don't remember the exact details, but we started using the api.py approach instead of __init__ on Enthought's lead (I think to be more friendly to setuptools, perhaps it had something to do with namespace packages). There were discussions a while ago on the Enthought lists about the reasons why they were moving away from __init__. While it kind of bothered me a bit in the beginning out of an "If it ain't broke, don't fix it" view, I realized that they seemed to have thought it through. You may want to inquire with them for the details (I was only paying marginal attention and relied on trusting that they *did* think it through) and then decide whether the reasons do/will/may apply to MPL as well. But it didn't happen by accident, it was a deliberate choice. Cheers, f ------------------------------------------------------------------------- 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
