On 29 April 2004, Gustavo Niemeyer said: > I have two small customizations I've used in most projects I've > plugged optparse into. Since they're simple and generic, I'd > like to integrate them back in optparser. These features are: > > - Add a help formatter which uses capitalized headers. Sure, looks simple enough. > - Add a "help" keyword in OptionParser, allowing straightforward > addition of a custom help messages. How is that different from the existing 'description' that David Goodger added for Optik 1.4? > Comments? > > Also, how are we currently handling changes in optparser? Do we > have an "official" maintainer (Greg?). IOW, should I: As it says at the top of optparse.py: Originally distributed as Optik; see http://optik.sourceforge.net/ . If you have problems with this module, please do not file bugs, patches, or feature requests with Python; instead, use Optik's SourceForge project page: http://sourceforge.net/projects/optik For support, use the optik-users at lists.sourceforge.net mailing list (http://lists.sourceforge.net/lists/listinfo/optik-users). So either post your patches to optik-users at lists.sourceforge.net, or file 'em on the Optik tracker at SF. Nothing wrong with cc'ing python-dev at the same time, though. Greg -- Greg Ward <gward at python.net> http://www.gerg.ca/ All of science is either physics or stamp collecting.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4