add report_header_info to release announce

and remove some ignores/excludes from MANIFEST.in for
a less verbose installation experience

--HG--
branch : trunk
This commit is contained in:
holger krekel 2010-01-18 17:00:22 +01:00
parent d3c0ff3a1f
commit 6756416d69
2 changed files with 17 additions and 16 deletions

View File

@ -8,11 +8,11 @@ graft doc
graft contrib
graft bin
graft testing
exclude *.orig
exclude *.rej
#exclude *.orig
#exclude *.rej
exclude .hginore
exclude *.pyc
recursive-exclude testing *.pyc *.orig *.rej *$py.class
prune .pyc
prune .svn
prune .hg
#exclude *.pyc
#recursive-exclude testing *.pyc *.orig *.rej *$py.class
#prune .pyc
#prune .svn
#prune .hg

View File

@ -14,16 +14,17 @@ py.test 1.2.0 brings many bug fixes and interesting new abilities:
* --genscript=path creates a standalone py.test-equivalent test-script
* --ignore=path prevents collection of anything below that path
* --confcutdir=path only lookup conftest.py test configs below that path
* a new "pytestconfig" function argument gives direct access to option values
* parametrized tests can now be specified per-class as well
* on CPython py.test additionally installs as "py.test-VERSION"
* a 'pytest_report_header' hook to add info to the terminal report header
* a 'pytestconfig' function argument gives direct access to option values
* 'pytest_generate_tests' can now be put into a class as well
* on CPython py.test additionally installs as "py.test-VERSION", on
Jython as py.test-jython and on PyPy as py.test-pypy-XYZ
Apart from many bug fixes 1.2.0 also has better pluginization.
Distributed testing and looponfailing testing have been moved
out into its own "pytest-xdist" plugin which can be installed separately.
The same is true for "pytest-figleaf" for doing coverage reporting.
Those can also serve well now as blue prints for doing your own.
separately released plugins.
Apart from many bug fixes 1.2.0 also has better pluginization:
Distributed testing and looponfailing testing now live in the
separately installable 'pytest-xdist' plugin. The same is true for
'pytest-figleaf' for doing coverage reporting. Those two plugins
can serve well now as blue prints for doing your own.
thanks to all who helped and gave feedback,
have fun,