This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Rhamphoryncus
Recipients Rhamphoryncus, georg.brandl, gustavo, gvanrossum, jdemeyer
Date 2019-04-09.18:55:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Disagree; if you're writing signal-handling code you should be very careful to do it properly, even if that's only proper for your current platform.  If you can't do it properly you should find an alternative that doesn't involve signals.

The fact that sig_atomic_t is only 1 byte on VxWorks strongly implies using int WILL fail in strange ways on that platform.  I can see three options:

1) use pycore_atomic.h, implementing it for VxWorks if you haven't already.  This also implies sig_atomic_t could have been int but wasn't for some reason, such as performance.
2) disable wakeup_fd entirely.  It's obscure, GNOME being the biggest user I can think of.
3) unpack the int into an array of sig_atomic_t.  Only the main thread writes to it so this method is ugly but viable.
Date User Action Args
2019-04-09 18:55:56Rhamphoryncussetrecipients: + Rhamphoryncus, gvanrossum, georg.brandl, gustavo, jdemeyer
2019-04-09 18:55:56Rhamphoryncussetmessageid: <>
2019-04-09 18:55:56Rhamphoryncuslinkissue1583 messages
2019-04-09 18:55:56Rhamphoryncuscreate