[issue1352] Preliminary stderr patch

2007-11-02 Thread Martin v. Löwis
Martin v. Löwis added the comment: > 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 t

[issue1352] Preliminary stderr patch

2007-11-02 Thread Guido van Rossum
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? If so, the role field could just be a dropdown instead of a list of roles... ___

[issue1352] Preliminary stderr patch

2007-11-02 Thread Martin v. Löwis
Martin v. Löwis added the comment: I just created http://wiki.python.org/moin/TrackerAccessControl which specifies all permissions in the tracker in detail. -- nosy: +loewis __ Tracker <[EMAIL PROTECTED]> _

[issue1352] Preliminary stderr patch

2007-11-02 Thread Georg Brandl
Georg Brandl added the comment: I've submitted a new bug in the meta tracker. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubs

[issue1352] Preliminary stderr patch

2007-11-01 Thread Guido van Rossum
Guido van Rossum added the comment: 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 rol

[issue1352] Preliminary stderr patch

2007-11-01 Thread Georg Brandl
Georg Brandl added the comment: You should be able to close it yourself now :) -- nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]> __ ___ Pyth

[issue1352] Preliminary stderr patch

2007-10-30 Thread Christian Heimes
Christian Heimes added the comment: 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? Christ

[issue1352] Preliminary stderr patch

2007-10-30 Thread Guido van Rossum
Guido van Rossum added the comment: 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. -- resolution: -> accepted status: open -> closed _

[issue1352] Preliminary stderr patch

2007-10-29 Thread Christian Heimes
Christian Heimes added the comment: 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

[issue1352] Preliminary stderr patch

2007-10-29 Thread Guido van Rossum
Guido van Rossum added the comment: 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 PyDi

[issue1352] Preliminary stderr patch

2007-10-29 Thread Guido van Rossum
Changes by Guido van Rossum: -- assignee: -> gvanrossum priority: -> high __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1352] Preliminary stderr patch

2007-10-29 Thread Christian Heimes
Christian Heimes added the comment: Improved patch -- nosy: +gvanrossum Added file: http://bugs.python.org/file8648/py3k_preliminary_stderr2.patch __ Tracker <[EMAIL PROTECTED]> __Index: P

[issue1352] Preliminary stderr patch

2007-10-28 Thread Christian Heimes
New submission from Christian Heimes: 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. -- components: Interpreter Core files