On 26 January 2012 18:36, mark florisson <markflorisso...@gmail.com> wrote: > On 26 January 2012 17:56, Wes McKinney <wesmck...@gmail.com> wrote: >> Just wanted to bring this issue to your guys' attention in case you >> knew what was responsible for this: >> >> https://github.com/ipython/ipython/issues/1317#issuecomment-3652550 >> >> I traced down the problem (with git bisect) to a seemingly innocuous >> commit referenced in that GitHub thread. The issue seemed to only >> present itself in IPython, so likely there was some problem with >> inspecting the Cython frames for giving context around the full >> traceback. >> >> best, >> Wes >> _______________________________________________ >> cython-devel mailing list >> cython-devel@python.org >> http://mail.python.org/mailman/listinfo/cython-devel > > So commit 0e579823bd34de5d1d9b4aeac2c8d727415cba2d fixed the problem? > I don't see how it could do that. Anyway, when I try to run the code > from the example I don't get any traceback at all. Could you perhaps > paste the exact code that produces the behaviour?
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. _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
