/usr/share/doc/python-pytest-doc/html/announce/release-2.5.0.html is in python-pytest-doc 2.8.7-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>pytest-2.5.0: now down to ZERO reported bugs!</title>
<link rel="stylesheet" href="../_static/flasky.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '2.8.7',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<link rel="shortcut icon" href="../_static/pytest1favi.ico"/>
<link rel="top" title="None" href="../contents.html" />
<link rel="up" title="Release announcements" href="index.html" />
<link rel="next" title="pytest-2.4.2: colorama on windows, plugin/tmpdir fixes" href="release-2.4.2.html" />
<link rel="prev" title="pytest-2.5.1: fixes and new home page styling" href="release-2.5.1.html" />
<meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9">
</head>
<body role="document">
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="release-2.4.2.html" title="pytest-2.4.2: colorama on windows, plugin/tmpdir fixes"
accesskey="N">next</a></li>
<li class="right" >
<a href="release-2.5.1.html" title="pytest-2.5.1: fixes and new home page styling"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="../contents.html">pytest-2.8.7</a> »</li>
<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">Release announcements</a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body" role="main">
<div class="section" id="pytest-2-5-0-now-down-to-zero-reported-bugs">
<h1>pytest-2.5.0: now down to ZERO reported bugs!<a class="headerlink" href="#pytest-2-5-0-now-down-to-zero-reported-bugs" title="Permalink to this headline">¶</a></h1>
<p>pytest-2.5.0 is a big fixing release, the result of two community bug
fixing days plus numerous additional works from many people and
reporters. The release should be fully compatible to 2.4.2, existing
plugins and test suites. We aim at maintaining this level of ZERO reported
bugs because it’s no fun if your testing tool has bugs, is it? Under a
condition, though: when submitting a bug report please provide
clear information about the circumstances and a simple example which
reproduces the problem.</p>
<p>The issue tracker is of course not empty now. We have many remaining
“enhacement” issues which we’ll hopefully can tackle in 2014 with your
help.</p>
<p>For those who use older Python versions, please note that pytest is not
automatically tested on python2.5 due to virtualenv, setuptools and tox
not supporting it anymore. Manual verification shows that it mostly
works fine but it’s not going to be part of the automated release
process and thus likely to break in the future.</p>
<p>As usual, current docs are at</p>
<blockquote>
<div><a class="reference external" href="http://pytest.org">http://pytest.org</a></div></blockquote>
<p>and you can upgrade from pypi via:</p>
<div class="highlight-python"><div class="highlight"><pre>pip install -U pytest
</pre></div>
</div>
<p>Particular thanks for helping with this release go to Anatoly Bubenkoff,
Floris Bruynooghe, Marc Abramowitz, Ralph Schmitt, Ronny Pfannschmidt,
Donald Stufft, James Lan, Rob Dennis, Jason R. Coombs, Mathieu Agopian,
Virgil Dupras, Bruno Oliveira, Alex Gaynor and others.</p>
<p>have fun,
holger krekel</p>
<div class="section" id="id1">
<h2>2.5.0<a class="headerlink" href="#id1" title="Permalink to this headline">¶</a></h2>
<ul>
<li><p class="first">dropped python2.5 from automated release testing of pytest itself
which means it’s probably going to break soon (but still works
with this release we believe).</p>
</li>
<li><p class="first">simplified and fixed implementation for calling finalizers when
parametrized fixtures or function arguments are involved. finalization
is now performed lazily at setup time instead of in the “teardown phase”.
While this might sound odd at first, it helps to ensure that we are
correctly handling setup/teardown even in complex code. User-level code
should not be affected unless it’s implementing the pytest_runtest_teardown
hook and expecting certain fixture instances are torn down within (very
unlikely and would have been unreliable anyway).</p>
</li>
<li><p class="first">PR90: add –color=yes|no|auto option to force terminal coloring
mode (“auto” is default). Thanks Marc Abramowitz.</p>
</li>
<li><p class="first">fix issue319 - correctly show unicode in assertion errors. Many
thanks to Floris Bruynooghe for the complete PR. Also means
we depend on py>=1.4.19 now.</p>
</li>
<li><p class="first">fix issue396 - correctly sort and finalize class-scoped parametrized
tests independently from number of methods on the class.</p>
</li>
<li><p class="first">refix issue323 in a better way – parametrization should now never
cause Runtime Recursion errors because the underlying algorithm
for re-ordering tests per-scope/per-fixture is not recursive
anymore (it was tail-call recursive before which could lead
to problems for more than >966 non-function scoped parameters).</p>
</li>
<li><p class="first">fix issue290 - there is preliminary support now for parametrizing
with repeated same values (sometimes useful to to test if calling
a second time works as with the first time).</p>
</li>
<li><p class="first">close issue240 - document precisely how pytest module importing
works, discuss the two common test directory layouts, and how it
interacts with PEP420-namespace packages.</p>
</li>
<li><p class="first">fix issue246 fix finalizer order to be LIFO on independent fixtures
depending on a parametrized higher-than-function scoped fixture.
(was quite some effort so please bear with the complexity of this sentence :)
Thanks Ralph Schmitt for the precise failure example.</p>
</li>
<li><p class="first">fix issue244 by implementing special index for parameters to only use
indices for paramentrized test ids</p>
</li>
<li><p class="first">fix issue287 by running all finalizers but saving the exception
from the first failing finalizer and re-raising it so teardown will
still have failed. We reraise the first failing exception because
it might be the cause for other finalizers to fail.</p>
</li>
<li><p class="first">fix ordering when mock.patch or other standard decorator-wrappings
are used with test methods. This fixues issue346 and should
help with random “xdist” collection failures. Thanks to
Ronny Pfannschmidt and Donald Stufft for helping to isolate it.</p>
</li>
<li><p class="first">fix issue357 - special case “-k” expressions to allow for
filtering with simple strings that are not valid python expressions.
Examples: “-k 1.3” matches all tests parametrized with 1.3.
“-k None” filters all tests that have “None” in their name
and conversely “-k ‘not None’”.
Previously these examples would raise syntax errors.</p>
</li>
<li><p class="first">fix issue384 by removing the trial support code
since the unittest compat enhancements allow
trial to handle it on its own</p>
</li>
<li><p class="first">don’t hide an ImportError when importing a plugin produces one.
fixes issue375.</p>
</li>
<li><p class="first">fix issue275 - allow usefixtures and autouse fixtures
for running doctest text files.</p>
</li>
<li><p class="first">fix issue380 by making –resultlog only rely on longrepr instead
of the “reprcrash” attribute which only exists sometimes.</p>
</li>
<li><p class="first">address issue122: allow @pytest.fixture(params=iterator) by exploding
into a list early on.</p>
</li>
<li><p class="first">fix pexpect-3.0 compatibility for pytest’s own tests.
(fixes issue386)</p>
</li>
<li><p class="first">allow nested parametrize-value markers, thanks James Lan for the PR.</p>
</li>
<li><p class="first">fix unicode handling with new monkeypatch.setattr(import_path, value)
API. Thanks Rob Dennis. Fixes issue371.</p>
</li>
<li><p class="first">fix unicode handling with junitxml, fixes issue368.</p>
</li>
<li><p class="first">In assertion rewriting mode on Python 2, fix the detection of coding
cookies. See issue #330.</p>
</li>
<li><p class="first">make “–runxfail” turn imperative pytest.xfail calls into no ops
(it already did neutralize pytest.mark.xfail markers)</p>
</li>
<li><p class="first">refine pytest / pkg_resources interactions: The AssertionRewritingHook
PEP302 compliant loader now registers itself with setuptools/pkg_resources
properly so that the pkg_resources.resource_stream method works properly.
Fixes issue366. Thanks for the investigations and full PR to Jason R. Coombs.</p>
</li>
<li><p class="first">pytestconfig fixture is now session-scoped as it is the same object during the
whole test run. Fixes issue370.</p>
</li>
<li><p class="first">avoid one surprising case of marker malfunction/confusion:</p>
<div class="highlight-python"><div class="highlight"><pre>@pytest.mark.some(lambda arg: ...)
def test_function():
</pre></div>
</div>
<p>would not work correctly because pytest assumes @pytest.mark.some
gets a function to be decorated already. We now at least detect if this
arg is an lambda and thus the example will work. Thanks Alex Gaynor
for bringing it up.</p>
</li>
<li><p class="first">xfail a test on pypy that checks wrong encoding/ascii (pypy does
not error out). fixes issue385.</p>
</li>
<li><p class="first">internally make varnames() deal with classes’s __init__,
although it’s not needed by pytest itself atm. Also
fix caching. Fixes issue376.</p>
</li>
<li><p class="first">fix issue221 - handle importing of namespace-package with no
__init__.py properly.</p>
</li>
<li><p class="first">refactor internal FixtureRequest handling to avoid monkeypatching.
One of the positive user-facing effects is that the “request” object
can now be used in closures.</p>
</li>
<li><p class="first">fixed version comparison in pytest.importskip(modname, minverstring)</p>
</li>
<li><p class="first">fix issue377 by clarifying in the nose-compat docs that pytest
does not duplicate the unittest-API into the “plain” namespace.</p>
</li>
<li><p class="first">fix verbose reporting for @mock’d test functions</p>
</li>
</ul>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="../contents.html">
<img class="logo" src="../_static/pytest1.png" alt="Logo"/>
</a></p><h3><a href="../contents.html">Table Of Contents</a></h3>
<ul>
<li><a href="../index.html">Home</a></li>
<li><a href="../contents.html">Contents</a></li>
<li><a href="../getting-started.html">Install</a></li>
<li><a href="../example/index.html">Examples</a></li>
<li><a href="../customize.html">Customize</a></li>
<li><a href="../contact.html">Contact</a></li>
<li><a href="../talks.html">Talks/Posts</a></li>
<li><a href="../changelog.html">Changelog</a></li>
</ul>
<hr>
<ul>
<li><a class="reference internal" href="#">pytest-2.5.0: now down to ZERO reported bugs!</a><ul>
<li><a class="reference internal" href="#id1">2.5.0</a></li>
</ul>
</li>
</ul>
<h3>Related Topics</h3>
<ul>
<li><a href="../contents.html">Documentation overview</a><ul>
<li><a href="index.html">Release announcements</a><ul>
<li>Previous: <a href="release-2.5.1.html" title="previous chapter">pytest-2.5.1: fixes and new home page styling</a></li>
<li>Next: <a href="release-2.4.2.html" title="next chapter">pytest-2.4.2: colorama on windows, plugin/tmpdir fixes</a></li>
</ul></li>
</ul></li>
</ul><h3>Useful Links</h3>
<ul>
<li><a href="../index.html">The pytest Website</a></li>
<li><a href="../contributing.html">Contribution Guide</a></li>
<li><a href="https://pypi.python.org/pypi/pytest">pytest @ PyPI</a></li>
<li><a href="https://github.com/pytest-dev/pytest/">pytest @ GitHub</a></li>
<li><a href="http://plugincompat.herokuapp.com/">3rd party plugins</a></li>
<li><a href="https://github.com/pytest-dev/pytest/issues">Issue Tracker</a></li>
<li><a href="http://pytest.org/latest/pytest.pdf">PDF Documentation</a>
</ul>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<input type="text" name="q" />
<input type="submit" value="Go" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
<p class="searchtip" style="font-size: 90%">
Enter search terms or a module, class or function name.
</p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
© Copyright 2015, holger krekel and pytest-dev team.
Created using <a href="http://sphinx.pocoo.org/">Sphinx</a>.
</div>
</body>
</html>
|