On Thu, Jun 26, 2014 at 02:33:09PM +0100, Ian Ozsvald wrote: > Oops, sorry to be slow, I had to submit the manuscript for my book > (now off for editing - yay!). Congrats \o/ > I can't share the material for that course, that's a private course > I'm now running. In this case I used the Julia set example (which I > built through all the various tools, from Cython through to Numba, > both lists & numpy), we just built it and ran the demo and a few of > the students wanted to try pythran on their own code. ok, > When it comes to interfacing with numpy functions - do you plan to > have a fall-back mode that uses a default numpy function *outside* of > pythran, so that all the numpy functions are 'always available' even > if pythran doesn't provide an optimized version? I suspect you'll say > that you've got your own GC and so this isn't possible, since I'm not > very familiar with pythran's internals I might be asking a silly > question. There is no fall-back mode, although it would be possible (we are using a reference counting GC compatible with CPython's one). At least the compiler should warn you that the given function is NIY :-)