Commits on Oct 29, 2019

1. Fix KeyboardInterrupt handling logic. …

   When uvloop is run in the main thread we *always* want to set up a
   self-pipe and a signal wakeup FD.  That's the only way how libuv
   can be notified that a ^C happened and break away from selecting
   on sockets.
   
   asyncio does not need to do that, as the 'selectors' module it uses
   is already aware of the way Python implements ^C handling.
   
   This translates to a slightly different behavior between asyncio &
   uvloop:
   
   1. uvloop needs to always call signal.set_wakeup_fd() when run in the
     main thread;
   
   2. asyncio only needs to call signal.set_wakeup_fd() when a user
     registers a signal handler.
   
   (2) means that if the user had not set up any signals, the signal
   wakeup FD stays the same between different asyncio runs.  This commit
   fixes uvloop signal implementation to make sure that uvloop behaves
   the same way as asyncio in regards to signal wakeup FD between the
   loop runs.  It also ensures that uvloop always have a proper
   self-pipe set up so that ^C is always supported when it is run in
   the main thread.
   
   Issue #295.

   

   1st1 committed Oct 29, 2019

   Loading status checks…
   Verified

   This commit was signed with a verified signature.

   1st1 Yury Selivanov

   GPG key ID: E6ABA2A46889EBBB Learn about signing commits

   fa1fd10