On Fri, Jan 22, 2010 at 11:07 AM, Collin Winter collinwin...@google.com wrote:
Hey Jake,
On Thu, Jan 21, 2010 at 10:48 AM, Jake McGuire mcgu...@google.com wrote:
On Thu, Jan 21, 2010 at 10:19 AM, Reid Kleckner r...@mit.edu wrote:
On Thu, Jan 21, 2010 at 12:27 PM, Jake McGuire
On 1/23/2010 2:53 AM, Martin v. Löwis wrote:
So for the limited case of text IO, Python 3.x now makes a guess.
However, this guess is not in the face of ambiguity: it is the
locale that the user (or his administrator) has selected,
That is a mistaken assumption for many. I have never, that I
So for the limited case of text IO, Python 3.x now makes a guess.
However, this guess is not in the face of ambiguity: it is the
locale that the user (or his administrator) has selected,
That is a mistaken assumption for many. I have never, that I know of,
selected a locale on any of about
Terry Reedy tjreedy at udel.edu writes:
If the current guess is based on a mistaken assumption -- that it is
giving the user what the user asked for -- it might be reconsidered. I
personally would prefer that the default file encoding for Python 3 be
utf-8 on any machine my code runs on
Hi list,
It looks like the python interpreter environment is easily movable between two
directories because the sys.prefix variable is changed automatically when I run
the interpreter so the interpreter will find his libraries... however in the
Python documentation I found that
Martin v. Löwis wrote:
This all begs the question: why is there a default? and why is the
default a guess?
I have to admit that I was completely oblivious to this potential
pitfall, and mostly that's because in the most common case, I am working
with ASCII files.
You answered your own
No, but it's most likely a wrong guess, since text files don't
really have anything to do with what the user wants to see in
a user interface.
That also depends on the operating system. On Windows, there is
a long tradition of encoding all text in the system code page.
All text editors on
Martin v. Löwis wrote:
No, but it's most likely a wrong guess, since text files don't
really have anything to do with what the user wants to see in
a user interface.
That also depends on the operating system. On Windows, there is
a long tradition of encoding all text in the system code
M.-A. Lemburg wrote:
Martin v. Löwis wrote:
Hmm - what do you mean by normally? Normally, text files are meant
for human readers, not for exchange between programs.
It's rather common to exchange text files between users... and
in form of XML and CSV files, these also tend to get used as
M.-A. Lemburg mal at egenix.com writes:
It's rather common to exchange text files between users... and
in form of XML and CSV files, these also tend to get used as
input for programs every now and then
For XML files, encoding should be taken care of by the XML layer, not the IO
layer. That
Antoine Pitrou wrote:
M.-A. Lemburg mal at egenix.com writes:
It's rather common to exchange text files between users... and
in form of XML and CSV files, these also tend to get used as
input for programs every now and then
For XML files, encoding should be taken care of by the XML layer,
Nick Coghlan wrote:
M.-A. Lemburg wrote:
Martin v. Löwis wrote:
Hmm - what do you mean by normally? Normally, text files are meant
for human readers, not for exchange between programs.
It's rather common to exchange text files between users... and
in form of XML and CSV files, these also
Hi Collin
IMO it'll be better to make Unladen Swallow project a module, to be
installed and used if needed, so demanding to users the choice of having it
or not. The same way psyco does, indeed.
Nowadays it requires too much memory, longer loading time, and fat binaries
for not-so-great
On 1/23/2010 7:53 AM, Antoine Pitrou wrote:
Terry Reedytjreedyat udel.edu writes:
If the current guess is based on a mistaken assumption -- that it is
giving the user what the user asked for -- it might be reconsidered. I
personally would prefer that the default file encoding for Python 3 be
Terry Reedy tjreedy at udel.edu writes:
Dreadfully rong. In general, the default encoding on my Windows *does
not work* on Python3 strings but causes
UnicodeEncodeError:
If the text is not written to the file, it is completely non-portable.
You must mistake portable for something else.
Le samedi 23 janvier 2010 à 20:43 +0100, M.-A. Lemburg a écrit :
Now, we cannot easily remove this guessing since we're in stable
mode again with 3.1. Perhaps we should add a way to at least be
able to switch off this guessing, so that applications can be
tested in a predictable way, rather
16 matches
Mail list logo
