Re: [Numpy-discussion] Controlling the way a module is imported

2008-05-25 Thread David Cournapeau
Robert Kern wrote: > > Can you be more specific? Sure: in my branch to refactor fftpack, every non default backend (that is everything but fftpack) is a separate python module, which implements some fft functions, and is 'importable'. So in scipy.fftpack, I have a function which: - tries t

Re: [Numpy-discussion] Controlling the way a module is imported

2008-05-25 Thread Robert Kern
On Sun, May 25, 2008 at 4:28 AM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Hi, > >This is not numpy specific, but I need it for numpy/scipy. More > specifically, I would like to be able to have one module interface which > load imp1, imp2, imp3, etc... depending on some options. Can you be

[Numpy-discussion] Controlling the way a module is imported

2008-05-25 Thread David Cournapeau
Hi, This is not numpy specific, but I need it for numpy/scipy. More specifically, I would like to be able to have one module interface which load imp1, imp2, imp3, etc... depending on some options. I see two obvious solutions: monkey patching, and file configuration, but I try to avoid