Hi Martin,
On Tue, May 20, 2008 at 10:22:37AM +0200, "Martin v. Löwis" wrote:
> In particular, setting this environment variable would also disable
> the detection of whether stdout is a terminal.
In this case, it seems to me that existing programs that start python as
a non-interactive subproces
On Tue, May 20, 2008 at 10:22:03PM +0200, "Martin v. L?wis" wrote:
> >PYTHONIOENCODING?
>
> Unprecise in a different way (as it is meant to apply only to stdout,
> not to all IO), but shorter.
I don't think you can make it both precise and short. If you want to be
precise and have both PYT
> What about PYTHONLANG ?
>
> or something that tries to reflect which environment variables are used
> for this ?
>
> (LC_CTYPE -> PYTHONCTYPE ? if the code uses just LC_CTYPE)
It's not meant to name a locale, but an encoding. In fact, that the
encoding is tied to the locale is IMO a misconcep
>Is it to override locale settings in case the user wants a different
> encoding? for such cases as redirected stdout, or windows console (which
> has an "OEM" encoding that differs from the locale encoding)?
On Windows, the setlocale mechanism isn't used at all, since it doesn't
support nl_la
On 2008-05-20 21:34, Martin v. Löwis wrote:
I'm not exactly sure why, since using .encoding would be useful
in all cases.
Right, I think it should use the file's encoding also for .write.
Could you add that to the proposal ?!
Please also add the ability to set the .encoding on file objects.
> I'm not exactly sure why, since using .encoding would be useful
> in all cases.
Right, I think it should use the file's encoding also for .write.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
On 2008-05-20 20:23, Martin v. Löwis wrote:
Writing Unicode to stdout will still use the default encoding
ASCII to convert it to an 8-bit string.
That's not true.
Are you sure ?
> setenv LC_ALL de_DE.utf8
> python2.5
Python 2.5 (r25:51908, May 9 2007, 00:53:06)
>>> u = u'äöü'
>>> sys.stdout
> PYTHONSTDOUTENCODING could then provide the default to
> sys.stdout.encoding.
Right - that's the proposal.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.
>> You're forgetting about print; in Python 2.x, when stdout is connected to a
>> terminal, the locale settings (typically the LANG, LC_ALL and LC_CTYPE
>> environment variables) are taken into account when 'print' writes to
>> sys.stdout.
>
> Isn't it then enough to make sure your locale setting
> Writing Unicode to stdout will still use the default encoding
> ASCII to convert it to an 8-bit string.
That's not true.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Tue, May 20, 2008 at 12:48 PM, Oleg Broytmann <[EMAIL PROTECTED]> wrote:
> On Tue, May 20, 2008 at 10:22:37AM +0200, "Martin v. L?wis" wrote:
> > I'd like to propose a new environment variable PYTHONSTDOUTENCODING.
> > This is meant to solve various problems that people had with Python
> > not
On Tue, May 20, 2008 at 10:22:37AM +0200, "Martin v. L?wis" wrote:
> I'd like to propose a new environment variable PYTHONSTDOUTENCODING.
> This is meant to solve various problems that people had with Python
> not detecting their terminal encoding correctly; it would override
> any detection that P
On 2008-05-20 12:16, Thomas Wouters wrote:
On Tue, May 20, 2008 at 10:41 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
On 2008-05-20 10:22, Martin v. Löwis wrote:
I'd like to propose a new environment variable PYTHONSTDOUTENCODING.
This is meant to solve various problems that people had with P
On Tue, May 20, 2008 at 12:16 PM, Thomas Wouters <[EMAIL PROTECTED]> wrote:
> You're forgetting about print; in Python 2.x, when stdout is connected to a
> terminal, the locale settings (typically the LANG, LC_ALL and LC_CTYPE
> environment variables) are taken into account when 'print' writes to
>
On Tue, May 20, 2008 at 10:41 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> On 2008-05-20 10:22, Martin v. Löwis wrote:
>
>> I'd like to propose a new environment variable PYTHONSTDOUTENCODING.
>> This is meant to solve various problems that people had with Python
>> not detecting their terminal
On 2008-05-20 10:22, Martin v. Löwis wrote:
I'd like to propose a new environment variable PYTHONSTDOUTENCODING.
This is meant to solve various problems that people had with Python
not detecting their terminal encoding correctly; it would override
any detection that Python would use for determini
16 matches
Mail list logo
