[Numpy-discussion] f2py - a recap
Thu Jul 24 02:31:50 CDT 2008
Few months ago I joined a group of system biologist and I have
been busy with new projects (mostly C++ based). So I haven't
had a chance to work on f2py.
However, I am still around to fix f2py bugs and maintain/support
numpy.f2py (as long as current numpy maintainers allow it..)
-- as a rule these tasks do not take much of my time.
I have also rewritten f2py users guide
for numpy.f2py and submitted a paper on f2py. I'll make them
available when I get some more time..
On Thu, July 24, 2008 1:46 am, Fernando Perez wrote:
> On Wed, Jul 23, 2008 at 3:18 PM, Stéfan van der Walt <email@example.com>
>> 2008/7/23 Fernando Perez <firstname.lastname@example.org>:
>> I agree (with your previous e-mail) that it would be good to have some
>> documentation, so if you could give me some pointers on *what* to
>> document (I haven't used f2py much), then I'll try my best to get
>> around to it.
> Well, I think my 'recap' message earlier in this thread points to a
> few issues that can probably be addressed quickly (the 'instead' error
> in the help, the doc/docs dichotomy needs to be cleaned up so a single
> documentation directory exists, etc). I'm also attaching a set of
> very old notes I wrote years ago on f2py that you are free to use in
> any way you see fit. I gave them a 2-minute rst treatment but didn't
> edit them at all, so they may be somewhat outdated (I originally wrote
> them in 2002 I think).
> If Pearu has moved to greener pastures, f2py could certainly use an
> adoptive parent. It happens to be a really important piece of
> infrastructure and for the most part it works fairly well. I think
> a litlte bit of cleanup/doc integration with the rest of numpy is
> probably all that's needed, so it could be a good project for someone
> to adopt that would potentially be low-demand yet quite useful.
> Numpy-discussion mailing list
More information about the Numpy-discussion