diff options
author | Tim Peters <tim.peters@gmail.com> | 2003-06-27 20:48:05 (GMT) |
---|---|---|
committer | Tim Peters <tim.peters@gmail.com> | 2003-06-27 20:48:05 (GMT) |
commit | 6ebe61fa807d250ccab419473abd8d746a932e75 (patch) | |
tree | 18350da8265076dbebafc9fca16fe1b5506f6206 /Misc | |
parent | 6cf26195c6e206cba1bb3ebe554e82ab52304bd5 (diff) | |
download | cpython-6ebe61fa807d250ccab419473abd8d746a932e75.zip cpython-6ebe61fa807d250ccab419473abd8d746a932e75.tar.gz cpython-6ebe61fa807d250ccab419473abd8d746a932e75.tar.bz2 |
A hack to ease compatibility with pre-2.3 Pythons: by default, doctest
now accepts "True" when a test expects "1", and similarly for "False"
versus "0". This is un-doctest-like, but on balance makes it much
more pleasant to write doctests that pass under 2.2 and 2.3. I expect
it to go away again, when 2.2 is forgotten. In the meantime, there's
a new doctest module constant that can be passed to a new optional
argument, if you want to turn this behavior off.
Note that this substitution is very simple-minded: the expected and
actual outputs have to consist of single tokens. No attempt is made,
e.g., to accept [True, False] when a test expects [1, 0]. This is a
simple hack for simple tests, and I intend to keep it that way.
Diffstat (limited to 'Misc')
-rw-r--r-- | Misc/NEWS | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -83,6 +83,14 @@ Extension modules Library ------- +- For compatibility with doctests created before 2.3, if an expected + output block consists solely of "1" and the actual output block + consists solely of "True", it's accepted as a match; similarly + for "0" and "False". This is quite un-doctest-like, but is practical. + The behavior can be disabled by passing the new doctest module + constant DONT_ACCEPT_TRUE_FOR_1 to the new optionflags optional + argument. + - The cgitb module has been extended to support plain text display (SF patch 569574). |