[py-svn] pytest commit ddcf34bc8c80: refine release announcement

[commits-noreply at bitbucket.org]

# HG changeset patch -- Bitbucket.org
# Project pytest
# URL http://bitbucket.org/hpk42/pytest/overview
# User holger krekel <holger at merlinux.eu>
# Date 1290102153 -3600
# Node ID ddcf34bc8c80790e66689a13ae1d23fb8461a4ac
# Parent  c359bd19375e6ce32534799d1981e9a59da627b2
refine release announcement

--- a/doc/Makefile
+++ b/doc/Makefile
@@ -39,8 +39,8 @@ help:
 clean:
 	-rm -rf $(BUILDDIR)/*
 
-install: html
-	rsync -avz _build/html/ code:public_html/pytest
+install: clean html
+	rsync -avz _build/html/ code:www-pytest/2.0.0
 
 html:
 	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html

--- a/doc/conf.py
+++ b/doc/conf.py
@@ -51,7 +51,9 @@ copyright = u'2010, holger krekel et ali
 # The short X.Y version.
 version = '2.0.0'
 # The full version, including alpha/beta/rc tags.
-release = '2.0.0dev0'
+import py, pytest
+assert py.path.local().relto(py.path.local(pytest.__file__).dirpath().dirpath())
+release = pytest.__version__
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

--- a/doc/announce/release-2.0.0.txt
+++ b/doc/announce/release-2.0.0.txt
@@ -1,24 +1,23 @@
-py.test 2.0.0: standalone, features++, implementation++, docs++
+py.test 2.0.0: improved asserts, unittest, reporting, config, docs
 ===========================================================================
 
-XXX PENDING
+Welcome to pytest-2.0.0, a major new release of "py.test", the rapid
+easy Python testing tool.  There are many new features and a lot of
+long-deprecated code is removed, resulting in a much smaller and cleaner
+implementation.  If you had a test suite using non-deprecated
+functionality 2.0.0 is very likely to continue to work for you without
+requiring changes.
 
-Welcome to pytest-2.0.0, rapid and easy testing for and with Python.
-py.test now comes as its own PyPI distribution named ``pytest`` which
-installs the ``py.test`` tool.  It removes most long-deprecated code,
-providing for a much smaller and easier to understand code base.  There
-are also many new features and much improved documentation. See
+Check out the revised the improved documentation and examples:
 
-    http://pytest.org
-
-for details or below for some more information.
+    http://pytest.org/2.0.0/index.html
 
 Thanks to all issue reporters and people asking questions or
 complaining.  Particular thanks to Floris Bruynooghe and Ronny Pfannschmidt
-for their great coding contributions.
+for their great coding contributions and may others for feedback and help.
 
 best,
-holger
+holger krekel
 
 
 New Features
@@ -30,7 +29,7 @@ New Features
 
   or from a python program::
 
-    import pytest ; pytest.main(args, plugins)
+    import pytest ; pytest.main(arglist, pluginlist)
 
   see http://pytest.org/2.0.0/usage.html for details.
 
@@ -48,14 +47,17 @@ New Features
 
   see http://pytest.org/2.0.0/customize.html
 
-- improved standard unittest support.  For example you can now run
-  the tests of an installed 'unittest' package with py.test::
+- improved standard unittest support.  In general py.test should now
+  better run custom TestCases like twisted trial or Django based
+  TestCases.  Also you can now run the tests of an installed
+  'unittest' package with py.test::
 
     py.test --pyargs unittest
 
 - new "-q" option which decreases verbosity and prints a more
   nose/unittest-style "dot" output.
 
+- many more improvements in details
 
 Fixes
 -----------------------
@@ -72,14 +74,24 @@ Fixes
 - fix bug: unittest collected functions now also can have "pytestmark"
   applied at class/module level
 
-Important Note on importing "pytest" versus "py.test"
--------------------------------------------------------
+Notes
+--------------------
 
-The usual way in pre-2.0 times to use py.test in python code was
-to import "py" and then e.g. use "py.test.raises" for the helper.
-This remains valid and is not planned to be deprecated.  However,
-in most examples and internal code you'll find "import pytest"
-and "pytest.raises" used as the recommended default way.
+* The usual way in pre-2.0 times to use py.test in python code was
+  to import "py" and then e.g. use "py.test.raises" for the helper.
+  This remains valid and is not planned to be deprecated.  However,
+  in most examples and internal code you'll find "import pytest"
+  and "pytest.raises" used as the recommended default way.
+
+* pytest now first performs collection of the complete test suite
+  before running any test. This changes for example the semantics of when
+  pytest_collectstart/pytest_collectreport are called.  Some plugins may
+  need upgrading.
+
+* The pytest package consists of a 400 LOC core.py and about 20 builtin plugins,
+  summing up to roughly 5000 LOCs, including docstrings. To be fair, it also
+  uses generic code from the "pylib", and the new "py" package to help
+  with filesystem and introspection/code manipulation.
 
 (Incompatible) Removals
 -----------------------------
@@ -99,7 +111,7 @@ and "pytest.raises" used as the recommen
 
 - py.test.collect.Directory does not exist anymore and it
   is not possible to provide an own "Directory" object.
-  If you have used this and don#t know what to do, get
+  If you have used this and don't know what to do, get
   in contact.  We'll figure someting out.
 
   Note that pytest_collect_directory() is still called but