On 9/4/06, David Hopwood <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > I've always said (can someone find a quote perhaps?) that there ought
> > to be a sensible default encoding for files (including but not limited
> > to stdin/out/err), perhaps influenced by personalized settings,
> >
Guido van Rossum wrote:
> On 9/3/06, Jim Jewett <[EMAIL PROTECTED]> wrote:
>
>>Two followup questions, then ...
>>
>>(1) To what extent should python support files (including stdin,
>>stdout) in local (non-unicode) encodings? (not at all, per-file,
>>settable global default?)
Per-file, I hope.
On Mon, Sep 04, 2006, Oleg Broytmann wrote:
> On Sun, Sep 03, 2006 at 01:45:28PM -0700, Aahz wrote:
>>
>> You want to be able to read the file and write data to it. That argues
>> in favor of seek(0) and seek(-1) being the only supported behaviors,
>> though.
>
>Sometimes programs need tell(
On Sun, Sep 03, 2006 at 01:45:28PM -0700, Aahz wrote:
> On Sun, Sep 03, 2006, Marcin 'Qrczak' Kowalczyk wrote:
> > "tomer filiba" <[EMAIL PROTECTED]> writes:
> >>
> >> file("foo", "w+") ?
> >
> > What is a rationale of this operation for a text file?
>
> You want to be able to read the file and w
On Sat, Sep 02, 2006 at 06:36:37PM +0200, Georg Brandl wrote:
> While looking at the changes necessary to implement the exception
> related syntax changes (except ... as ..., raise without type),
> I came across some more substantial things that I think must be discussed.
>
> * How should exceptio
