[Bug python/12150] New: sys.stdout and sys.stderr should have a 'fileno' method

[Bug python/12150] New: sys.stdout and sys.stderr should have a 'fileno' method

[markflorisson88 at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12150

           Summary: sys.stdout and sys.stderr should have a 'fileno'
                    method
           Product: gdb
           Version: 7.0
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned@sourceware.org
        ReportedBy: markflorisson88@gmail.com


sys.stdout and sys.stderr are replaced by GdbOutputFile instances, which do not
implement 'fileno'. This method should return the file descriptor associated
with that I/O stream. Even if pagination is used I think fileno should return
the appropriate file descriptor.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug python/12150] sys.stdout and sys.stderr should have a 'fileno' method

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12150

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2010-10-22 21:55:21 UTC ---
When is this necessary?

Also, these might be redirected to a string buffer,
in which case there is no fileno.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug python/12150] sys.stdout and sys.stderr should have a 'fileno' method

[markflorisson88 at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12150

--- Comment #2 from Mark Florisson <markflorisson88 at gmail dot com> 2010-10-22 22:05:21 UTC ---
(In reply to comment #1)
> When is this necessary?
Several cases, like duping, selecting, using os.read/os.write etc, although
admittedly no specific gdb use case comes to mind.

> Also, these might be redirected to a string buffer,
> in which case there is no fileno.
In case of pagination? In any case, if the user wants to use any of the
aforementioned functions (or use a library that asks for the fileno), thereby
bypassing pagination, I think this should still be possible.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug python/12150] sys.stdout and sys.stderr should have a 'fileno' method

[ratmice at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=12150

matt rice <ratmice at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ratmice at gmail dot com

--- Comment #3 from matt rice <ratmice at gmail dot com> 2011-08-24 17:04:49 UTC ---
one use case i came across is...

from curses import *
setupterm(None, sys.stdout)

i currently just hacked my scripts to
setupterm(None, 1)

which seems to work fine in my case...
generating the correct escape sequences for the terminal, not actual curses
stuff.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.