classification
Title: extend captured_output to simulate different stdout.encoding
Type: enhancement Stage: patch review
Components: Tests Versions: Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: berker.peksag, eric.araujo, ezio.melotti, flox, mike_hart
Priority: normal Keywords: easy, patch

Created on 2010-02-22 13:09 by flox, last changed 2019-03-15 23:39 by BreamoreBoy.

Files
File name Uploaded Description Edit
issue7982.diff berker.peksag, 2014-06-23 16:36 review
Messages (3)
msg99730 - (view) Author: Florent Xicluna (flox) * (Python committer) Date: 2010-02-22 13:09
For some tests (doctest, unittest, pydoc...) it would be useful to simulate different stdout encodings ("ascii", "utf-8", ...).

The context manager could accept an optional encoding argument in this case.
msg220756 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-06-16 20:37
Seems like a good idea but it'll go nowhere without a patch, anybody up for it?
msg221366 - (view) Author: Berker Peksag (berker.peksag) * (Python committer) Date: 2014-06-23 16:36
Here's a patch to add an optional encoding parameter to captured_stdout.
History
Date User Action Args
2019-03-15 23:39:14BreamoreBoysetnosy: - BreamoreBoy
2014-06-23 16:36:33berker.peksagsetfiles: + issue7982.diff

nosy: + berker.peksag
messages: + msg221366

keywords: + patch
stage: needs patch -> patch review
2014-06-17 11:55:22berker.peksagsetversions: - Python 2.7
2014-06-16 20:37:15BreamoreBoysetnosy: + BreamoreBoy

messages: + msg220756
versions: + Python 2.7, Python 3.5, - Python 3.4
2013-07-25 04:10:22ezio.melottisetnosy: + ezio.melotti
2013-07-06 17:54:29serhiy.storchakasetversions: + Python 3.4, - Python 3.2
2013-07-06 13:19:09mike_hartsetnosy: + mike_hart
2010-11-28 04:02:10eric.araujosetnosy: + eric.araujo
2010-11-28 04:02:02eric.araujosetkeywords: + easy
stage: needs patch
2010-07-11 14:22:11BreamoreBoysetversions: + Python 3.2, - Python 2.7
2010-02-22 13:09:16floxcreate