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 tim.peters
Recipients Sergey.Kirpichev, georg.brandl, noam, r.david.murray, tim.peters
Date 2019-05-17.00:17:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558052253.57.0.0259888019969.issue26092@roundup.psfhosted.org>
In-reply-to
Content
Noam Yorav-Raphael, I tried to add you because this is pushing back against your patch in issue 8408.  It's been some years now, and nobody has cared enough to pursue it, so I'll just close this if you still don't care ;-)

As doctest's original author, I appreciate why 8408 was done, but don't think it was "a good" solution.  In fact doctest can have no idea whether an example was _intended_ to be run with or without a custom shell's displayhook function invoked to massage the output first.  So more sensible would have been to add a new doctest directive + optional argument, to make the intent explicit.

Which is certainly more work, and hasn't actually come up as "a problem" yet.
History
Date User Action Args
2019-05-17 00:17:33tim.peterssetrecipients: + tim.peters, georg.brandl, noam, r.david.murray, Sergey.Kirpichev
2019-05-17 00:17:33tim.peterssetmessageid: <1558052253.57.0.0259888019969.issue26092@roundup.psfhosted.org>
2019-05-17 00:17:33tim.peterslinkissue26092 messages
2019-05-17 00:17:33tim.peterscreate