4 new commits in pytest:
https://bitbucket.org/pytest-dev/pytest/commits/5d3bd2512a06/
Changeset: 5d3bd2512a06
Branch: pytest-2.7
User: flub
Date: 2015-04-30 21:54:43+00:00
Summary: Prepare docs for bugfix release
Affected #: 2 files
diff -r 219483189eb71cca40376c15fb6ffebd492a3d12 -r
5d3bd2512a06a725a2067de19c2cf4f9402b8b4b doc/en/announce/index.txt
--- a/doc/en/announce/index.txt
+++ b/doc/en/announce/index.txt
@@ -5,6 +5,8 @@
.. toctree::
:maxdepth: 2
+ release-2.7.1
+ release-2.7.0
release-2.6.3
release-2.6.2
release-2.6.1
diff -r 219483189eb71cca40376c15fb6ffebd492a3d12 -r
5d3bd2512a06a725a2067de19c2cf4f9402b8b4b doc/en/announce/release-2.7.1.txt
--- /dev/null
+++ b/doc/en/announce/release-2.7.1.txt
@@ -0,0 +1,58 @@
+pytest-2.7.1: bug fixes
+=======================
+
+pytest is a mature Python testing tool with more than a 1100 tests
+against itself, passing on many different interpreters and platforms.
+This release is supposed to be drop-in compatible to 2.7.0.
+
+See below for the changes and see docs at:
+
+ http://pytest.org
+
+As usual, you can upgrade from pypi via::
+
+ pip install -U pytest
+
+Thanks to all who contributed to this release, among them:
+
+ Bruno Oliveira
+ Holger Krekel
+ Ionel Maries Cristian
+ Floris Bruynooghe
+
+Happy testing,
+The py.test Development Team
+
+
+2.7.1 (compared to 2.7.0)
+-------------------------
+
+- fix issue731: do not get confused by the braces which may be present
+ and unbalanced in an object's repr while collapsing False
+ explanations. Thanks Carl Meyer for the report and test case.
+
+- fix issue553: properly handling inspect.getsourcelines failures in
+ FixtureLookupError which would lead to to an internal error,
+ obfuscating the original problem. Thanks talljosh for initial
+ diagnose/patch and Bruno Oliveira for final patch.
+
+- fix issue660: properly report scope-mismatch-access errors
+ independently from ordering of fixture arguments. Also
+ avoid the pytest internal traceback which does not provide
+ information to the user. Thanks Holger Krekel.
+
+- streamlined and documented release process. Also all versions
+ (in setup.py and documentation generation) are now read
+ from _pytest/__init__.py. Thanks Holger Krekel.
+
+- fixed docs to remove the notion that yield-fixtures are experimental.
+ They are here to stay :) Thanks Bruno Oliveira.
+
+- Support building wheels by using environment markers for the
+ requirements. Thanks Ionel Maries Cristian.
+
+- fixed regression to 2.6.4 which surfaced e.g. in lost stdout capture printing
+ when tests raised SystemExit. Thanks Holger Krekel.
+
+- reintroduced _pytest fixture of the pytester plugin which is used
+ at least by pytest-xdist.
https://bitbucket.org/pytest-dev/pytest/commits/6ec6b4170c89/
Changeset: 6ec6b4170c89
Branch: pytest-2.7
User: flub
Date: 2015-04-30 21:55:01+00:00
Summary: Some small corrections to release process
Affected #: 1 file
diff -r 5d3bd2512a06a725a2067de19c2cf4f9402b8b4b -r
6ec6b4170c89088862a09a30d1c455502eb089e4 HOWTORELEASE.rst
--- a/HOWTORELEASE.rst
+++ b/HOWTORELEASE.rst
@@ -2,11 +2,11 @@
How to release pytest (draft)
--------------------------------------------
-1. bump version numbers in setup.py and pytest/__init__.py
+1. bump version numbers in pytest/__init__.py (setup.py reads it)
2. check and finalize CHANGELOG
-3. write doc/en/announce/pytest-VERSION.txt and include
+3. write doc/en/announce/release-VERSION.txt and include
it in doc/en/announce/index.txt
4. use devpi for uploading a release tarball to a staging area:
https://bitbucket.org/pytest-dev/pytest/commits/3c21f64ac44a/
Changeset: 3c21f64ac44a
Branch: pytest-2.7
User: flub
Date: 2015-04-30 23:27:04+00:00
Summary: Some more tweaks of how to release
Affected #: 1 file
diff -r 6ec6b4170c89088862a09a30d1c455502eb089e4 -r
3c21f64ac44a43ad2b52211f152fa7f9e87c9de5 HOWTORELEASE.rst
--- a/HOWTORELEASE.rst
+++ b/HOWTORELEASE.rst
@@ -15,7 +15,7 @@
5. run from multiple machines:
- ``devpi use https://devpi.net/USER/dev``
- - ``devpi test pytest-VERSION``
+ - ``devpi test pytest==VERSION``
6. check that tests pass for relevant combinations with
``devpi list pytest``
@@ -25,14 +25,15 @@
which is ok (tox does not support skipping on
per-platform basis yet).
-7. XXX "regen docs" (not easy to do currently as it requires
- a development version of the regendoc tool from ronny)
+7. Regenerate the docs using the toplevel makefile::
+ make docs
-8. go to "doc/en" and upload docs with "make install"
- (the latter requires ssh-login permissions on pytest.org
- because it uses rsync). Note that the "install" target of
- doc/en/Makefile defines where the rsync goes to, typically
- to the "latest" section of pytest.org.
+8. Upload the docs using the toplevel makefile::
+ make upload-docs
+ This requires ssh-login permission on pytest.org because it uses
+ rsync.
+ Note that the "install" target of doc/en/Makefile defines where the
+ rsync goes to, typically to the "latest" section of pytest.org.
9. publish to pypi "devpi push pytest-2.6.2 pypi:NAME" where NAME
is the name of pypi.python.org as configured in your
https://bitbucket.org/pytest-dev/pytest/commits/13b32b864565/
Changeset: 13b32b864565
Branch: pytest-2.7
User: flub
Date: 2015-04-30 23:27:47+00:00
Summary: Use current regendocs location
Affected #: 1 file
diff -r 3c21f64ac44a43ad2b52211f152fa7f9e87c9de5 -r
13b32b864565690c56777a989558772303347e50 requirements-docs.txt
--- a/requirements-docs.txt
+++ b/requirements-docs.txt
@@ -1,2 +1,2 @@
sphinx==1.2.3
-hg+ssh://h...@bitbucket.org/RonnyPfannschmidt/regendoc#egg=regendoc
+hg+ssh://h...@bitbucket.org/pytest-dev/regendoc#egg=regendoc
Repository URL: https://bitbucket.org/pytest-dev/pytest/
--
This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.
_______________________________________________
pytest-commit mailing list
pytest-commit@python.org
https://mail.python.org/mailman/listinfo/pytest-commit
