Stefan Behnel wrote: > Dag Sverre Seljebotn wrote: >> 2) Code and patch workflow. >> >> On the (A) side, the status with f2py is that the author started a full >> rewrite (f2py 3G) which hasn't seen work for half a year >> (http://f2py.org/). So anything can happen here and we have to get back >> to how it's going to be done and where it should live. > > Sounds like the right thing to ask the author first.
This is the current consensus between us and Pearu: He considers f2py G3 still in development, he just doesn't have time for it at the time. And he's noticed interest in the parser component, "fparser", from other parties as well, and has seperated it out in a seperate module. Myself and Kurt will get access to f2py G3's Launchpad project and use f2py's repo, tracker and mailing list for any work that is strictly related to fparser, in cooperation with Pearu. It seems then that the fparser -> Cython part of it will live in the Cython project and use Cython's tracker etc. (The reason I don't think it is premature to deal with this now is that I consider it important that discussions happen in the right places, and the coming month is the one that's going to be most discussion-intensive.) -- Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
