debconf.py should only mess with sys.stdout if we're using it for writing

Bug #300146 reported by Xavid Pretzer on 2008-11-20
4
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: debconf

It's confusing and pointless for Debconf objects in debconf.py to change sys.stdout when you pass in your own file as write, such that it's not using sys.stdout at all.

I'm basing this off source package debconf-1.5.23ubuntu1.

I've attached a patch that causes debconf.py to only modify sys.stdout when the write parameter to a newly-constructed Debconf instance is unspecified.

Xavid Pretzer (xavid) wrote :
Colin Watson (cjwatson) wrote :

I'd like to think about this quite hard in the light of bug 24727.

Changed in debconf:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers