I’ve noticed that sometimes lately the python interactor will stop processing new commands. This is something new in the past few weeks. It seems to happen when there’s a background exception. @lassoan the other day on the developer hangout it sounded like you’d seen this before too, but we didn’t have time to talk. Do you know why it’s happening?
I don’t remember ever experiencing this.
I confirm I experienced similar problem. I will report an issue with exact step.
Thanks @jcfr - I’ve had it happen a couple times. In case it helps, today I was able to track it down to an exception being thrown in an imported library. Nothing showed up on the Slicer console, but when I ran the same code in an external python process the exception showed up.