On 30-mei-2006, at 22:32, Tom Cato Amundsen wrote: > optparse > ======== > > Using unicode strings with non-ascii chars.[1] > > I'm working around this by subclassing OptionParser. Below is a > workaround I use in GNU Solfege. Should something like this be > included in python 2.5? Could you please file a bug or feature request for this on SF? Your report might get lost otherwise. Ronald
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