Issue1270

CTRL+C in Jython 2.5b2 does not exit the console properly: the shell
behaves strangely afterwards, with NEWLINE not working anymore for example.

Well, to be fair:

  1. CTRL+D exits properly,

  2. an exit on CTRL+C (clean or not) is not the CPython behavior. 
Instead it displays 'KeyboardInterrupt' and does not exit.

This will likely be fixable on Unix by registering a SIGINT handler. Not 
sure about Windows.

This may be a function of the underlying readline support. Now that we
have JLine installed by default, on OS X at the very least it exhibits
the same behavior as CPython. No signal handling required!

boisgera, is this still a problem?

I removed my registry file so that GnuReadline does not kick in. The
registry file was:

   python.console=org.python.util.ReadlineConsole
   python.console.readlinelib=GnuReadline

That change alone did cause the beta 3 version to exit properly on a
CTRL+C. The RC3 version exhibits the same behavior (and the rev. 6450 as
well): clean exit on CTRL+C when the Readline console is not selected,
ugly exit when the registry file is present, and never the
'KeyboardInterrupt' behavior.

this is a dupe of #1746106

I just tested this with 2.5 rc 3 and could still reproduce the problem.
Is this a regression?

Ctrl-c killing the console isn't that big problem, but the fact that
ctrl-c cannot be caught as KeyboardInterrupt (issue 1313) means that I
cannot implement graceful shutdown from the CLI to my app easily. I
assume these problems have the same root cause.

Ooops, the version I used in testing was 2.5.1 RC 3 i.e. the latest
available release.

This is still outstanding; there has been no regression.

I thought this was closed as the resolution says 'fixed'.