[SciPy-User] Arpack changes from 0.7.2 to 0.8.0
Tue Aug 10 23:56:02 CDT 2010
On Wed, Aug 11, 2010 at 12:05 AM, Lutz Maibaum <firstname.lastname@example.org> wrote:
> On Tue, Aug 10, 2010 at 5:26 PM, <email@example.com> wrote:
>> I think there is a problem that the function is shadowing the module.
>> I remember I had problems with this before. I don't remember whether
>> there was a work around.
> Thanks, that's what I thought. Was this done on purpose? It seems like
> this is an API change that breaks backwards compatibility (that's how
> I stumbled upon it). It would be nice if there was a warning in the
> release notes, and/or in the scipy.sparse.linalg documentation.
reading the thread again from jan 11
[Numpy-discussion] TypeError: 'module' object is not callable
I'm still not clear what was going on.
The import into the sparse.linalg namespace was missing only for 2
months, after ARPACK had been temporarily removed, between r:5154 and
r:5527, which it looks like was just when 0.7.0 was branched.
I think I added the import in 5527 just to restore the previous state.
I don't think this was an intended change in behavior.
> SciPy-User mailing list
More information about the SciPy-User