On Thu, May 6, 2010 at 5:59 AM, Sarah Mount wrote:
> On 5 May 2010 10:17, Carl Banks wrote:
>> On May 2, 11:06 am, Sarah Mount wrote:
>>> This is a bit of an odd question, but is there any way for a Python
>>> debugger to suppress I/O generated by the program which is being
>>> debugged? I guess
On 5 May 2010 10:17, Carl Banks wrote:
> On May 2, 11:06 am, Sarah Mount wrote:
>> This is a bit of an odd question, but is there any way for a Python
>> debugger to suppress I/O generated by the program which is being
>> debugged? I guess an "obvious" thing to do would be to replace core
>> part
On May 2, 11:06 am, Sarah Mount wrote:
> This is a bit of an odd question, but is there any way for a Python
> debugger to suppress I/O generated by the program which is being
> debugged? I guess an "obvious" thing to do would be to replace core
> parts of the standard library and change any relev
This is a bit of an odd question, but is there any way for a Python
debugger to suppress I/O generated by the program which is being
debugged? I guess an "obvious" thing to do would be to replace core
parts of the standard library and change any relevant imports in the
locals and globals dicts to f
