[Cython] Slow traceback reconstruction in IPython between 0.15.1 and master
markflorisson88 at gmail.com
Thu Jan 26 20:21:03 CET 2012
On 26 January 2012 19:10, Fernando Perez <fperez.net at gmail.com> wrote:
> On Thu, Jan 26, 2012 at 10:37 AM, mark florisson
> <markflorisson88 at 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".
Apologies, it was indeed a rather vague comment. I had some issues
with pasting unicode characters a few years back that would get
incorrect codepoints in ipython but not regular python, but I'm afraid
I don't have any concrete report. As such I withdraw my comment, I
just wanted to mention that if something smells iffy it might be a
good idea to resort to regular python.
> 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.
> cython-devel mailing list
> cython-devel at python.org
More information about the cython-devel