Chris Jerdonek added the comment: Here is an updated patch for review (just for the default branch for now).
The main change from the previous patch is that the ValueError exception is now documented. A few additional comments/questions: Is there a better way to signify in the documentation that certain behavior is an unfixable bug as opposed to desired behavior? Would that be appropriate here? I created a new folder inside Lib/test for supporting test files specific to doctest. In addition to the two new files this patch adds, I would also like to move the eight existing support files into this new directory: doctest_aliases.py test_doctest.txt test_doctest3.txt sample_doctest.py test_doctest2.py test_doctest4.txt test_doctest.py test_doctest2.txt Can that be done as a separate change after the patch for this issue, or should it be done before? Assuming people are okay with keeping this ValueError behavior the same in the maintenance releases (i.e. not handling this as a bug fix), would people be open to changing the behavior in future versions, or should we keep the behavior the same in future versions as well? ---------- Added file: http://bugs.python.org/file26990/issue-14649-2.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14649> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
