Hi,
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
Howdy,
On Wed, Jul 23, 2008 at 3:18 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
> 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
On Wed, Jul 23, 2008 at 17:18, Stéfan van der Walt <[EMAIL PROTECTED]> wrote:
> 2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
>> I'm just reposting here to see if anyone with a stake in f2py has an
>> opinion/advice on the points below. F2py feels very much in
>> autopilot/drifting into the iceber
2008/7/23 Fernando Perez <[EMAIL PROTECTED]>:
> I'm just reposting here to see if anyone with a stake in f2py has an
> opinion/advice on the points below. F2py feels very much in
> autopilot/drifting into the icebergs mode right now. Is that correct
> assessment?
>
> If there's any guidance on wh
Hi all,
I'm just reposting here to see if anyone with a stake in f2py has an
opinion/advice on the points below. F2py feels very much in
autopilot/drifting into the icebergs mode right now. Is that correct
assessment?
If there's any guidance on where to go, I can at least file tickets on
these
Howdy,
today's exercise with f2py left some lessons learned, mostly thanks to
Robert's excellent help, for which I'm grateful.
I'd like to recap here what we have, mostly to decide what changes (if
any) should go into numpy to make the experience less "interesting"
for future users:
- Remove the
