On 2/10/07, Tim Leslie <[EMAIL PROTECTED]> wrote:

> And for what it's worth this is also the direction nipy is taking,
> having an api.py in each package.

I don't have a problem with this if it makes sense to other people and
helps with consistency across packages, but I don't find the mnemonic
particularly clear.  Eg

  from matplotlib.config import rc, verbose

makes more sense to me than

  from matplotlib.api import rc, verbose

since I consider these (and most other stuff in  __init__) to be part
of the configuration, and a lot of stuff that doesn't live there
(Figure, Axes, Line2D) to be part of the API.  What is the
enthought/nipy rationale for calling it api?

JDH

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to