On Wed, Mar 18, 2009 at 12:32 PM, Stefan Behnel <[email protected]> wrote: > > Thanks for looking into this. Without actually knowing the details, I'm not > sure yet that this is a good way to do it. I do not have high confidence in > the current handling of the return_type, so setting it globally in a class > might cover incorrect assumptions in other parts of the code that just > expect that the return_type is set at some point in the pipeline where it > normally wouldn't be set (i.e. long before code generation). I ran into > tons of problems like these since I started working on ticket 144. It's > actually possible that this will be fixed when I'm done with that ticket. > > BTW, I'm working in cython-unstable with these things.
Good points -- thanks for the feedback. I've still got lots to learn about Cython ;-) Kurt _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
