On 7/12/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Joe Gregorio wrote:
> > flush() raises
> > ValueError() if the file is already closed,
> >
> > Should io.py raise OSError instead of ValueError?
>
> Is it really necessary to raise anything at all?
> An already-closed file is as flushed as it can
On 7/12/07, Neil Schemenauer <[EMAIL PROTECTED]> wrote:
> It's a small detail but I wonder if it's time to stop using a
> leading underscore for internal APIs. I'm not sure what would be a
> good replacement, perhaps a trailing underscore. In case people
> don't remember, the _Py prefix could, th
Guido van Rossum wrote:
> On 7/11/07, Walter Dörwald <[EMAIL PROTECTED]> wrote:
>> I guess for the final version of Py3000 type_set_name() in typeobject.c
>> will not downgrade unicode strings to str8, but instead upgrade str8
>> objects to unicode.
>
> Right, Thomas is working on this (but I have
On 7/12/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 7/12/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> > Joe Gregorio wrote:
> > > flush() raises
> > > ValueError() if the file is already closed,
> > >
> > > Should io.py raise OSError instead of ValueError?
> >
> > Is it really necessary to
On Thu, Jul 12, 2007 at 10:04:44AM +0300, Guido van Rossum wrote:
> There are lots of things we do that could theoretically be bad C. I
> doubt that this particular one will ever bite us. Are there any other
> reasons for such a change?
I think Python is one of the only open source projects to use
