On Fri, Aug 15, 2008 at 02:59:43AM -0500, Stéfan van der Walt wrote: > 2008/8/15 Robert Kern <[EMAIL PROTECTED]>: > > The devil is in the details. What exactly do you propose? When we > > discussed this last time, the participants more or less agreed that > > environment variables could cause more fragility than they're worth. > > It also breaks the first time you try to import a numpy-using library > > that was not written with this in mind. Basically, you're stuck with > > only code that you've written.
> First, I propose that I write some code. Second, I do not suggest the > behaviour above, but: > 1) Expose a new interface to numpy, called numpy.api > 2) If a certain environment variable is set, the numpy namespace is > not populated, and numpy.api becomes instantaneous to load. That doesn't work because of a "feature" in Python's import: when loading foo.bar, Python loads foo.__init__ first. This is why we have "api" modules all over ETS. Gaël _______________________________________________ Numpy-discussion mailing list [email protected] http://projects.scipy.org/mailman/listinfo/numpy-discussion
