[issue4297] Add error_log attribute to optparse.OptionParser

Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker ___ ___

[issue4297] Add error_log attribute to optparse.OptionParser

Irit Katriel added the comment: Following issue9938, argparse now offers a convenient way to handle errors. I propose to close this issue as out of date. -- nosy: +iritkatriel status: open -> pending ___ Python tracker

[issue4297] Add error_log attribute to optparse.OptionParser

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4297 ___ ___

[issue4297] Add error_log attribute to optparse.OptionParser

Sandro Tosi sandro.t...@gmail.com added the comment: Hi Daniel, did you read Steven suggestions? are you willing to propose a patch about your feature request against argparse (optparse is deprecated and no more under development in stdlib)? -- nosy: +sandro.tosi

[issue4297] Add error_log attribute to optparse.OptionParser

Steven Bethard steven.beth...@gmail.com added the comment: Not sure, but I think _print_message in argparse isn't exactly what the OP is looking for if they really only care about errors. If you want to override how errors are printed, then it's absolutely correct to override the error method

[issue4297] Add error_log attribute to optparse.OptionParser

Changes by Éric Araujo mer...@netwok.org: -- nosy: +merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4297 ___ ___ Python-bugs-list mailing

[issue4297] Add error_log attribute to optparse.OptionParser

R. David Murray rdmur...@bitdance.com added the comment: Having an easy way to control where output goes makes sense. This is a new feature, however, and thus only a candidate for 3.2, and in 3.2 it would be better to target it at argparse. I think argarse makes this easier to do via

[issue4297] Add error_log attribute to optparse.OptionParser

Mark Lawrence breamore...@yahoo.co.uk added the comment: To move this forward would need patches against py3k, assuming that the original patch is agreed upon in principle. -- nosy: +BreamoreBoy versions: +Python 3.1, Python 3.2 ___ Python tracker

[issue4297] Add error_log attribute to optparse.OptionParser

New submission from Daniel Watkins [EMAIL PROTECTED]: I've recently had to subclass optparse.OptionParser, and copy-paste the exit method, just to change where errors were printed to (I needed stdout rather than stderr). I've also had a request from a client to log errors with command-line

[issue4297] Add error_log attribute to optparse.OptionParser

Changes by Raghuram Devarakonda [EMAIL PROTECTED]: -- nosy: +draghuram ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4297 ___ ___ Python-bugs-list