M.-A. Lemburg wrote:
> How can a test break when you change the error message text ?
> I'd say that the test was broken: you should never
> rely on a particular message text since these can
> and do change rather often.
When Docutils reports errors, it sometimes uses the exception text returned
by Python. The test that broke is one of those; it tests for an expected
exception. I'm not questioning the validity of the change, just the
backport. I'm fine with the change in 2.3, but I question whether the
changed behavior should have been back backported to 2.2.2. I don't see the
old text as a bug; the new text is improved, true, but that says
"enhancement" to me, not "bugfix". My post was a question that goes to
backport policy.
--
David Goodger <goodger@python.org> Open-source projects:
- Python Docutils: http://docutils.sourceforge.net/
(includes reStructuredText: http://docutils.sf.net/rst.html)
- The Go Tools Project: http://gotools.sourceforge.net/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4