Stupid email disclaimers (was: [unicode] inconvenient unicode conversion of non-string arguments)

2006-12-13 Thread Ben Finney
"Marc 'BlackJack' Rintsch" <[EMAIL PROTECTED]> writes: > In <[EMAIL PROTECTED]>, Holger Joukl > wrote: > > [a meaningless disclaimer text at the bottom of every message] > > Maybe you should rethink if it really makes sense to add this huge > block of "nonsense" to a post to a newsgroup or public

Re: [unicode] inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Marc 'BlackJack' Rintsch
In <[EMAIL PROTECTED]>, Holger Joukl wrote: > Der Inhalt dieser E-Mail ist vertraulich. Falls Sie nicht der angegebene > Empfänger sind oder falls diese E-Mail irrtümlich an Sie adressiert wurde, > verständigen Sie bitte den Absender sofort und löschen Sie die E-Mail > sodann. Das unerlaubte Kopie

Re: Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Holger Joukl
[EMAIL PROTECTED] schrieb am 13.12.2006 12:05:33: > Holger Joukl wrote: > > >>> Ok, but I still don't see why these arguments shouldn't simply be > >>> silently ignored > >> > >> >>> import this > > > > You probably refer to "Explicit is better than implicit.". > > "Errors should never pass sile

Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Fredrik Lundh
Holger Joukl wrote: >>> Ok, but I still don't see why these arguments shouldn't simply be >>> silently ignored >> >> >>> import this > > You probably refer to "Explicit is better than implicit.". "Errors should never pass silently." is a better match, I think. you're trying to do an invalid

Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Leo Kislov
Holger Joukl wrote: > [EMAIL PROTECTED] schrieb am 13.12.2006 > 11:02:30: > > > > > Holger Joukl wrote: > > > Hi there, > > > > > > I consider the behaviour of unicode() inconvenient wrt to conversion of > > > non-string > > > arguments. > > > While you can do: > > > > > > >>> unicode(17.3) > > >

Re: Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Holger Joukl
[EMAIL PROTECTED] schrieb am 13.12.2006 11:37:03: > Holger Joukl wrote: > > > Ok, but I still don't see why these arguments shouldn't simply be silently > > ignored > > >>> import this > > > You probably refer to "Explicit is better than implicit.". In that particular case I still think it woul

Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Fredrik Lundh
Holger Joukl wrote: > Ok, but I still don't see why these arguments shouldn't simply be silently > ignored >>> import this -- http://mail.python.org/mailman/listinfo/python-list

Re: Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Holger Joukl
[EMAIL PROTECTED] schrieb am 13.12.2006 11:02:30: > > Holger Joukl wrote: > > Hi there, > > > > I consider the behaviour of unicode() inconvenient wrt to conversion of > > non-string > > arguments. > > While you can do: > > > > >>> unicode(17.3) > > u'17.3' > > > > you cannot do: > > > > >>> unico

Re: inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Leo Kislov
Holger Joukl wrote: > Hi there, > > I consider the behaviour of unicode() inconvenient wrt to conversion of > non-string > arguments. > While you can do: > > >>> unicode(17.3) > u'17.3' > > you cannot do: > > >>> unicode(17.3, 'ISO-8859-1', 'replace') > Traceback (most recent call last): > File

[unicode] inconvenient unicode conversion of non-string arguments

2006-12-13 Thread Holger Joukl
Hi there, I consider the behaviour of unicode() inconvenient wrt to conversion of non-string arguments. While you can do: >>> unicode(17.3) u'17.3' you cannot do: >>> unicode(17.3, 'ISO-8859-1', 'replace') Traceback (most recent call last): File "", line 1, in ? TypeError: coercing to Unicod