This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sergey.Kirpichev
Recipients Sergey.Kirpichev
Date 2016-01-12.18:20:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1452622857.37.0.137754453324.issue26092@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-01-12 18:20:57Sergey.Kirpichevsetrecipients: + Sergey.Kirpichev
2016-01-12 18:20:57Sergey.Kirpichevsetmessageid: <1452622857.37.0.137754453324.issue26092@psf.upfronthosting.co.za>
2016-01-12 18:20:57Sergey.Kirpichevlinkissue26092 messages
2016-01-12 18:20:57Sergey.Kirpichevcreate