4 new commits in pytest:
https://bitbucket.org/hpk42/pytest/commits/0cd954097a90/
Changeset: 0cd954097a90
Branch: pdb_doc_update
User: jurko
Date: 2014-02-01 10:07:54
Summary: correct inconsistent comment wording
Once the 'the' article was used before 'first' and once it was not, all within
the same code example.
Affected #: 1 file
diff -r cba8287569b0e19d15436e2310b832b9315d0c84 -r
0cd954097a9098a24d462548d13d25f4e90b9efe doc/en/usage.txt
--- a/doc/en/usage.txt
+++ b/doc/en/usage.txt
@@ -82,7 +82,7 @@
failure situation::
py.test -x --pdb # drop to PDB on first failure, then end test session
- py.test --pdb --maxfail=3 # drop to PDB for the first three failures
+ py.test --pdb --maxfail=3 # drop to PDB for first three failures
Setting a breakpoint / aka ``set_trace()``
https://bitbucket.org/hpk42/pytest/commits/df43c6b73043/
Changeset: df43c6b73043
Branch: pdb_doc_update
User: jurko
Date: 2014-02-01 10:11:42
Summary: make all 'PDB' doc references be recognized as links
Affected #: 1 file
diff -r 0cd954097a9098a24d462548d13d25f4e90b9efe -r
df43c6b730434bf4f6f39f8a02ad4ec43484122e doc/en/usage.txt
--- a/doc/en/usage.txt
+++ b/doc/en/usage.txt
@@ -67,13 +67,13 @@
py.test --tb=short # a shorter traceback format
py.test --tb=line # only one line per failure
-Dropping to PDB (Python Debugger) on failures
-----------------------------------------------
+Dropping to PDB_ (Python Debugger) on failures
+-----------------------------------------------
.. _PDB: http://docs.python.org/library/pdb.html
Python comes with a builtin Python debugger called PDB_. ``pytest``
-allows one to drop into the PDB prompt via a command line option::
+allows one to drop into the PDB_ prompt via a command line option::
py.test --pdb
@@ -98,7 +98,7 @@
.. versionadded: 2.0.0
-In previous versions you could only enter PDB tracing if
+In previous versions you could only enter PDB_ tracing if
you disabled capturing on the command line via ``py.test -s``.
.. _durations:
https://bitbucket.org/hpk42/pytest/commits/636b8ac8b413/
Changeset: 636b8ac8b413
Branch: pdb_doc_update
User: jurko
Date: 2014-02-01 10:19:09
Summary: reword PDB usage documentation
Documented that since pytest 2.4.0 you can use the raw pdb.set_trace() call
directly without the pytest.set_trace() wrapper or explicitly disabling pytest's
output capture using 'py.test -s'.
Clearly stated how pytest (since version 2.0.0.) automatically disables its
output capture when entering an interactive PDB debugger. This avoids confusing
new users because their tests display different output when running with or
without entering an interactive debugger (even if user does nothing in that
interactive debugger session other than exit it and continue with the regular
test execution).
Affected #: 1 file
diff -r df43c6b730434bf4f6f39f8a02ad4ec43484122e -r
636b8ac8b413f3f33f0c49c3f9f5fb03dcbc624d doc/en/usage.txt
--- a/doc/en/usage.txt
+++ b/doc/en/usage.txt
@@ -98,8 +98,24 @@
.. versionadded: 2.0.0
-In previous versions you could only enter PDB_ tracing if
-you disabled capturing on the command line via ``py.test -s``.
+Prior to pytest version 2.0.0 you could only enter PDB_ tracing if you disabled
+capturing on the command line via ``py.test -s``. In later versions, pytest
+automatically disables its output capture when you enter PDB_ tracing:
+
+* Output capture in other tests is not affected.
+* Any prior test output that has already been captured and will be processed as
+ such.
+* Any later output produced within the same test will not be captured and will
+ instead get sent directly to ``sys.stdout``. Note that this holds true even
+ for test output occuring after you exit the interactive PDB_ tracing session
+ and continue with the regular test run.
+
+.. versionadded: 2.4.0
+
+Since pytest version 2.4.0 you can also use the native Python
+``import pdb;pdb.set_trace()`` call to enter PDB_ tracing without having to use
+the ``pytest.set_trace()`` wrapper or explicitly disable pytest's output
+capturing via ``py.test -s``.
.. _durations:
https://bitbucket.org/hpk42/pytest/commits/8d2d44cf0345/
Changeset: 8d2d44cf0345
User: hpk42
Date: 2014-03-06 08:36:42
Summary: Merged in jurko/pytest/pdb_doc_update (pull request #118)
update PDB related pytest docs
Affected #: 1 file
diff -r 3ba7553c51cb0a85333f73be76aeffb9733450a6 -r
8d2d44cf0345a9e4e5992768c50c5918b8dc08cc doc/en/usage.txt
--- a/doc/en/usage.txt
+++ b/doc/en/usage.txt
@@ -67,13 +67,13 @@
py.test --tb=short # a shorter traceback format
py.test --tb=line # only one line per failure
-Dropping to PDB (Python Debugger) on failures
-----------------------------------------------
+Dropping to PDB_ (Python Debugger) on failures
+-----------------------------------------------
.. _PDB: http://docs.python.org/library/pdb.html
Python comes with a builtin Python debugger called PDB_. ``pytest``
-allows one to drop into the PDB prompt via a command line option::
+allows one to drop into the PDB_ prompt via a command line option::
py.test --pdb
@@ -82,7 +82,7 @@
failure situation::
py.test -x --pdb # drop to PDB on first failure, then end test session
- py.test --pdb --maxfail=3 # drop to PDB for the first three failures
+ py.test --pdb --maxfail=3 # drop to PDB for first three failures
Setting a breakpoint / aka ``set_trace()``
@@ -98,8 +98,24 @@
.. versionadded: 2.0.0
-In previous versions you could only enter PDB tracing if
-you disabled capturing on the command line via ``py.test -s``.
+Prior to pytest version 2.0.0 you could only enter PDB_ tracing if you disabled
+capturing on the command line via ``py.test -s``. In later versions, pytest
+automatically disables its output capture when you enter PDB_ tracing:
+
+* Output capture in other tests is not affected.
+* Any prior test output that has already been captured and will be processed as
+ such.
+* Any later output produced within the same test will not be captured and will
+ instead get sent directly to ``sys.stdout``. Note that this holds true even
+ for test output occuring after you exit the interactive PDB_ tracing session
+ and continue with the regular test run.
+
+.. versionadded: 2.4.0
+
+Since pytest version 2.4.0 you can also use the native Python
+``import pdb;pdb.set_trace()`` call to enter PDB_ tracing without having to use
+the ``pytest.set_trace()`` wrapper or explicitly disable pytest's output
+capturing via ``py.test -s``.
.. _durations:
Repository URL: https://bitbucket.org/hpk42/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
