New submission from Sergey B Kirpichev: The purpose of doctest's - verify interactive examples. But if your users will use custom displayhook all the time (consider, as examples CAS like SymPy or https://github.com/skirpichev/omg/) - why you must show them examples with the builtin's displayhook?
After https://bugs.python.org/issue8048, sys.displayhook can't be customized for doctest. I think, that decision was wrong and we should have a better solution. PS: In fact, right now this issue can be workarrounded if you instead override sys.__displayhook__ before doctest call. But I believe this "solution" has own problems. ---------- components: Library (Lib) messages: 258115 nosy: Sergey.Kirpichev priority: normal severity: normal status: open title: doctest should allow custom sys.displayhook type: behavior _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26092> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com