> Right, the case at hand is about a possible optimisation. I still do not > understand why this is considered worth delaying the release of 0.13. It is > not a regression at all, it has been like this for ages. Instead of just > taking the time to find a suitable solution that we can apply under the > hood, everyone is rushing to force users to change their code to deploy > flags and decorators, either one way or another. >
At least for me, I wanted this in because I know Sage developers are chomping at the bit to get this fixed. Carl originally ran into this because William discovered a huge performance degradation in Sage (the degradation wasn't Cython's fault directly), and Carl traced it back to this. If we don't get this into 0.13, they'll immediately need a patched Cython with this fix included. I agree that it's unfortunate that it was discovered so far into the (nigh-infinitely-long) release cycle ... -cc _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
