Antoine Pitrou:
> I don't have a Windows machine at hand right now to test it, but, even
> if this solution works, it breaks the principle of least astonishment:
Astonishment is subjective and so a poor tool to measure by. At one
stage Ruby tried to follow the more common formulation "principl
Le vendredi 09 septembre 2005 à 23:09 +1000, Neil Hodgson a écrit :
> Antoine Pitrou:
>
> > As for seamless unicode support, there are also problems sometimes with
> > filenames and filepaths: see e.g.
> > https://sourceforge.net/tracker/?func=detail&aid=1283895&group_id=5470&atid=105470
>
>T
Antoine Pitrou:
> As for seamless unicode support, there are also problems sometimes with
> filenames and filepaths: see e.g.
> https://sourceforge.net/tracker/?func=detail&aid=1283895&group_id=5470&atid=105470
This bug report is using byte string arguments causing byte string
processing rathe
Antoine Pitrou wrote:
> - seamless unicode support: how about making the default Python
> charset utf-8 instead of ascii ? right now, someone (say an American or
> English) who does not design his app with non-ascii characters in mind
> may have a surprise when users enter those characters in cus
> This does make me think of the interesting prospect of an internationalised
> string literal, though (e.g., _"This an il8n string"). I'm not sure it would
> be enough of a win over the status quo though,
I don't think so either. i18n doesn't require its specific string
notation (in addition,
