Here is another patch related to stdio from me. It creates and sets up a
very dumb and easy stderr writer until the new io infrastructure is
initialized. It makes debugging problems in the init phase much easier.

Improved patch

Good idea.

Are there any places where PyBytes or PyString are written to stderr? 
Or can you get away with just supporting PyUnicode?

It's "dumb", not "dump".

I wouldn't explicitly remove the old stderr printer -- it will be
deleted automatically by the PyDict_SetItemString() call in
PySys_SetObject().  That way you'll still have it when the
PyFile_FromFd() call fails...

This patch doesn't commute with your 'closefd' patch...

Guido van Rossum wrote:
> Are there any places where PyBytes or PyString are written to stderr? 
> Or can you get away with just supporting PyUnicode?

I could have simple copied the write method from _fileio.c and letting
the argument parser do its job instead of fighting with the API for 20
minutes. :

> It's "dumb", not "dump".

I need an IDE with a context aware spell checker :]

> I wouldn't explicitly remove the old stderr printer -- it will be
> deleted automatically by the PyDict_SetItemString() call in
> PySys_SetObject().  That way you'll still have it when the
> PyFile_FromFd() call fails...

I didn't know that. I'll keep it in place.

I've checked in the patch you added to issue 1329, with one mod: where
you wrote "int fd : 1;" I removed the ": 1" since a field width of one
bit makes no sense here.

Guido van Rossum wrote:
> I've checked in the patch you added to issue 1329, with one mod: where
> you wrote "int fd : 1;" I removed the ": 1" since a field width of one
> bit makes no sense here.

Can you close http://bugs.python.org/issue1771260, too?

Christian

You should be able to close it yourself now :)

Georg, could you explain somewhere in the tracker docs linked from the
tracker side bar what the options are? I looked into giving Christian
more tracker privileges before, but I didn't know what to type in the
Roles box. IOW I don't know what the allowable roles are, what they
mean, or where to find a list that describes them.

On 11/1/07, Georg Brandl <report@bugs.python.org> wrote:
>
> Georg Brandl added the comment:
>
> You should be able to close it yourself now :)

I've submitted a new bug in the meta tracker.

I just created

http://wiki.python.org/moin/TrackerAccessControl

which specifies all permissions in the tracker in detail.

> http://wiki.python.org/moin/TrackerAccessControl
>
> which specifies all permissions in the tracker in detail.

Is it so that Anonymous < User < Developer < Coordinator? If so, the
role field could just be a dropdown instead of a list of roles...

> Guido van Rossum added the comment:
> 
>> http://wiki.python.org/moin/TrackerAccessControl
>>
>> which specifies all permissions in the tracker in detail.
> 
> Is it so that Anonymous < User < Developer < Coordinator? 

Not in roundup per se, no. It is so in this installation.

> If so, the role field could just be a 
> dropdown instead of a list of roles...

I believe a lot of these permissions are redundant. People
holding the Developer role typically also hold the User
role. It might be possible to drop the User role from the
developers, and the User and Developer roles from the Coordinators,
without loss of permissions - but there is a chance that doing
so would break things in case some permission was forgotten.

Regards,
Martin