[SciPy-Dev] Using Pythran to compile some of the scipy internals

serge guelton serge.guelton at telecom-bretagne.eu
Wed Jan 31 06:42:23 EST 2018


On Mon, Jan 29, 2018 at 12:34:02PM +0100, serge guelton wrote:
> On Mon, Jan 22, 2018 at 03:28:40PM +0100, Serge Guelton wrote:
> > > Another potential benefit is to decrease the size of the binary distribution of
> > > SciPy. Cython extensions are quite expensive in this respect. Do you have an
> > > idea of how Pythran compares? Both in case of only float64 inputs, and with
> > > templated inputs? A good example of the latter is scipy.ndimage.label, which is
> > > a straightforward function that ends up being a 700kb .so
> > 
> > Thanks for pointing out this aspect. There's still room for improvement
> > here, but with current pythran's master, and same compilation flags, the
> > cython implementation of `max_len_seq_inner` takes ~700kb while
> > pythran's version takes ~200kb.
> > 
> > I'm going to investigate that a bet more though, and probably post the
> > results in this thread later on.
> 
> Hey scip-dev, finally the result of some dev + thoughts on
> Pythran-generated code:
> 
>     http://serge-sans-paille.github.io/pythran-stories/shrinking-pythran-generated-binaries.html
> 
> I'll move on to Windows support now :-)

Just to make sure: which toolchain is used to build scipy on windows:
mingw or msvc? What's the default build environment? WinPython or the
official Python binaries from Python.org?


More information about the SciPy-Dev mailing list