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

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to