Tim Peters added the comment: This should remain closed. It's "a feature" that doctest demands exact textual equality, and that the only way to override this is with one of the `#doctest:` flags. "What you see is what you get - exactly" is one of doctest's fundamental design goals.
If you would like to open a different report, suggesting (e.g.) a new "#doctest: object_equality" flag, go ahead. But I don't expect that would get a warm reception: there are many ways to write doctests with sets and dicts that already work fine. That you may have to add additional functions to make them pass in all cases isn't a bug: it's being explicit about that the raw unprocessed output is _not_ reliable. If you don't want that level of pickiness, fine, use something else :-) ---------- nosy: +tim.peters _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3332> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
