In a for loop on xonsh's REPL, how can I detect that Ctrl-C was issued?

[halloleo]

Sometimes I have to write in the xonsh REPL a for-loop of long running commands . For example:

For d in data_set_list:
   work_on_dataset @(d)

When I press Ctrl-c during the long running command work_on_dataset @(d) ,this command aborts as expected, but xonsh continues with the next iteration of d. How can I check after returning from work_on_dataset @(d) whether the command was aborted or not (in order to abort the loop then).

MWE

Here an minimal working example everybody can try:

for i in range(5):
    print(i)
    sleep 10

When I Ctrl-c out of the sleep, xonsh continues with the next iteration.

What I've tried

• I tried using rtn = !(sleep 5), but then I cannot abort anymore at all!

• Then I experimented with rtn = $(sleep 5) and this aborts, but rtn is always the same afterwards, so I cannot use it to determine whether sleep 5 was aborted.

[anki-code]

Hey! I know this case and I agree it's really annoying.
I'm working on things around processes now and I traced this behavior. Here is the code:

xonsh/xonsh/jobs.py

Lines 269 to 288 in 26c6e11

	try:
	_, wcode = os.waitpid(obj.pid, os.WUNTRACED)
	except ChildProcessError as e: # No child processes
	if return_error:
	return e
	else:
	return _safe_wait_for_active_job(
	last_task=active_task, backgrounded=backgrounded
	)
	if os.WIFSTOPPED(wcode):
	active_task["status"] = "stopped"
	backgrounded = True
	elif os.WIFSIGNALED(wcode):
	print() # get a newline because ^C will have been printed
	obj.signal = (os.WTERMSIG(wcode), os.WCOREDUMP(wcode))
	obj.returncode = None
	else:
	obj.returncode = os.WEXITSTATUS(wcode)
	obj.signal = None
	return wait_for_active_job(last_task=active_task, backgrounded=backgrounded)

When you run sleep 10 the system process go to wait and we stuck on os.waitpid. After pressing Ctrl+C (sending SIGINT) process get the SIGINT signal and we catch that signal appeared using WIFSIGNALED (line 281) but have no actions about stopping the execution entirely and we continue execution.
It would be cool to considering the cases around this (i.e. can we really stop the execution of the whole code?) and stopping the execution carefully here. A bunch of helpful tools is here. PR is welcome!

[anki-code]

Fixed in #5380. Set $RAISE_SUBPROC_ERROR = True before loop.