3 ms·
> calling back and forth between C and Python Yes - the trick really is to move your accelerated code away from python's object model, because then you can dro
by ris 7y ago
> calling back and forth between C and Python
Yes - the trick really is to move your accelerated code away from python's object model, because then you can drop a lot of overhead and also release the GIL. Tricky, though. Out of interest, did you see any improvement from pypy or numba?
> prohibitively unmaintainable
I don't think well written cython should be any more unmaintainable than Go IMHO.
- throwaway894345 7y agoWe didn't try numba and couldn't get pypy working; we had dependencies that didn't work with Pypy. I'm curious about numba though. > I don't think well written cython should be any more unmaintainable than Go IMHO. I've written a lot of Go, it's always struck me as about as maintainable as Python (I would put it at a bit more maintainable than Python given its mature static typing story--mypy still has lots of problems). I haven't given Cython a fair shake, but it doesn't seem very well-invested in; this is generally what has kept me away from it.