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 telmich
Recipients Jurko.Gospodnetić, barry, eric.araujo, eric.snow, fossilet, neologix, pitrou, poq, r.david.murray, telmich, vstinner
Date 2013-12-21.15:33:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387639996.49.0.795941503086.issue14228@psf.upfronthosting.co.za>
In-reply-to
Content
Victor, the problem is *not* that python exits. This is fine and virtually every other unix program behaves like that.

The problem is that python throws an ugly-to-read and completly senseless backtrace to the novice (end!) user by default. Backtraces are great for debugging and should be treated as such, but not presented to an end user by default.

But I as a developer, who wants to prevent the user seeing a backtrace while she does the most normal thing, this places a huge burden on me and I need to use undocumented workarounds to try to prevent this - in the case of a try... except block around my whole program even without suceess.

The point is that no programming language should shout its internals to an end user and prevent the developer from cushion it easily.

Think about "ls -lR" that throws debugging symbols at you, because you interrupted it - you would not want to see them, nor what you be happy if you had to cushion and especially not if this was not documented and hard to do.

So in short my request is to make python more user friendly by cushion the unnecessary backtrace of a Ctrl-C printed out.
History
Date User Action Args
2013-12-21 15:33:16telmichsetrecipients: + telmich, barry, pitrou, vstinner, fossilet, eric.araujo, r.david.murray, neologix, Jurko.Gospodnetić, eric.snow, poq
2013-12-21 15:33:16telmichsetmessageid: <1387639996.49.0.795941503086.issue14228@psf.upfronthosting.co.za>
2013-12-21 15:33:16telmichlinkissue14228 messages
2013-12-21 15:33:15telmichcreate