Hi,

As my GSoC winds up, we need to decide whether we'll package the
fortran parser, 'fparser' (located as a subpackage of the G3 F2PY
project http://code.google.com/p/f2py/) with Cython, or if it will
remain an external dependency.

Dag Sverre and I had a short email thread with Pearu Peterson about
this, and inclusion was left as a possibility.  I want to check here
and see if inclusion would be rejected straight away, before pursuing
the matter further with Pearu.

First, I believe there to be no licensing issues, although I'm not
100% certain here -- Cython is under the Apache license, right?  And
G3 F2PY is under the Numpy-license.  If these are incompatible then
that takes care of the issue.

Otherwise --

In favor of including fparser:

 * Ease of use, one fewer barrier to entry.
 * Dag and I both have commit access to fparser; we (principally me)
can fix bugs in the Cython branch of fparser.
 * fparser is a self-contained package, but its ultimate design is a
part of another package (G3 F2PY) that is developing.  Since users
would have to deal with the G3 F2PY level for download, etc, and G3
F2PY is unfinished but for fparser, this would be confusing.  It would
be great to hide these details completely.

Against including fparser:

 * Maintenance & support -- responsibility for upkeep falls more on
Cython's shoulders (via yours truly).
 * Bloat.  It includes a large package in Cython not central to
Cython's core philosophy.

I'm neutral in this.  If the devs decide against inclusion, then I'd
strongly consider implementing a smaller fortran parser (focused just
on the bits we need for fwrap) that *would* be included.

Thanks,

Kurt
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to