TODO@ad73f75c9046
TODO
Thu, 24 Jul 2008 22:35:38 -0400
- author
- Brett Smith <brettcsmith@brettcsmith.org>
- date
- Thu, 24 Jul 2008 22:35:38 -0400
- branch
- trunk
- changeset 85
- ad73f75c9046
- parent 79
- 9c0cc7aef510
- child 86
- e02ca4e9bf42
- permissions
- -rw-r--r--
Use the default action for SIGPIPE.
Using Python's built-in handler makes weird error messages for the user,
and there's no reason not to act like every other Unix program in this
regard. This seems particularly true since we're most likely to get
SIGPIPE with dtrx -l, where we won't write things to disk etc.
-*- text -*- To do: * Investigate the right way to handle SIGPIPE and do so. * --expert mode: prompts don't show an explanation of what the options are, unless you ask with ?. Things which I have a use case/anti-use case for: * Support pisi packages (http://paketler.pardus.org.tr/pardus-2007/) * Steal ideas from <http://martin.ankerl.com/files/e>. * More consistently raise and handle exceptions. Things that are generally good: * Better tests. * Better error messages. Things I think might be good but can't prove: * Consider having options about whether or not to make sane directories, have tarbomb protection, etc. * Use zipfile instead of the zip commands. * Processing from stdin. * shar support.
