[SciPy-Dev] Multivariate Ctypes PR

[Ralf Gommers]

Hi Nathan, Brian,


On Tue, May 27, 2014 at 10:15 PM, Gmail <charlesnwoods at gmail.com> wrote:

> Hey guys,
>
> We’re unfortunately fast running out of time with this, since Brian’s soon
> moving on to bigger and better things, at least temporarily. I understand
> that this is a less-tidy bit of code that we’d all like, but interfacing
> with ancient Fortran code isn’t really a tidy application anyway. Is there
> any way we can get this reviewed and at least provisionally evaluated in
> the next week or so?
>

Thanks for being persistent. I did some testing, sent you a fix and
provided some feedback on the PR.

Cheers,
Ralf


>
> Nathan
>
> On May 14, 2014, at 5:10 PM, Brian Lee Newsom <Brian.Newsom at Colorado.EDU>
> wrote:
>
> Hello all,
>
> In regards to the multivariate ctypes PR (
> https://github.com/scipy/scipy/pull/3262), Nathan and I have addressed
> all the issues presented earlier regarding this code.  Tests have been
> added and integrated into the build system and are working and passing.
>
> As for merging the code paths between Python and Ctypes, my opinion is
> that this is a route where little progress can be made.  I have removed the
> need for an extra stack storage struct (ZStorage) and am now using the one
> previously used for python (QStorage). Other than that, the initialization,
> call, and restore all require different enough behaviors for the Python vs.
> the C that I do not believe it is feasible to merge them.  If anyone else
> has a different opinion I'd love to hear your thoughts.
>
> Ideally a route that could be explored soon would be compiling the Python
> into C with code generation and handling that automatically, and in this
> way the complexities could be removed.  However with CTypes this
> possibility seems extremely challenging or impossible, and Nathan and I
> believe that this should be held off until Cython can be supported.
>
> At it's present state, this feature is usable, tested, and documented.
>  Let me know if anything else can be done to hasten it's inclusion.
>
> Thanks,
> Brian
>  _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20140528/21896c07/attachment.html>