[Numpy-discussion] How to test f2py?
Tue Feb 23 22:19:32 CST 2010
On Tue, Feb 23, 2010 at 22:12, Charles R Harris
> On Tue, Feb 23, 2010 at 8:54 PM, Robert Kern <email@example.com> wrote:
>> On Tue, Feb 23, 2010 at 21:51, Charles R Harris
>> <firstname.lastname@example.org> wrote:
>> > On Tue, Feb 23, 2010 at 8:31 PM, Robert Kern <email@example.com>
>> > wrote:
>> >> On Tue, Feb 23, 2010 at 21:14, Charles R Harris
>> >> <firstname.lastname@example.org> wrote:
>> >> > Hi All,
>> >> >
>> >> > I've made PyCObject -> PyCapsule changes to f2py for python3.1. How
>> >> > can
>> >> > I
>> >> > check that f2py still works as advertised before making a commit?
>> >> numpy/f2py/tests/run_all.py
>> > It's not py3k compatible...
>> So make it py3k compatible.
> It's autoconverted in build/py3k. It is, however, not installed anywhere.
>> > also it doesn't find the f2py2e module even
>> > though it has been installed with numpy. ?
>> I don't understand this. Error message?
> Running /usr/bin/python
> 10 --quiet
> Traceback (most recent call last):
> line 10, in <module>
> import f2py2e
> ImportError: No module named f2py2e
> TEST FAILURE (status=1)
> So the import is wrong. The question is: did this used to work?
>From the independent f2py2e days, yes. Just change those import lines
to "from numpy import f2py as f2py2e".
"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
-- Umberto Eco
More information about the NumPy-Discussion