[SciPy-Dev] 1.0 roadmap: weave

[Constantine Evans]

I can at least describe our case of porting away from weave. In order to
improve portability and stability when releasing our software, we ported
our inline C weave code to normal Python C modules. This only required, at
least in our case, separating out the C portions of our code into their own
functions and adding some short boilerplate C code for dealing with
parameters and output. There was no need to modify the already-written C
code beyond placing it into separate files. If I understand the mechanisms
behind weave correctly, this is essentially what weave.inline does
automatically. Perhaps documentation of this porting method, maybe in the
SciPy tutorial to replace the weave section, might be useful.

This of course would not work for porting code that uses weave.blitz, but
blitz involves such small expressions that porting to pure C wouldn't
necessarily seem too tricky (so long as blitz arrays aren't being used).

Regards,
Constantine


On Wed, Sep 25, 2013 at 9:18 AM, Arnd Baecker <arnd.baecker at web.de> wrote:

> Hi,
>
>  On Sat, Sep 21, 2013 at 8:54 PM, Ralf Gommers <ralf.gommers at gmail.com>
>> wrote:
>>
> [...]
>
>  weave
>> `````
>> This is the only module that was not ported to Python 3.  Effectively it's
>> deprecated (not recommended to use for new code).  In the future it
>> should be
>> removed from scipy (can be made into a separate module).
>>
>
> Let me just mention that I am worried about the removal of weave:
> a substantial amount of code developed in our group over the years
> uses weave. Porting this to cython seems not trivial,
> in particular, because many of the original authors
> (diploma students, PhD students, ...) have left academia by now.
>
> Well, as porting weave to Python 3 is way out of my capabilities,
> this is just a comment in the hope that someone could give this a try
> (if at some point testing would be needed, I could try to help,
> of course).
>
> Best, Arnd
>
> _______________________________________________
> 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/20130925/97af92d6/attachment.html>