On Thu, May 2, 2013 at 5:04 PM, Steve <[email protected]> wrote:
> So, any more thoughts on this issue? > > > On Friday, April 26, 2013 11:28:08 AM UTC-5, Carlos Córdoba wrote: > >> Please use hg bisect to detect the exact revision that introduced the >> problem for you between beta2 and beta3. I have a guess for what could >> be happeing in your case but first I would like to know your bisect >> output. >> >> Cheers, >> Carlos >> >> El 25/04/13 10:58, Steve escribió: >> > I've been having issues with the ipython console not working. I have >> > ipython 0.13.1. I'd been running the current spyder version. While >> > looking into a pylint related issue I was rolling back in time. If I >> > use v2.2.0beta2 the ipython console suddenly starts working. If I >> > move up to v2.2.0beta3 or newer the ipython console does not work. Is >> > there any output that would be helpful for diagnosing this issue? >> > -- https://groups.google.com/groups/opt_out. >> > > Hi, Steve. Could you use hg bisect [1] to figure out precisely which commit between beta2 and beta3 causes the problem? There are 80+ commits between the two tags, and many of them are related to IPython console. It would be very helpful to know which of those to target. [1] http://www.selenic.com/mercurial/hg.1.html#bisect -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
