[issue8048] doctest assumes sys.displayhook hasn't been touched

Georg Brandl added the comment: Thanks, applied to 3k in r83268. -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue8048] doctest assumes sys.displayhook hasn't been touched

Noam Yorav-Raphael added the comment: Here is a better and much shorter patch: I use sys.__displayhook__ instead of implementing it in Python, which has the nice side effect of not changing pdb behaviour. -- Added file: http://bugs.python.org/file16581/patch _

[issue8048] doctest assumes sys.displayhook hasn't been touched

Noam Yorav-Raphael added the comment: Ok, here's a patch (against current svn of Python 2) with a test case. I had to fix three tests which combined pdb and doctest, since now, when run under doctest, pdb steps into the displayhook because it's a Python function and not a built-in function. T

[issue8048] doctest assumes sys.displayhook hasn't been touched

Changes by Florent Xicluna : -- nosy: +flox priority: -> normal stage: -> test needed versions: +Python 2.7, Python 3.2 ___ Python tracker ___ __

[issue8048] doctest assumes sys.displayhook hasn't been touched

New submission from Noam Raphael : Hello, This bug is the cause of a bug reported about DreamPie: https://bugs.launchpad.net/bugs/530969 DreamPie (http://dreampie.sourceforge.net) changes sys.displayhook so that values will be sent to the parent process instead of being printed in stdout. Th