On Thu, Jan 26, 2012 at 10:37 AM, mark florisson <markflorisso...@gmail.com> wrote: > On a side note, ipython is not something I usually trust to test > things out, as it gets things wrong sometimes which can seriously make > you question your own sanity.
I should note that we'd love to know specifics about problems that severe. Without a concrete report it's impossible for us to fix a problem, unfortunately, and a vague statement like this only serves to spread the notion "ipython is bad, for reasons unspecified". Also, since I know some core Cython devs are also heavy sage users, and the sage command-line is actually ipython, having an issue at the intersection of cython/ipython is problematic for all sage users working at the terminal. So we'd really like to make the cython/ipython combo as robust as possible. I certainly don't expect everyone to use ipython, and obviously when I see something that looks really bizarre, I double-check with plain Python first, as ultimately that is our reference and regressions from plain python are automatically bugs for us. But I have to say that it's been a very long time since I have encountered a situation where ipython produces something completely absurd, and if it happens to you, by all means please let us know, so we can try to fix it. Best, f _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
