You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point the user is dumped back to the shell but the shell is not in a good state (hatch's child process python is in fact still running.)
Compare with just this, which could be the desired behaviour:
python
<Ctrl-C>
>>>
KeyboardInterrupt
>>>
(python also still running here, but it keeps control of the terminal)
In short: "hatch run" is not transparent because python inside hatch run does not behave the same way that plain python does. Letting the child process handle Ctrl-c as it wants to do will help multiple applications (another example: jupyterlab will ask the user to quit or not, with an interactive prompt, if you use Ctrl-c, and ipykernel will interrupt current computation but not quit, if you sent SIGINT.).
Hatch, version 1.12.0
platform: linux (x86_64)
The text was updated successfully, but these errors were encountered:
bluss
changed the title
hatch run handles keyboard interrupt
hatch run handles keyboard interrupt (but maybe should defer to child)
Jul 28, 2024
Inside a hatch project, try this:
The result is:
At this point the user is dumped back to the shell but the shell is not in a good state (hatch's child process python is in fact still running.)
Compare with just this, which could be the desired behaviour:
(python also still running here, but it keeps control of the terminal)
In short: "hatch run" is not transparent because python inside hatch run does not behave the same way that plain python does. Letting the child process handle Ctrl-c as it wants to do will help multiple applications (another example: jupyterlab will ask the user to quit or not, with an interactive prompt, if you use Ctrl-c, and ipykernel will interrupt current computation but not quit, if you sent SIGINT.).
Hatch, version 1.12.0
platform: linux (x86_64)
The text was updated successfully, but these errors were encountered: