Am 21.03.2012 20:49, schrieb Richard Stanton:
> Even stranger, on my Windows machine, running the function py-separator-
> char inside edebug gives me the following output:
>
> "\\Traceback (most recent call last): File \"<string>\", line 1, in
> <module>SystemExitIf you suspect this is an IPython bug, please report
> it at: https://github.com/ipython/ipython/issuesor send an email to
> the mailing list at <email address hidden> can print a more detailed
> traceback right now with \"%tb\", or use \"%debug\"to interactively
> debug it.Extra-detailed tracebacks for bug-reporting purposes can be
> enabled via: %config Application.verbose_crash=True>>> "
>
Strange.
What does M-x describe-function py-separator-char RET tell?
May jump to the code then and send its definition?
Am 21.03.2012 20:49, schrieb Richard Stanton: SystemExitIf you suspect this is an IPython bug, please report /github. com/ipython/ ipython/ issuesor send an email to verbose_ crash=True> >> "
> Even stranger, on my Windows machine, running the function py-separator-
> char inside edebug gives me the following output:
>
> "\\Traceback (most recent call last): File \"<string>\", line 1, in
> <module>
> it at: https:/
> the mailing list at <email address hidden> can print a more detailed
> traceback right now with \"%tb\", or use \"%debug\"to interactively
> debug it.Extra-detailed tracebacks for bug-reporting purposes can be
> enabled via: %config Application.
>
Strange.
What does M-x describe-function py-separator-char RET tell?
May jump to the code then and send its definition?