Message 213109 - Python tracker

➜

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	zzzeek
Recipients	Jeremy.Fishman, ncoghlan, pitrou, terry.reedy, ulidtko, zzzeek
Date	2014-03-11.00:25:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
my users are reporting one of these issues, and while I can easily catch IOError on Python 2, I can't catch anything on Python 3, and pointing SIGPIPE to SIG_DFL isn't an option because this is for Alembic migrations and the command needs to complete its work. What is/will be the recommended solution for people who want their programs to finish totally but not complain when their pipe is cut off in Python 3?

my users are reporting one of these issues, and while I can easily catch IOError on Python 2, I can't catch anything on Python 3, and pointing SIGPIPE to SIG_DFL isn't an option because this is for Alembic migrations and the command needs to complete its work.

What is/will be the recommended solution for people who want their programs to finish totally but not complain when their pipe is cut off in Python 3?

History
Date	User	Action	Args
2014-03-11 00:25:06	zzzeek	set	recipients: + zzzeek, terry.reedy, ncoghlan, pitrou, ulidtko, Jeremy.Fishman
2014-03-11 00:25:06	zzzeek	set	messageid: <[email protected]>
2014-03-11 00:25:06	zzzeek	link	issue11380 messages
2014-03-11 00:25:05	zzzeek	create