backport pastebin fix

--HG--
branch : pytest-2.6

.hgtags

@@ -70,3 +70,5 @@ a064ad64d167508a8e9e73766b1a4e6bd10c85db 2.5.0
 60725b17a9d1af4100abb8be3f9f4ddf6262bf34 2.6.0
 88af949b9611494e2c65d528f9e565b00fb7e8ca 2.6.0
 a4f9639702baa3eb4f3b16e162f74f7b69f3f9e1 2.6.1
+a4f25c5e649892b5cc746d21be971e4773478af9 2.6.2
+2967aa416a4f3cdb65fc75073a2a148e1f372742 2.6.3

CHANGELOG

@@ -1,3 +1,53 @@
+2.6.4
+----------
+
+- Improve assertion failure reporting on iterables, by using ndiff and pprint.
+
+- removed outdated japanese docs from source tree.
+
+- docs for "pytest_addhooks" hook.  Thanks Bruno Oliveira.
+
+- updated plugin index docs.  Thanks Bruno Oliveira.
+
+- fix issue557: with "-k" we only allow the old style "-" for negation
+  at the beginning of strings and even that is deprecated.  Use "not" instead.
+  This should allow to pick parametrized tests where "-" appeared in the parameter.
+
+- fix issue604: Escape % character in the assertion message.
+
+- fix issue620: add explanation in the --genscript target about what
+  the binary blob means. Thanks Dinu Gherman.
+
+- fix issue614: fixed pastebin support.
+
+
+2.6.3
+-----------
+
+- fix issue575: xunit-xml was reporting collection errors as failures
+  instead of errors, thanks Oleg Sinyavskiy.
+
+- fix issue582: fix setuptools example, thanks Laszlo Papp and Ronny
+  Pfannschmidt.
+
+- Fix infinite recursion bug when pickling capture.EncodedFile, thanks
+  Uwe Schmitt.
+
+- fix issue589: fix bad interaction with numpy and others when showing
+  exceptions.  Check for precise "maximum recursion depth exceed" exception
+  instead of presuming any RuntimeError is that one (implemented in py
+  dep).  Thanks Charles Cloud for analysing the issue.
+
+- fix conftest related fixture visibility issue: when running with a
+  CWD outside a test package pytest would get fixture discovery wrong.
+  Thanks to Wolfgang Schnerring for figuring out a reproducable example.
+
+- Introduce pytest_enter_pdb hook (needed e.g. by pytest_timeout to cancel the
+  timeout when interactively entering pdb).  Thanks Wolfgang Schnerring.
+
+- check xfail/skip also with non-python function test items. Thanks
+  Floris Bruynooghe.
+
 2.6.2
 -----------
 
@@ -23,6 +73,10 @@
   other builds due to the extra argparse dependency.  Fixes issue566.
   Thanks sontek.
 
+- Implement issue549: user-provided assertion messages now no longer
+  replace the py.test instrospection message but are shown in addition
+  to them.
+
 2.6.1
 -----------------------------------
 
@@ -49,7 +103,7 @@
 - fix issue with detecting conftest files if the arguments contain
   "::" node id specifications (copy pasted from "-v" output)
 
-- fix issue544 by only removing "@NUM" at the end of "::" separated parts 
+- fix issue544 by only removing "@NUM" at the end of "::" separated parts
   and if the part has an ".py" extension
 
 - don't use py.std import helper, rather import things directly.
@@ -62,7 +116,7 @@
 
 - fix issue537: Avoid importing old assertion reinterpretation code by default.
 
-- fix issue364: shorten and enhance tracebacks representation by default.  
+- fix issue364: shorten and enhance tracebacks representation by default.
   The new "--tb=auto" option (default) will only display long tracebacks
   for the first and last entry.  You can get the old behaviour of printing
   all entries as long entries with "--tb=long".  Also short entries by
@@ -88,14 +142,14 @@
 - fix issue473: work around mock putting an unbound method into a class
   dict when double-patching.
 
-- fix issue498: if a fixture finalizer fails, make sure that 
+- fix issue498: if a fixture finalizer fails, make sure that
   the fixture is still invalidated.
 
 - fix issue453: the result of the pytest_assertrepr_compare hook now gets
   it's newlines escaped so that format_exception does not blow up.
 
 - internal new warning system: pytest will now produce warnings when
-  it detects oddities in your test collection or execution.  
+  it detects oddities in your test collection or execution.
   Warnings are ultimately sent to a new pytest_logwarning hook which is
   currently only implemented by the terminal plugin which displays
   warnings in the summary line and shows more details when -rw (report on
@@ -139,7 +193,7 @@
 
 - fix issue492: avoid leak in test_writeorg.  Thanks Marc Abramowitz.
 
-- fix issue493: don't run tests in doc directory with ``python setup.py test`` 
+- fix issue493: don't run tests in doc directory with ``python setup.py test``
   (use tox -e doctesting for that)
 
 - fix issue486: better reporting and handling of early conftest loading failures
@@ -153,8 +207,8 @@
   Groenholm.
 
 - support nose-style ``__test__`` attribute on modules, classes and
-  functions, including unittest-style Classes.  If set to False, the 
-  test will not be collected.  
+  functions, including unittest-style Classes.  If set to False, the
+  test will not be collected.
 
 - fix issue512: show "<notset>" for arguments which might not be set
   in monkeypatch plugin.  Improves output in documentation.
@@ -164,11 +218,11 @@
 -----------------------------------
 
 - fix issue409 -- better interoperate with cx_freeze by not
-  trying to import from collections.abc which causes problems 
+  trying to import from collections.abc which causes problems
   for py27/cx_freeze.  Thanks Wolfgang L. for reporting and tracking it down.
 
 - fixed docs and code to use "pytest" instead of "py.test" almost everywhere.
-  Thanks Jurko Gospodnetic for the complete PR.  
+  Thanks Jurko Gospodnetic for the complete PR.
 
 - fix issue425: mention at end of "py.test -h" that --markers
   and --fixtures work according to specified test path (or current dir)
@@ -179,7 +233,7 @@
 
 - copy, cleanup and integrate py.io capture
   from pylib 1.4.20.dev2 (rev 13d9af95547e)
-  
+
 - address issue416: clarify docs as to conftest.py loading semantics
 
 - fix issue429: comparing byte strings with non-ascii chars in assert
@@ -199,7 +253,7 @@
 
 - Allow parameterized fixtures to specify the ID of the parameters by
   adding an ids argument to pytest.fixture() and pytest.yield_fixture().
-  Thanks Floris Bruynooghe. 
+  Thanks Floris Bruynooghe.
 
 - fix issue404 by always using the binary xml escape in the junitxml
   plugin.  Thanks Ronny Pfannschmidt.

HOWTORELEASE.rst

@@ -25,18 +25,21 @@ How to release pytest (draft)
    which is ok (tox does not support skipping on
    per-platform basis yet).
 
-7. go to "doc/en" and upload docs with "make install"
+7. XXX "regen docs" (not easy to do currently as it requires
+   a development version of the regendoc tool from ronny)
+
+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. publish to pypi "devpi push pytest-2.6.2 pypi:NAME" where NAME 
+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 
    ~/.pypirc file -- it's the same you would use with 
    "setup.py upload -r NAME"
 
-9. send release announcement to mailing lists:
+10. send release announcement to mailing lists:
 
    pytest-dev
    testing-in-python

README.rst

@@ -1,3 +1,7 @@
+.. image:: https://drone.io/bitbucket.org/hpk42/pytest/status.png
+   :target: https://drone.io/bitbucket.org/hpk42/pytest/latest
+.. image:: https://pypip.in/v/pytest/badge.png
+   :target: https://crate.io/packages/pytest/
 
 Documentation: http://pytest.org/latest/
 
@@ -19,8 +23,9 @@ scales to support complex functional testing.  It provides
 - multi-paradigm support: you can use ``pytest`` to run test suites based
   on `unittest <http://pytest.org/latest/unittest.html>`_ (or trial),
   `nose <http://pytest.org/latest/nose.html>`_
-- single-source compatibility to Python2.5 all the way up to Python3.4,
-  PyPy-2.3 and Jython-2.5.1.
+- single-source compatibility from Python2.6 all the way up to
+  Python3.4, PyPy-2.3, (jython-2.5 untested)
+
 
 - many `external plugins <http://pytest.org/latest/plugins.html#installing-external-plugins-searching>`_.
 

_pytest/__init__.py

@@ -1,2 +1,2 @@
 #
-__version__ = '2.6.2'
+__version__ = '2.6.4'

_pytest/assertion/oldinterpret.py

@@ -57,7 +57,7 @@ class View(object):
     def __getattr__(self, attr):
         # attributes not found in the normal hierarchy rooted on View
         # are looked up in the object's real class
-        return getattr(self.__obj__, attr)
+        return getattr(object.__getattribute__(self, '__obj__'), attr)
 
     def __viewkey__(self):
         return self.__obj__.__class__

_pytest/assertion/rewrite.py

@@ -351,6 +351,33 @@ def _saferepr(obj):
 
 from _pytest.assertion.util import format_explanation as _format_explanation # noqa
 
+def _format_assertmsg(obj):
+    """Format the custom assertion message given.
+
+    For strings this simply replaces newlines with '\n~' so that
+    util.format_explanation() will preserve them instead of escaping
+    newlines.  For other objects py.io.saferepr() is used first.
+
+    """
+    # reprlib appears to have a bug which means that if a string
+    # contains a newline it gets escaped, however if an object has a
+    # .__repr__() which contains newlines it does not get escaped.
+    # However in either case we want to preserve the newline.
+    if py.builtin._istext(obj) or py.builtin._isbytes(obj):
+        s = obj
+        is_repr = False
+    else:
+        s = py.io.saferepr(obj)
+        is_repr = True
+    if py.builtin._istext(s):
+        t = py.builtin.text
+    else:
+        t = py.builtin.bytes
+    s = s.replace(t("\n"), t("\n~")).replace(t("%"), t("%%"))
+    if is_repr:
+        s = s.replace(t("\\n"), t("\n~"))
+    return s
+
 def _should_repr_global_name(obj):
     return not hasattr(obj, "__name__") and not py.builtin.callable(obj)
 
@@ -419,6 +446,56 @@ def set_location(node, lineno, col_offset):
 
 
 class AssertionRewriter(ast.NodeVisitor):
+    """Assertion rewriting implementation.
+
+    The main entrypoint is to call .run() with an ast.Module instance,
+    this will then find all the assert statements and re-write them to
+    provide intermediate values and a detailed assertion error.  See
+    http://pybites.blogspot.be/2011/07/behind-scenes-of-pytests-new-assertion.html
+    for an overview of how this works.
+
+    The entry point here is .run() which will iterate over all the
+    statenemts in an ast.Module and for each ast.Assert statement it
+    finds call .visit() with it.  Then .visit_Assert() takes over and
+    is responsible for creating new ast statements to replace the
+    original assert statement: it re-writes the test of an assertion
+    to provide intermediate values and replace it with an if statement
+    which raises an assertion error with a detailed explanation in
+    case the expression is false.
+
+    For this .visit_Assert() uses the visitor pattern to visit all the
+    AST nodes of the ast.Assert.test field, each visit call returning
+    an AST node and the corresponding explanation string.  During this
+    state is kept in several instance attributes:
+
+    :statements: All the AST statements which will replace the assert
+       statement.
+
+    :variables: This is populated by .variable() with each variable
+       used by the statements so that they can all be set to None at
+       the end of the statements.
+
+    :variable_counter: Counter to create new unique variables needed
+       by statements.  Variables are created using .variable() and
+       have the form of "@py_assert0".
+
+    :on_failure: The AST statements which will be executed if the
+       assertion test fails.  This is the code which will construct
+       the failure message and raises the AssertionError.
+
+    :explanation_specifiers: A dict filled by .explanation_param()
+       with %-formatting placeholders and their corresponding
+       expressions to use in the building of an assertion message.
+       This is used by .pop_format_context() to build a message.
+
+    :stack: A stack of the explanation_specifiers dicts maintained by
+       .push_format_context() and .pop_format_context() which allows
+       to build another %-formatted string while already building one.
+
+    This state is reset on every new assert statement visited and used
+    by the other visitors.
+
+    """
 
     def run(self, mod):
         """Find all assert statements in *mod* and rewrite them."""
@@ -500,15 +577,41 @@ class AssertionRewriter(ast.NodeVisitor):
         return ast.Attribute(builtin_name, name, ast.Load())
 
     def explanation_param(self, expr):
+        """Return a new named %-formatting placeholder for expr.
+
+        This creates a %-formatting placeholder for expr in the
+        current formatting context, e.g. ``%(py0)s``.  The placeholder
+        and expr are placed in the current format context so that it
+        can be used on the next call to .pop_format_context().
+
+        """
         specifier = "py" + str(next(self.variable_counter))
         self.explanation_specifiers[specifier] = expr
         return "%(" + specifier + ")s"
 
     def push_format_context(self):
+        """Create a new formatting context.
+
+        The format context is used for when an explanation wants to
+        have a variable value formatted in the assertion message.  In
+        this case the value required can be added using
+        .explanation_param().  Finally .pop_format_context() is used
+        to format a string of %-formatted values as added by
+        .explanation_param().
+
+        """
         self.explanation_specifiers = {}
         self.stack.append(self.explanation_specifiers)
 
     def pop_format_context(self, expl_expr):
+        """Format the %-formatted string with current format context.
+
+        The expl_expr should be an ast.Str instance constructed from
+        the %-placeholders created by .explanation_param().  This will
+        add the required code to format said string to .on_failure and
+        return the ast.Name instance of the formatted string.
+
+        """
         current = self.stack.pop()
         if self.stack:
             self.explanation_specifiers = self.stack[-1]
@@ -526,11 +629,15 @@ class AssertionRewriter(ast.NodeVisitor):
         return res, self.explanation_param(self.display(res))
 
     def visit_Assert(self, assert_):
-        if assert_.msg:
-            # There's already a message. Don't mess with it.
-            return [assert_]
+        """Return the AST statements to replace the ast.Assert instance.
+
+        This re-writes the test of an assertion to provide
+        intermediate values and replace it with an if statement which
+        raises an assertion error with a detailed explanation in case
+        the expression is false.
+
+        """
         self.statements = []
-        self.cond_chain = ()
         self.variables = []
         self.variable_counter = itertools.count()
         self.stack = []
@@ -542,8 +649,13 @@ class AssertionRewriter(ast.NodeVisitor):
         body = self.on_failure
         negation = ast.UnaryOp(ast.Not(), top_condition)
         self.statements.append(ast.If(negation, body, []))
-        explanation = "assert " + explanation
-        template = ast.Str(explanation)
+        if assert_.msg:
+            assertmsg = self.helper('format_assertmsg', assert_.msg)
+            explanation = "\n>assert " + explanation
+        else:
+            assertmsg = ast.Str("")
+            explanation = "assert " + explanation
+        template = ast.BinOp(assertmsg, ast.Add(), ast.Str(explanation))
         msg = self.pop_format_context(template)
         fmt = self.helper("format_explanation", msg)
         err_name = ast.Name("AssertionError", ast.Load())

_pytest/assertion/util.py

@@ -73,7 +73,7 @@ def _split_explanation(explanation):
     raw_lines = (explanation or u('')).split('\n')
     lines = [raw_lines[0]]
     for l in raw_lines[1:]:
-        if l.startswith('{') or l.startswith('}') or l.startswith('~'):
+        if l and l[0] in ['{', '}', '~', '>']:
             lines.append(l)
         else:
             lines[-1] += '\\n' + l
@@ -103,13 +103,14 @@ def _format_lines(lines):
             stackcnt.append(0)
             result.append(u(' +') + u('  ')*(len(stack)-1) + s + line[1:])
         elif line.startswith('}'):
-            assert line.startswith('}')
             stack.pop()
             stackcnt.pop()
             result[stack[-1]] += line[1:]
         else:
-            assert line.startswith('~')
-            result.append(u('  ')*len(stack) + line[1:])
+            assert line[0] in ['~', '>']
+            stack[-1] += 1
+            indent = len(stack) if line.startswith('~') else len(stack) - 1
+            result.append(u('  ')*indent + line[1:])
     assert len(stack) == 1
     return result
 
@@ -134,18 +135,32 @@ def assertrepr_compare(config, op, left, right):
     isdict = lambda x: isinstance(x, dict)
     isset = lambda x: isinstance(x, (set, frozenset))
 
+    def isiterable(obj):
+        try:
+            iter(obj)
+            return not istext(obj)
+        except TypeError:
+            return False
+
     verbose = config.getoption('verbose')
     explanation = None
     try:
         if op == '==':
             if istext(left) and istext(right):
                 explanation = _diff_text(left, right, verbose)
-            elif issequence(left) and issequence(right):
-                explanation = _compare_eq_sequence(left, right, verbose)
-            elif isset(left) and isset(right):
-                explanation = _compare_eq_set(left, right, verbose)
-            elif isdict(left) and isdict(right):
-                explanation = _compare_eq_dict(left, right, verbose)
+            else:
+                if issequence(left) and issequence(right):
+                    explanation = _compare_eq_sequence(left, right, verbose)
+                elif isset(left) and isset(right):
+                    explanation = _compare_eq_set(left, right, verbose)
+                elif isdict(left) and isdict(right):
+                    explanation = _compare_eq_dict(left, right, verbose)
+                if isiterable(left) and isiterable(right):
+                    expl = _compare_eq_iterable(left, right, verbose)
+                    if explanation is not None:
+                        explanation.extend(expl)
+                    else:
+                        explanation = expl
         elif op == 'not in':
             if istext(left) and istext(right):
                 explanation = _notin_text(left, right, verbose)
@@ -202,6 +217,19 @@ def _diff_text(left, right, verbose=False):
     return explanation
 
 
+def _compare_eq_iterable(left, right, verbose=False):
+    if not verbose:
+        return [u('Use -v to get the full diff')]
+    # dynamic import to speedup pytest
+    import difflib
+
+    left = pprint.pformat(left).splitlines()
+    right = pprint.pformat(right).splitlines()
+    explanation = [u('Full diff:')]
+    explanation.extend(line.strip() for line in difflib.ndiff(left, right))
+    return explanation
+
+
 def _compare_eq_sequence(left, right, verbose=False):
     explanation = []
     for i in range(min(len(left), len(right))):

_pytest/capture.py

@@ -238,7 +238,7 @@ class EncodedFile(object):
         self.write(data)
 
     def __getattr__(self, name):
-        return getattr(self.buffer, name)
+        return getattr(object.__getattribute__(self, "buffer"), name)
 
 
 class MultiCapture(object):
@@ -428,6 +428,9 @@ class DontReadFromInput:
     because in automated test runs it is better to crash than
     hang indefinitely.
     """
+
+    encoding = None
+
     def read(self, *args):
         raise IOError("reading from stdin while output is captured")
     readline = read

_pytest/hookspec.py

@@ -262,3 +262,5 @@ def pytest_exception_interact(node, call, report):
     that is not an internal exception like "skip.Exception".
     """
 
+def pytest_enter_pdb():
+    """ called upon pdb.set_trace()"""

_pytest/junitxml.py

@@ -129,10 +129,10 @@ class LogXML(object):
             self.failed += 1
         self._write_captured_output(report)
 
-    def append_collect_failure(self, report):
+    def append_collect_error(self, report):
         #msg = str(report.longrepr.reprtraceback.extraline)
-        self.append(Junit.failure(bin_xml_escape(report.longrepr),
-                                  message="collection failure"))
+        self.append(Junit.error(bin_xml_escape(report.longrepr),
+                                message="collection failure"))
         self.errors += 1
 
     def append_collect_skipped(self, report):
@@ -181,7 +181,7 @@ class LogXML(object):
         if not report.passed:
             self._opentestcase(report)
             if report.failed:
-                self.append_collect_failure(report)
+                self.append_collect_error(report)
             else:
                 self.append_collect_skipped(report)
 

_pytest/main.py

@@ -24,7 +24,7 @@ name_re = re.compile("^[a-zA-Z_]\w*$")
 
 def pytest_addoption(parser):
     parser.addini("norecursedirs", "directory patterns to avoid for recursion",
-        type="args", default=('.*', 'CVS', '_darcs', '{arch}', '*.egg'))
+        type="args", default=['.*', 'CVS', '_darcs', '{arch}', '*.egg'])
     #parser.addini("dirpatterns",
     #    "patterns specifying possible locations of test files",
     #    type="linelist", default=["**/test_*.txt",
@@ -153,13 +153,14 @@ def pytest_ignore_collect(path, config):
         ignore_paths.extend([py.path.local(x) for x in excludeopt])
     return path in ignore_paths
 
-class HookProxy:
+class HookProxy(object):
     def __init__(self, fspath, config):
         self.fspath = fspath
         self.config = config
 
     def __getattr__(self, name):
-        hookmethod = getattr(self.config.hook, name)
+        config = object.__getattribute__(self, "config")
+        hookmethod = getattr(config.hook, name)
 
         def call_matching_hooks(**kwargs):
             plugins = self.config._getmatchingplugins(self.fspath)

_pytest/mark.py

@@ -56,6 +56,11 @@ def pytest_collection_modifyitems(items, config):
     matchexpr = config.option.markexpr
     if not keywordexpr and not matchexpr:
         return
+    # pytest used to allow "-" for negating
+    # but today we just allow "-" at the beginning, use "not" instead
+    # we probably remove "-" alltogether soon
+    if keywordexpr.startswith("-"):
+        keywordexpr = "not " + keywordexpr[1:]
     selectuntil = False
     if keywordexpr[-1:] == ":":
         selectuntil = True
@@ -122,7 +127,6 @@ def matchkeyword(colitem, keywordexpr):
     Additionally, matches on names in the 'extra_keyword_matches' set of
     any item, as well as names directly assigned to test functions.
     """
-    keywordexpr = keywordexpr.replace("-", "not ")
     mapped_names = set()
 
     # Add the names of the current item and any parent items

_pytest/pastebin.py

@@ -1,10 +1,6 @@
 """ submit failure or test session information to a pastebin service. """
 import py, sys
 
-class url:
-    base = "http://bpaste.net"
-    xmlrpc = base + "/xmlrpc/"
-    show = base + "/show/"
 
 def pytest_addoption(parser):
     group = parser.getgroup("terminal reporting")
@@ -27,22 +23,45 @@ def pytest_configure(__multicall__, config):
 
 def pytest_unconfigure(config):
     if hasattr(config, '_pastebinfile'):
+        # get terminal contents and delete file
         config._pastebinfile.seek(0)
         sessionlog = config._pastebinfile.read()
         config._pastebinfile.close()
         del config._pastebinfile
-        proxyid = getproxy().newPaste("python", sessionlog)
-        pastebinurl = "%s%s" % (url.show, proxyid)
-        sys.stderr.write("pastebin session-log: %s\n" % pastebinurl)
+        # undo our patching in the terminal reporter
         tr = config.pluginmanager.getplugin('terminalreporter')
         del tr._tw.__dict__['write']
+        # write summary
+        tr.write_sep("=", "Sending information to Paste Service")
+        pastebinurl = create_new_paste(sessionlog)
+        tr.write_line("pastebin session-log: %s\n" % pastebinurl)
 
-def getproxy():
+def create_new_paste(contents):
+    """
+    Creates a new paste using bpaste.net service.
+
+    :contents: paste contents
+    :returns: url to the pasted contents
+    """
+    import re
     if sys.version_info < (3, 0):
-        from xmlrpclib import ServerProxy
+        from urllib import urlopen, urlencode
     else:
-        from xmlrpc.client import ServerProxy
-    return ServerProxy(url.xmlrpc).pastes
+        from urllib.request import urlopen
+        from urllib.parse import urlencode
+
+    params = {
+        'code': contents,
+        'lexer': 'python3' if sys.version_info[0] == 3 else 'python',
+        'expiry': '1week',
+    }
+    url = 'https://bpaste.net'
+    response = urlopen(url, data=urlencode(params)).read()
+    m = re.search(r'href="/raw/(\w+)"', response)
+    if m:
+        return '%s/show/%s' % (url, m.group(1))
+    else:
+        return 'bad response: ' + response
 
 def pytest_terminal_summary(terminalreporter):
     if terminalreporter.config.option.pastebin != "failed":
@@ -50,9 +69,6 @@ def pytest_terminal_summary(terminalreporter):
     tr = terminalreporter
     if 'failed' in tr.stats:
         terminalreporter.write_sep("=", "Sending information to Paste Service")
-        if tr.config.option.debug:
-            terminalreporter.write_line("xmlrpcurl: %s" %(url.xmlrpc,))
-        serverproxy = getproxy()
         for rep in terminalreporter.stats.get('failed'):
             try:
                 msg = rep.longrepr.reprtraceback.reprentries[-1].reprfileloc
@@ -62,6 +78,5 @@ def pytest_terminal_summary(terminalreporter):
             rep.toterminal(tw)
             s = tw.stringio.getvalue()
             assert len(s)
-            proxyid = serverproxy.newPaste("python", s)
-            pastebinurl = "%s%s" % (url.show, proxyid)
+            pastebinurl = create_new_paste(s)
             tr.write_line("%s --> %s" %(msg, pastebinurl))

_pytest/pdb.py

@@ -42,6 +42,7 @@ class pytestPDB:
             tw = py.io.TerminalWriter()
             tw.line()
             tw.sep(">", "PDB set_trace (IO-capturing turned off)")
+            self._pluginmanager.hook.pytest_enter_pdb()
         pdb.Pdb().set_trace(frame)
 
 

_pytest/python.py

@@ -124,11 +124,11 @@ def pytest_addoption(parser):
     parser.addini("usefixtures", type="args", default=[],
         help="list of default fixtures to be used with this project")
     parser.addini("python_files", type="args",
-        default=('test_*.py', '*_test.py'),
+        default=['test_*.py', '*_test.py'],
         help="glob-style file patterns for Python test module discovery")
-    parser.addini("python_classes", type="args", default=("Test",),
+    parser.addini("python_classes", type="args", default=["Test",],
         help="prefixes for Python test class discovery")
-    parser.addini("python_functions", type="args", default=("test",),
+    parser.addini("python_functions", type="args", default=["test",],
         help="prefixes for Python test function and method discovery")
 
 def pytest_cmdline_main(config):
@@ -1611,10 +1611,15 @@ class FixtureManager:
         except AttributeError:
             pass
         else:
+            # construct the base nodeid which is later used to check
+            # what fixtures are visible for particular tests (as denoted
+            # by their test id)
             if p.basename.startswith("conftest.py"):
-                nodeid = p.dirpath().relto(self.session.fspath)
+                nodeid = self.session.fspath.bestrelpath(p.dirpath())
                 if p.sep != "/":
                     nodeid = nodeid.replace(p.sep, "/")
+                if nodeid == ".":
+                    nodeid = ""
         self.parsefactories(plugin, nodeid)
         self._seenplugins.add(plugin)
 

_pytest/skipping.py

@@ -58,6 +58,7 @@ class MarkEvaluator:
     @property
     def holder(self):
         return self.item.keywords.get(self.name, None)
+
     def __bool__(self):
         return bool(self.holder)
     __nonzero__ = __bool__
@@ -136,8 +137,6 @@ class MarkEvaluator:
 
 @pytest.mark.tryfirst
 def pytest_runtest_setup(item):
-    if not isinstance(item, pytest.Function):
-        return
     evalskip = MarkEvaluator(item, 'skipif')
     if evalskip.istrue():
         pytest.skip(evalskip.getexplanation())
@@ -155,8 +154,6 @@ def check_xfail_no_run(item):
                 pytest.xfail("[NOTRUN] " + evalxfail.getexplanation())
 
 def pytest_runtest_makereport(__multicall__, item, call):
-    if not isinstance(item, pytest.Function):
-        return
     # unitttest special case, see setting of _unexpectedsuccess
     if hasattr(item, '_unexpectedsuccess'):
         rep = __multicall__.execute()

_pytest/standalonetemplate.py

@@ -1,5 +1,24 @@
 #! /usr/bin/env python
 
+# Hi There!
+# You may be wondering what this giant blob of binary data here is, you might
+# even be worried that we're up to something nefarious (good for you for being
+# paranoid!). This is a base64 encoding of a zip file, this zip file contains
+# a fully functional basic pytest script.
+#
+# Pytest is a thing that tests packages, pytest itself is a package that some-
+# one might want to install, especially if they're looking to run tests inside
+# some package they want to install. Pytest has a lot of code to collect and
+# execute tests, and other such sort of "tribal knowledge" that has been en-
+# coded in its code base. Because of this we basically include a basic copy
+# of pytest inside this blob. We do this  because it let's you as a maintainer
+# or application developer who wants people who don't deal with python much to
+# easily run tests without installing the complete pytest package.
+#
+# If you're wondering how this is created: you can create it yourself if you
+# have a complete pytest installation by using this command on the command-
+# line: ``py.test --genscript=runtests.py``.
+
 sources = """
 @SOURCES@"""
 

doc/en/announce/index.txt

@@ -5,6 +5,7 @@ Release announcements
 .. toctree::
    :maxdepth: 2
 
+   release-2.6.3
    release-2.6.2
    release-2.6.1
    release-2.6.0

doc/en/announce/release-2.6.3.txt

@@ -0,0 +1,52 @@
+pytest-2.6.3: fixes and little improvements
+===========================================================================
+
+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 drop-in compatible to 2.5.2 and 2.6.X.
+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, among them:
+
+    Floris Bruynooghe
+    Oleg Sinyavskiy
+    Uwe Schmitt
+    Charles Cloud
+    Wolfgang Schnerring
+
+have fun,
+holger krekel
+
+Changes 2.6.3
+======================
+
+- fix issue575: xunit-xml was reporting collection errors as failures
+  instead of errors, thanks Oleg Sinyavskiy.
+
+- fix issue582: fix setuptools example, thanks Laszlo Papp and Ronny
+  Pfannschmidt.
+
+- Fix infinite recursion bug when pickling capture.EncodedFile, thanks
+  Uwe Schmitt.
+
+- fix issue589: fix bad interaction with numpy and others when showing
+  exceptions.  Check for precise "maximum recursion depth exceed" exception
+  instead of presuming any RuntimeError is that one (implemented in py
+  dep).  Thanks Charles Cloud for analysing the issue.
+
+- fix conftest related fixture visibility issue: when running with a
+  CWD outside a test package pytest would get fixture discovery wrong.
+  Thanks to Wolfgang Schnerring for figuring out a reproducable example.
+
+- Introduce pytest_enter_pdb hook (needed e.g. by pytest_timeout to cancel the
+  timeout when interactively entering pdb).  Thanks Wolfgang Schnerring.
+
+- check xfail/skip also with non-python function test items. Thanks
+  Floris Bruynooghe.
+

doc/en/assert.txt

@@ -26,7 +26,7 @@ you will see the return value of the function call::
 
     $ py.test test_assert1.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_assert1.py F
@@ -66,20 +66,23 @@ In order to write assertions about raised exceptions, you can use
 ``pytest.raises`` as a context manager like this::
 
     import pytest
-    with pytest.raises(ZeroDivisionError):
-        1 / 0
+
+    def test_zero_division():
+        with pytest.raises(ZeroDivisionError):
+            1 / 0
 
 and if you need to have access to the actual exception info you may use::
 
-    with pytest.raises(RuntimeError) as excinfo:
-        def f():
+    def test_recursion_depth():
+        with pytest.raises(RuntimeError) as excinfo:
+            def f():
+                f()
             f()
-        f()
-
-    # do checks related to excinfo.type, excinfo.value, excinfo.traceback
+        assert 'maximum recursion' in str(excinfo.value)
 
 ``excinfo`` is a `py.code.ExceptionInfo`_ instance, which is a wrapper around
-the actual exception raised.
+the actual exception raised.  The main attributes of interest are
+``.type``, ``.value`` and ``.traceback``.
 
 .. _py.code.ExceptionInfo:
     http://pylib.readthedocs.org/en/latest/code.html#py-code-exceptioninfo
@@ -132,7 +135,7 @@ if you run this module::
 
     $ py.test test_assert2.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_assert2.py F
@@ -149,6 +152,7 @@ if you run this module::
     E         '1'
     E         Extra items in the right set:
     E         '5'
+    E         Use -v to get the full diff
     
     test_assert2.py:5: AssertionError
     ========================= 1 failed in 0.01 seconds =========================

doc/en/capture.txt

@@ -64,7 +64,7 @@ of the failing function and hide the other one::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py .F
@@ -78,7 +78,7 @@ of the failing function and hide the other one::
     
     test_module.py:9: AssertionError
     -------------------------- Captured stdout setup ---------------------------
-    setting up <function test_func2 at 0x2b5d6a81c9d8>
+    setting up <function test_func2 at 0x2af94bea1d08>
     ==================== 1 failed, 1 passed in 0.01 seconds ====================
 
 Accessing captured output from a test function

doc/en/conf.py

@@ -18,7 +18,7 @@
 # The full version, including alpha/beta/rc tags.
 # The short X.Y version.
 version = "2.6"
-release = "2.6.2"
+release = "2.6.4"
 
 import sys, os
 

doc/en/doctest.txt

@@ -44,7 +44,7 @@ then you can just invoke ``py.test`` without command line options::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     mymodule.py .

doc/en/example/assertion/failure_demo.py

@@ -211,3 +211,27 @@ class TestMoreErrors:
         finally:
             x = 0
 
+
+class TestCustomAssertMsg:
+
+    def test_single_line(self):
+        class A:
+            a = 1
+        b = 2
+        assert A.a == b, "A.a appears not to be b"
+
+    def test_multiline(self):
+        class A:
+            a = 1
+        b = 2
+        assert A.a == b, "A.a appears not to be b\n" \
+            "or does not appear to be b\none of those"
+
+    def test_custom_repr(self):
+        class JSON:
+            a = 1
+            def __repr__(self):
+                return "This is JSON\n{\n  'foo': 'bar'\n}"
+        a = JSON()
+        b = 2
+        assert a.a == b, a

doc/en/example/assertion/test_failures.py

@@ -9,6 +9,6 @@ def test_failure_demo_fails_properly(testdir):
     failure_demo.copy(testdir.tmpdir.join(failure_demo.basename))
     result = testdir.runpytest(target)
     result.stdout.fnmatch_lines([
-        "*39 failed*"
+        "*42 failed*"
     ])
     assert result.ret != 0

doc/en/example/markers.txt

@@ -31,7 +31,7 @@ You can then restrict a test run to only run tests marked with ``webtest``::
 
     $ py.test -v -m webtest
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::test_send_http PASSED
@@ -43,7 +43,7 @@ Or the inverse, running all tests except the webtest ones::
 
     $ py.test -v -m "not webtest"
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::test_something_quick PASSED
@@ -62,7 +62,7 @@ tests based on their module, class, method, or function name::
 
     $ py.test -v test_server.py::TestClass::test_method
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 5 items
     
     test_server.py::TestClass::test_method PASSED
@@ -73,7 +73,7 @@ You can also select on the class::
 
     $ py.test -v test_server.py::TestClass
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::TestClass::test_method PASSED
@@ -84,7 +84,7 @@ Or select multiple nodes::
 
   $ py.test -v test_server.py::TestClass test_server.py::test_send_http
   =========================== test session starts ============================
-  platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+  platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
   collecting ... collected 8 items
   
   test_server.py::TestClass::test_method PASSED
@@ -120,7 +120,7 @@ select tests based on their names::
 
     $ py.test -v -k http  # running with the above defined example module
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::test_send_http PASSED
@@ -132,7 +132,7 @@ And you can also run all tests except the ones that match the keyword::
 
     $ py.test -k "not send_http" -v
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::test_something_quick PASSED
@@ -146,7 +146,7 @@ Or to select "http" and "quick" tests::
 
     $ py.test -k "http or quick" -v
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 4 items
     
     test_server.py::test_send_http PASSED
@@ -326,7 +326,7 @@ the test needs::
 
     $ py.test -E stage2
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_someenv.py s
@@ -337,7 +337,7 @@ and here is one that specifies exactly the environment needed::
 
     $ py.test -E stage1
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_someenv.py .
@@ -455,12 +455,12 @@ then you will see two test skipped and two executed tests as expected::
 
     $ py.test -rs # this option reports skip reasons
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 4 items
     
     test_plat.py sss.
     ========================= short test summary info ==========================
-    SKIP [3] /tmp/doc-exec-238/conftest.py:12: cannot run on platform linux
+    SKIP [3] /tmp/doc-exec-68/conftest.py:12: cannot run on platform linux
     
     =================== 1 passed, 3 skipped in 0.01 seconds ====================
 
@@ -468,7 +468,7 @@ Note that if you specify a platform via the marker-command line option like this
 
     $ py.test -m linux2
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 4 items
     
     test_plat.py s
@@ -519,7 +519,7 @@ We can now use the ``-m option`` to select one set::
 
   $ py.test -m interface --tb=short
   =========================== test session starts ============================
-  platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+  platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
   collected 4 items
   
   test_module.py FF
@@ -540,7 +540,7 @@ or to select both "event" and "interface" tests::
 
   $ py.test -m "interface or event" --tb=short
   =========================== test session starts ============================
-  platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+  platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
   collected 4 items
   
   test_module.py FFF

doc/en/example/nonpython.txt

@@ -27,10 +27,10 @@ now execute the test specification::
 
     nonpython $ py.test test_simple.yml
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
-    test_simple.yml .F
+    test_simple.yml F.
     
     ================================= FAILURES =================================
     ______________________________ usecase: hello ______________________________
@@ -56,11 +56,11 @@ consulted when reporting in ``verbose`` mode::
 
     nonpython $ py.test -v
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 2 items
     
-    test_simple.yml::usecase: ok PASSED
     test_simple.yml::usecase: hello FAILED
+    test_simple.yml::usecase: ok PASSED
     
     ================================= FAILURES =================================
     ______________________________ usecase: hello ______________________________
@@ -74,10 +74,10 @@ interesting to just look at the collection tree::
 
     nonpython $ py.test --collect-only
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     <YamlFile 'test_simple.yml'>
-      <YamlItem 'ok'>
       <YamlItem 'hello'>
+      <YamlItem 'ok'>
     
     =============================  in 0.03 seconds =============================

doc/en/example/parametrize.txt

@@ -106,7 +106,7 @@ this is a fully self-contained example which you can run with::
 
     $ py.test test_scenarios.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 4 items
     
     test_scenarios.py ....
@@ -118,7 +118,7 @@ If you just collect tests you'll also nicely see 'advanced' and 'basic' as varia
 
     $ py.test --collect-only test_scenarios.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 4 items
     <Module 'test_scenarios.py'>
       <Class 'TestSampleWithScenarios'>
@@ -182,7 +182,7 @@ Let's first see how it looks like at collection time::
 
     $ py.test test_backends.py --collect-only
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     <Module 'test_backends.py'>
       <Function 'test_db_initialized[d1]'>
@@ -197,7 +197,7 @@ And then when we run the test::
     ================================= FAILURES =================================
     _________________________ test_db_initialized[d2] __________________________
     
-    db = <conftest.DB2 object at 0x2b83684b5eb8>
+    db = <conftest.DB2 object at 0x2b04d7936be0>
     
         def test_db_initialized(db):
             # a dummy test
@@ -253,7 +253,7 @@ argument sets to use for each test function.  Let's run it::
     ================================= FAILURES =================================
     ________________________ TestClass.test_equals[2-1] ________________________
     
-    self = <test_parametrize.TestClass object at 0x2ae94130e390>, a = 1, b = 2
+    self = <test_parametrize.TestClass object at 0x2af4cdee0da0>, a = 1, b = 2
     
         def test_equals(self, a, b):
     >       assert a == b
@@ -279,12 +279,345 @@ is to be run with different sets of arguments for its three arguments:
 Running it results in some skips if we don't have all the python interpreters installed and otherwise runs all combinations (5 interpreters times 5 interpreters times 3 objects to serialize/deserialize)::
 
    . $ py.test -rs -q multipython.py
-   ssssssssssssssssssssssssssssssssssss......sssssssss......ssssssssssssssssss
-   ========================= short test summary info ==========================
-   SKIP [21] /home/hpk/p/pytest/doc/en/example/multipython.py:22: 'python2.5' not found
-   SKIP [21] /home/hpk/p/pytest/doc/en/example/multipython.py:22: 'python2.8' not found
-   SKIP [21] /home/hpk/p/pytest/doc/en/example/multipython.py:22: 'python2.4' not found
-   12 passed, 63 skipped in 0.65 seconds
+   ..................FFFFFF...
+   ================================= FAILURES =================================
+   ________________ test_basic_objects[python3.4-python2.6-42] ________________
+   
+   python1 = <multipython.Python object at 0x2afc7d8c2828>
+   python2 = <multipython.Python object at 0x2afc7d8c2588>, obj = 42
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p0/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p0/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p0/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.6/pickle.py", line 1370, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.6/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.6/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p0/load.py
+   _______________ test_basic_objects[python3.4-python2.6-obj1] _______________
+   
+   python1 = <multipython.Python object at 0x2afc7d8b8c88>
+   python2 = <multipython.Python object at 0x2afc7d8b8e48>, obj = {}
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p1/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p1/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p1/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.6/pickle.py", line 1370, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.6/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.6/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p1/load.py
+   _______________ test_basic_objects[python3.4-python2.6-obj2] _______________
+   
+   python1 = <multipython.Python object at 0x2afc7d8bf6d8>
+   python2 = <multipython.Python object at 0x2afc7d8bf860>, obj = {1: 3}
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p2/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/bin/python2.6 /tmp/pytest-111/test_basic_objects_python3_4_p2/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p2/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.6/pickle.py", line 1370, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.6/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.6/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p2/load.py
+   ________________ test_basic_objects[python3.4-python2.7-42] ________________
+   
+   python1 = <multipython.Python object at 0x2afc7d8b8710>
+   python2 = <multipython.Python object at 0x2afc7d8b8748>, obj = 42
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p3/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p3/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p3/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.7/pickle.py", line 1378, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.7/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.7/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p3/load.py
+   _______________ test_basic_objects[python3.4-python2.7-obj1] _______________
+   
+   python1 = <multipython.Python object at 0x2afc7d8bfb38>
+   python2 = <multipython.Python object at 0x2afc7d8bf3c8>, obj = {}
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p4/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p4/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p4/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.7/pickle.py", line 1378, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.7/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.7/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p4/load.py
+   _______________ test_basic_objects[python3.4-python2.7-obj2] _______________
+   
+   python1 = <multipython.Python object at 0x2afc7d8b86a0>
+   python2 = <multipython.Python object at 0x2afc7d8c2a90>, obj = {1: 3}
+   
+       @pytest.mark.parametrize("obj", [42, {}, {1:3},])
+       def test_basic_objects(python1, python2, obj):
+           python1.dumps(obj)
+   >       python2.load_and_is_true("obj == %s" % obj)
+   
+   multipython.py:51: 
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   multipython.py:46: in load_and_is_true
+       py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))
+   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
+   
+   cmd = '/home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p5/load.py'
+   
+       def cmdexec(cmd):
+           """ return unicode output of executing 'cmd' in a separate process.
+       
+           raise cmdexec.Error exeception if the command failed.
+           the exception will provide an 'err' attribute containing
+           the error-output from the command.
+           if the subprocess module does not provide a proper encoding/unicode strings
+           sys.getdefaultencoding() will be used, if that does not exist, 'UTF-8'.
+           """
+           process = subprocess.Popen(cmd, shell=True,
+                   universal_newlines=True,
+                   stdout=subprocess.PIPE, stderr=subprocess.PIPE)
+           out, err = process.communicate()
+           if sys.version_info[0] < 3: # on py3 we get unicode strings, on py2 not
+               try:
+                   default_encoding = sys.getdefaultencoding() # jython may not have it
+               except AttributeError:
+                   default_encoding = sys.stdout.encoding or 'UTF-8'
+               out = unicode(out, process.stdout.encoding or default_encoding)
+               err = unicode(err, process.stderr.encoding or default_encoding)
+           status = process.poll()
+           if status:
+   >           raise ExecutionFailed(status, status, cmd, out, err)
+   E           py.process.cmdexec.Error: ExecutionFailed: 1  /home/hpk/venv/0/bin/python2.7 /tmp/pytest-111/test_basic_objects_python3_4_p5/load.py
+   E           Traceback (most recent call last):
+   E             File "/tmp/pytest-111/test_basic_objects_python3_4_p5/load.py", line 4, in <module>
+   E               obj = pickle.load(f)
+   E             File "/usr/lib/python2.7/pickle.py", line 1378, in load
+   E               return Unpickler(file).load()
+   E             File "/usr/lib/python2.7/pickle.py", line 858, in load
+   E               dispatch[key](self)
+   E             File "/usr/lib/python2.7/pickle.py", line 886, in load_proto
+   E               raise ValueError, "unsupported pickle protocol: %d" % proto
+   E           ValueError: unsupported pickle protocol: 3
+   
+   ../../../.tox/regen/lib/python3.4/site-packages/py/_process/cmdexec.py:28: Error
+   --------------------------- Captured stdout call ---------------------------
+   /tmp/pytest-111/test_basic_objects_python3_4_p5/load.py
+   6 failed, 21 passed in 1.66 seconds
 
 Indirect parametrization of optional implementations/imports
 --------------------------------------------------------------------
@@ -331,12 +664,12 @@ If you run this with reporting for skips enabled::
 
     $ py.test -rs test_module.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py .s
     ========================= short test summary info ==========================
-    SKIP [1] /tmp/doc-exec-240/conftest.py:10: could not import 'opt2'
+    SKIP [1] /tmp/doc-exec-70/conftest.py:10: could not import 'opt2'
     
     =================== 1 passed, 1 skipped in 0.01 seconds ====================
 

doc/en/example/pythoncollection.txt

@@ -43,7 +43,7 @@ then the test collection looks like this::
 
     $ py.test --collect-only
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     <Module 'check_myapp.py'>
       <Class 'CheckMyApp'>
@@ -88,7 +88,7 @@ You can always peek at the collection tree without running tests like this::
 
     . $ py.test --collect-only pythoncollection.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 3 items
     <Module 'pythoncollection.py'>
       <Function 'test_function'>
@@ -141,10 +141,10 @@ interpreters and will leave out the setup.py file::
 
     $ py.test --collect-only
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 0 items
     
-    =============================  in 0.01 seconds =============================
+    =============================  in 0.00 seconds =============================
 
 If you run with a Python3 interpreter the moduled added through the conftest.py file will not be considered for test collection.
 

doc/en/example/reportingdemo.txt

@@ -13,10 +13,10 @@ get on the terminal - we are working on that):
 
     assertion $ py.test failure_demo.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
-    collected 39 items
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
+    collected 42 items
     
-    failure_demo.py FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
+    failure_demo.py FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
     
     ================================= FAILURES =================================
     ____________________________ test_generative[0] ____________________________
@@ -30,7 +30,7 @@ get on the terminal - we are working on that):
     failure_demo.py:15: AssertionError
     _________________________ TestFailing.test_simple __________________________
     
-    self = <failure_demo.TestFailing object at 0x2aec3e52d470>
+    self = <failure_demo.TestFailing object at 0x2b4436e4d390>
     
         def test_simple(self):
             def f():
@@ -40,13 +40,13 @@ get on the terminal - we are working on that):
         
     >       assert f() == g()
     E       assert 42 == 43
-    E        +  where 42 = <function TestFailing.test_simple.<locals>.f at 0x2aec3e47b158>()
-    E        +  and   43 = <function TestFailing.test_simple.<locals>.g at 0x2aec3e47b268>()
+    E        +  where 42 = <function TestFailing.test_simple.<locals>.f at 0x2b4436f1e6a8>()
+    E        +  and   43 = <function TestFailing.test_simple.<locals>.g at 0x2b4436f1e7b8>()
     
     failure_demo.py:28: AssertionError
     ____________________ TestFailing.test_simple_multiline _____________________
     
-    self = <failure_demo.TestFailing object at 0x2aec3e474ac8>
+    self = <failure_demo.TestFailing object at 0x2b4436f167b8>
     
         def test_simple_multiline(self):
             otherfunc_multi(
@@ -66,19 +66,19 @@ get on the terminal - we are working on that):
     failure_demo.py:11: AssertionError
     ___________________________ TestFailing.test_not ___________________________
     
-    self = <failure_demo.TestFailing object at 0x2aec3e5156a0>
+    self = <failure_demo.TestFailing object at 0x2b4436f12668>
     
         def test_not(self):
             def f():
                 return 42
     >       assert not f()
     E       assert not 42
-    E        +  where 42 = <function TestFailing.test_not.<locals>.f at 0x2aec3e47e620>()
+    E        +  where 42 = <function TestFailing.test_not.<locals>.f at 0x2b4436f1ebf8>()
     
     failure_demo.py:38: AssertionError
     _________________ TestSpecialisedExplanations.test_eq_text _________________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e50cba8>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436efaba8>
     
         def test_eq_text(self):
     >       assert 'spam' == 'eggs'
@@ -89,7 +89,7 @@ get on the terminal - we are working on that):
     failure_demo.py:42: AssertionError
     _____________ TestSpecialisedExplanations.test_eq_similar_text _____________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4e24e0>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ee02e8>
     
         def test_eq_similar_text(self):
     >       assert 'foo 1 bar' == 'foo 2 bar'
@@ -102,7 +102,7 @@ get on the terminal - we are working on that):
     failure_demo.py:45: AssertionError
     ____________ TestSpecialisedExplanations.test_eq_multiline_text ____________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4cc6d8>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ed5e48>
     
         def test_eq_multiline_text(self):
     >       assert 'foo\nspam\nbar' == 'foo\neggs\nbar'
@@ -115,7 +115,7 @@ get on the terminal - we are working on that):
     failure_demo.py:48: AssertionError
     ______________ TestSpecialisedExplanations.test_eq_long_text _______________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e501908>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ed2240>
     
         def test_eq_long_text(self):
             a = '1'*100 + 'a' + '2'*100
@@ -132,7 +132,7 @@ get on the terminal - we are working on that):
     failure_demo.py:53: AssertionError
     _________ TestSpecialisedExplanations.test_eq_long_text_multiline __________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e3af048>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436f18780>
     
         def test_eq_long_text_multiline(self):
             a = '1\n'*100 + 'a' + '2\n'*100
@@ -156,17 +156,18 @@ get on the terminal - we are working on that):
     failure_demo.py:58: AssertionError
     _________________ TestSpecialisedExplanations.test_eq_list _________________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e474c50>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436e42b00>
     
         def test_eq_list(self):
     >       assert [0, 1, 2] == [0, 1, 3]
     E       assert [0, 1, 2] == [0, 1, 3]
     E         At index 2 diff: 2 != 3
+    E         Use -v to get the full diff
     
     failure_demo.py:61: AssertionError
     ______________ TestSpecialisedExplanations.test_eq_list_long _______________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e515dd8>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436f164e0>
     
         def test_eq_list_long(self):
             a = [0]*100 + [1] + [3]*100
@@ -174,11 +175,12 @@ get on the terminal - we are working on that):
     >       assert a == b
     E       assert [0, 0, 0, 0, 0, 0, ...] == [0, 0, 0, 0, 0, 0, ...]
     E         At index 100 diff: 1 != 2
+    E         Use -v to get the full diff
     
     failure_demo.py:66: AssertionError
     _________________ TestSpecialisedExplanations.test_eq_dict _________________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4a5ef0>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436f12c50>
     
         def test_eq_dict(self):
     >       assert {'a': 0, 'b': 1, 'c': 0} == {'a': 0, 'b': 2, 'd': 0}
@@ -190,11 +192,12 @@ get on the terminal - we are working on that):
     E         {'c': 0}
     E         Right contains more items:
     E         {'d': 0}
+    E         Use -v to get the full diff
     
     failure_demo.py:69: AssertionError
     _________________ TestSpecialisedExplanations.test_eq_set __________________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4a2e48>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ec1208>
     
         def test_eq_set(self):
     >       assert set([0, 10, 11, 12]) == set([0, 20, 21])
@@ -206,21 +209,23 @@ get on the terminal - we are working on that):
     E         Extra items in the right set:
     E         20
     E         21
+    E         Use -v to get the full diff
     
     failure_demo.py:72: AssertionError
     _____________ TestSpecialisedExplanations.test_eq_longer_list ______________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4e0c50>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436efab70>
     
         def test_eq_longer_list(self):
     >       assert [1,2] == [1,2,3]
     E       assert [1, 2] == [1, 2, 3]
     E         Right contains more items, first extra item: 3
+    E         Use -v to get the full diff
     
     failure_demo.py:75: AssertionError
     _________________ TestSpecialisedExplanations.test_in_list _________________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4950f0>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436d73278>
     
         def test_in_list(self):
     >       assert 1 in [0, 2, 3, 4, 5]
@@ -229,7 +234,7 @@ get on the terminal - we are working on that):
     failure_demo.py:78: AssertionError
     __________ TestSpecialisedExplanations.test_not_in_text_multiline __________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e474f98>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ebfac8>
     
         def test_not_in_text_multiline(self):
             text = 'some multiline\ntext\nwhich\nincludes foo\nand a\ntail'
@@ -247,7 +252,7 @@ get on the terminal - we are working on that):
     failure_demo.py:82: AssertionError
     ___________ TestSpecialisedExplanations.test_not_in_text_single ____________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e5333c8>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ee0898>
     
         def test_not_in_text_single(self):
             text = 'single foo line'
@@ -260,7 +265,7 @@ get on the terminal - we are working on that):
     failure_demo.py:86: AssertionError
     _________ TestSpecialisedExplanations.test_not_in_text_single_long _________
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e4ccb70>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436ed5748>
     
         def test_not_in_text_single_long(self):
             text = 'head ' * 50 + 'foo ' + 'tail ' * 20
@@ -273,7 +278,7 @@ get on the terminal - we are working on that):
     failure_demo.py:90: AssertionError
     ______ TestSpecialisedExplanations.test_not_in_text_single_long_term _______
     
-    self = <failure_demo.TestSpecialisedExplanations object at 0x2aec3e502080>
+    self = <failure_demo.TestSpecialisedExplanations object at 0x2b4436e4db70>
     
         def test_not_in_text_single_long_term(self):
             text = 'head ' * 50 + 'f'*70 + 'tail ' * 20
@@ -292,7 +297,7 @@ get on the terminal - we are working on that):
             i = Foo()
     >       assert i.b == 2
     E       assert 1 == 2
-    E        +  where 1 = <failure_demo.test_attribute.<locals>.Foo object at 0x2aec3e519c18>.b
+    E        +  where 1 = <failure_demo.test_attribute.<locals>.Foo object at 0x2b4436e42ac8>.b
     
     failure_demo.py:101: AssertionError
     _________________________ test_attribute_instance __________________________
@@ -302,8 +307,8 @@ get on the terminal - we are working on that):
                 b = 1
     >       assert Foo().b == 2
     E       assert 1 == 2
-    E        +  where 1 = <failure_demo.test_attribute_instance.<locals>.Foo object at 0x2aec3e52d898>.b
-    E        +    where <failure_demo.test_attribute_instance.<locals>.Foo object at 0x2aec3e52d898> = <class 'failure_demo.test_attribute_instance.<locals>.Foo'>()
+    E        +  where 1 = <failure_demo.test_attribute_instance.<locals>.Foo object at 0x2b4436f185c0>.b
+    E        +    where <failure_demo.test_attribute_instance.<locals>.Foo object at 0x2b4436f185c0> = <class 'failure_demo.test_attribute_instance.<locals>.Foo'>()
     
     failure_demo.py:107: AssertionError
     __________________________ test_attribute_failure __________________________
@@ -319,7 +324,7 @@ get on the terminal - we are working on that):
     failure_demo.py:116: 
     _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
     
-    self = <failure_demo.test_attribute_failure.<locals>.Foo object at 0x2aec3e4e0b38>
+    self = <failure_demo.test_attribute_failure.<locals>.Foo object at 0x2b4436f16a58>
     
         def _get_b(self):
     >       raise Exception('Failed to get attrib')
@@ -335,15 +340,15 @@ get on the terminal - we are working on that):
                 b = 2
     >       assert Foo().b == Bar().b
     E       assert 1 == 2
-    E        +  where 1 = <failure_demo.test_attribute_multiple.<locals>.Foo object at 0x2aec3e4a5748>.b
-    E        +    where <failure_demo.test_attribute_multiple.<locals>.Foo object at 0x2aec3e4a5748> = <class 'failure_demo.test_attribute_multiple.<locals>.Foo'>()
-    E        +  and   2 = <failure_demo.test_attribute_multiple.<locals>.Bar object at 0x2aec3e4a51d0>.b
-    E        +    where <failure_demo.test_attribute_multiple.<locals>.Bar object at 0x2aec3e4a51d0> = <class 'failure_demo.test_attribute_multiple.<locals>.Bar'>()
+    E        +  where 1 = <failure_demo.test_attribute_multiple.<locals>.Foo object at 0x2b4436f12a90>.b
+    E        +    where <failure_demo.test_attribute_multiple.<locals>.Foo object at 0x2b4436f12a90> = <class 'failure_demo.test_attribute_multiple.<locals>.Foo'>()
+    E        +  and   2 = <failure_demo.test_attribute_multiple.<locals>.Bar object at 0x2b4436f12ac8>.b
+    E        +    where <failure_demo.test_attribute_multiple.<locals>.Bar object at 0x2b4436f12ac8> = <class 'failure_demo.test_attribute_multiple.<locals>.Bar'>()
     
     failure_demo.py:124: AssertionError
     __________________________ TestRaises.test_raises __________________________
     
-    self = <failure_demo.TestRaises object at 0x2aec3e4a2d68>
+    self = <failure_demo.TestRaises object at 0x2b4436ec1d68>
     
         def test_raises(self):
             s = 'qwe'
@@ -358,7 +363,7 @@ get on the terminal - we are working on that):
     <0-codegen /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/python.py:1028>:1: ValueError
     ______________________ TestRaises.test_raises_doesnt _______________________
     
-    self = <failure_demo.TestRaises object at 0x2aec3e4e2198>
+    self = <failure_demo.TestRaises object at 0x2b4436ee9860>
     
         def test_raises_doesnt(self):
     >       raises(IOError, "int('3')")
@@ -367,7 +372,7 @@ get on the terminal - we are working on that):
     failure_demo.py:136: Failed
     __________________________ TestRaises.test_raise ___________________________
     
-    self = <failure_demo.TestRaises object at 0x2aec3e5017b8>
+    self = <failure_demo.TestRaises object at 0x2b4436ed5198>
     
         def test_raise(self):
     >       raise ValueError("demo error")
@@ -376,7 +381,7 @@ get on the terminal - we are working on that):
     failure_demo.py:139: ValueError
     ________________________ TestRaises.test_tupleerror ________________________
     
-    self = <failure_demo.TestRaises object at 0x2aec3e533160>
+    self = <failure_demo.TestRaises object at 0x2b4436ebf320>
     
         def test_tupleerror(self):
     >       a,b = [1]
@@ -385,7 +390,7 @@ get on the terminal - we are working on that):
     failure_demo.py:142: ValueError
     ______ TestRaises.test_reinterpret_fails_with_print_for_the_fun_of_it ______
     
-    self = <failure_demo.TestRaises object at 0x2aec3e4cc438>
+    self = <failure_demo.TestRaises object at 0x2b4436f1c6d8>
     
         def test_reinterpret_fails_with_print_for_the_fun_of_it(self):
             l = [1,2,3]
@@ -398,7 +403,7 @@ get on the terminal - we are working on that):
     l is [1, 2, 3]
     ________________________ TestRaises.test_some_error ________________________
     
-    self = <failure_demo.TestRaises object at 0x2aec3e5199e8>
+    self = <failure_demo.TestRaises object at 0x2b4436e6abe0>
     
         def test_some_error(self):
     >       if namenotexi:
@@ -426,7 +431,7 @@ get on the terminal - we are working on that):
     <2-codegen 'abc-123' /home/hpk/p/pytest/doc/en/example/assertion/failure_demo.py:162>:2: AssertionError
     ____________________ TestMoreErrors.test_complex_error _____________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e515cf8>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436ee59e8>
     
         def test_complex_error(self):
             def f():
@@ -450,7 +455,7 @@ get on the terminal - we are working on that):
     failure_demo.py:5: AssertionError
     ___________________ TestMoreErrors.test_z1_unpack_error ____________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e4f7a58>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436f1a940>
     
         def test_z1_unpack_error(self):
             l = []
@@ -460,7 +465,7 @@ get on the terminal - we are working on that):
     failure_demo.py:179: ValueError
     ____________________ TestMoreErrors.test_z2_type_error _____________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e52db38>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436ef1ef0>
     
         def test_z2_type_error(self):
             l = 3
@@ -470,19 +475,19 @@ get on the terminal - we are working on that):
     failure_demo.py:183: TypeError
     ______________________ TestMoreErrors.test_startswith ______________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e538a58>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436f16710>
     
         def test_startswith(self):
             s = "123"
             g = "456"
     >       assert s.startswith(g)
-    E       assert <built-in method startswith of str object at 0x2aec3e501420>('456')
-    E        +  where <built-in method startswith of str object at 0x2aec3e501420> = '123'.startswith
+    E       assert <built-in method startswith of str object at 0x2b4436e42ea0>('456')
+    E        +  where <built-in method startswith of str object at 0x2b4436e42ea0> = '123'.startswith
     
     failure_demo.py:188: AssertionError
     __________________ TestMoreErrors.test_startswith_nested ___________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e4f1b00>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436f18c88>
     
         def test_startswith_nested(self):
             def f():
@@ -490,15 +495,15 @@ get on the terminal - we are working on that):
             def g():
                 return "456"
     >       assert f().startswith(g())
-    E       assert <built-in method startswith of str object at 0x2aec3e501420>('456')
-    E        +  where <built-in method startswith of str object at 0x2aec3e501420> = '123'.startswith
-    E        +    where '123' = <function TestMoreErrors.test_startswith_nested.<locals>.f at 0x2aec3e5572f0>()
-    E        +  and   '456' = <function TestMoreErrors.test_startswith_nested.<locals>.g at 0x2aec3e557268>()
+    E       assert <built-in method startswith of str object at 0x2b4436e42ea0>('456')
+    E        +  where <built-in method startswith of str object at 0x2b4436e42ea0> = '123'.startswith
+    E        +    where '123' = <function TestMoreErrors.test_startswith_nested.<locals>.f at 0x2b4436f1e950>()
+    E        +  and   '456' = <function TestMoreErrors.test_startswith_nested.<locals>.g at 0x2b4436f1e840>()
     
     failure_demo.py:195: AssertionError
     _____________________ TestMoreErrors.test_global_func ______________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e495438>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436eed0f0>
     
         def test_global_func(self):
     >       assert isinstance(globf(42), float)
@@ -508,18 +513,18 @@ get on the terminal - we are working on that):
     failure_demo.py:198: AssertionError
     _______________________ TestMoreErrors.test_instance _______________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e567240>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436e67c50>
     
         def test_instance(self):
             self.x = 6*7
     >       assert self.x != 42
     E       assert 42 != 42
-    E        +  where 42 = <failure_demo.TestMoreErrors object at 0x2aec3e567240>.x
+    E        +  where 42 = <failure_demo.TestMoreErrors object at 0x2b4436e67c50>.x
     
     failure_demo.py:202: AssertionError
     _______________________ TestMoreErrors.test_compare ________________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e502cc0>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436ebf668>
     
         def test_compare(self):
     >       assert globf(10) < 5
@@ -529,7 +534,7 @@ get on the terminal - we are working on that):
     failure_demo.py:205: AssertionError
     _____________________ TestMoreErrors.test_try_finally ______________________
     
-    self = <failure_demo.TestMoreErrors object at 0x2aec3e5197f0>
+    self = <failure_demo.TestMoreErrors object at 0x2b4436edf588>
     
         def test_try_finally(self):
             x = 1
@@ -538,4 +543,55 @@ get on the terminal - we are working on that):
     E           assert 1 == 0
     
     failure_demo.py:210: AssertionError
-    ======================== 39 failed in 0.22 seconds =========================
+    ___________________ TestCustomAssertMsg.test_single_line ___________________
+    
+    self = <failure_demo.TestCustomAssertMsg object at 0x2b4436ed5128>
+    
+        def test_single_line(self):
+            class A:
+                a = 1
+            b = 2
+    >       assert A.a == b, "A.a appears not to be b"
+    E       AssertionError: A.a appears not to be b
+    E       assert 1 == 2
+    E        +  where 1 = <class 'failure_demo.TestCustomAssertMsg.test_single_line.<locals>.A'>.a
+    
+    failure_demo.py:221: AssertionError
+    ____________________ TestCustomAssertMsg.test_multiline ____________________
+    
+    self = <failure_demo.TestCustomAssertMsg object at 0x2b4436e6ad30>
+    
+        def test_multiline(self):
+            class A:
+                a = 1
+            b = 2
+    >       assert A.a == b, "A.a appears not to be b\n" \
+                "or does not appear to be b\none of those"
+    E       AssertionError: A.a appears not to be b
+    E         or does not appear to be b
+    E         one of those
+    E       assert 1 == 2
+    E        +  where 1 = <class 'failure_demo.TestCustomAssertMsg.test_multiline.<locals>.A'>.a
+    
+    failure_demo.py:227: AssertionError
+    ___________________ TestCustomAssertMsg.test_custom_repr ___________________
+    
+    self = <failure_demo.TestCustomAssertMsg object at 0x2b4436ee92b0>
+    
+        def test_custom_repr(self):
+            class JSON:
+                a = 1
+                def __repr__(self):
+                    return "This is JSON\n{\n  'foo': 'bar'\n}"
+            a = JSON()
+            b = 2
+    >       assert a.a == b, a
+    E       AssertionError: This is JSON
+    E         {
+    E           'foo': 'bar'
+    E         }
+    E       assert 1 == 2
+    E        +  where 1 = This is JSON\n{\n  'foo': 'bar'\n}.a
+    
+    failure_demo.py:237: AssertionError
+    ======================== 42 failed in 0.23 seconds =========================

doc/en/example/simple.txt

@@ -63,9 +63,9 @@ And now with supplying a command line option::
     F
     ================================= FAILURES =================================
     _______________________________ test_answer ________________________________
-    
+
     cmdopt = 'type2'
-    
+
         def test_answer(cmdopt):
             if cmdopt == "type1":
                 print ("first")
@@ -73,7 +73,7 @@ And now with supplying a command line option::
                 print ("second")
     >       assert 0 # to see what was printed
     E       assert 0
-    
+
     test_sample.py:6: AssertionError
     --------------------------- Captured stdout call ---------------------------
     second
@@ -108,7 +108,7 @@ directory with the above conftest.py::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 0 items
     
     =============================  in 0.00 seconds =============================
@@ -152,12 +152,12 @@ and when running it will see a skipped "slow" test::
 
     $ py.test -rs    # "-rs" means report details on the little 's'
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py .s
     ========================= short test summary info ==========================
-    SKIP [1] /tmp/doc-exec-243/conftest.py:9: need --runslow option to run
+    SKIP [1] /tmp/doc-exec-73/conftest.py:9: need --runslow option to run
     
     =================== 1 passed, 1 skipped in 0.01 seconds ====================
 
@@ -165,7 +165,7 @@ Or run it including the ``slow`` marked test::
 
     $ py.test --runslow
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py ..
@@ -256,7 +256,7 @@ which will add the string to the test header accordingly::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     project deps: mylib-1.1
     collected 0 items
     
@@ -279,7 +279,7 @@ which will add info only when run with "--v"::
 
     $ py.test -v
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     info1: did you know that ...
     did you?
     collecting ... collected 0 items
@@ -290,7 +290,7 @@ and nothing when run plainly::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 0 items
     
     =============================  in 0.00 seconds =============================
@@ -322,7 +322,7 @@ Now we can profile which test functions execute the slowest::
 
     $ py.test --durations=3
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 3 items
     
     test_some_are_slow.py ...
@@ -383,7 +383,7 @@ If we run this::
 
     $ py.test -rx
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 4 items
     
     test_step.py .Fx.
@@ -391,7 +391,7 @@ If we run this::
     ================================= FAILURES =================================
     ____________________ TestUserHandling.test_modification ____________________
     
-    self = <test_step.TestUserHandling object at 0x2b2ef2a4feb8>
+    self = <test_step.TestUserHandling object at 0x2aad15c6d048>
     
         def test_modification(self):
     >       assert 0
@@ -453,7 +453,7 @@ We can run this::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 7 items
     
     test_step.py .Fx.
@@ -463,17 +463,17 @@ We can run this::
     
     ================================== ERRORS ==================================
     _______________________ ERROR at setup of test_root ________________________
-    file /tmp/doc-exec-243/b/test_error.py, line 1
+    file /tmp/doc-exec-73/b/test_error.py, line 1
       def test_root(db):  # no db here, will error out
             fixture 'db' not found
-            available fixtures: tmpdir, monkeypatch, capsys, capfd, pytestconfig, recwarn
+            available fixtures: monkeypatch, pytestconfig, tmpdir, capfd, capsys, recwarn
             use 'py.test --fixtures [testpath]' for help on them.
     
-    /tmp/doc-exec-243/b/test_error.py:1
+    /tmp/doc-exec-73/b/test_error.py:1
     ================================= FAILURES =================================
     ____________________ TestUserHandling.test_modification ____________________
     
-    self = <test_step.TestUserHandling object at 0x2b63a7aec710>
+    self = <test_step.TestUserHandling object at 0x2b058dc29e10>
     
         def test_modification(self):
     >       assert 0
@@ -482,20 +482,22 @@ We can run this::
     test_step.py:9: AssertionError
     _________________________________ test_a1 __________________________________
     
-    db = <conftest.DB object at 0x2b63a7b04470>
+    db = <conftest.DB object at 0x2b058db494a8>
     
         def test_a1(db):
     >       assert 0, db  # to show value
-    E       AssertionError: <conftest.DB object at 0x2b63a7b04470>
+    E       AssertionError: <conftest.DB object at 0x2b058db494a8>
+    E       assert 0
     
     a/test_db.py:2: AssertionError
     _________________________________ test_a2 __________________________________
     
-    db = <conftest.DB object at 0x2b63a7b04470>
+    db = <conftest.DB object at 0x2b058db494a8>
     
         def test_a2(db):
     >       assert 0, db  # to show value
-    E       AssertionError: <conftest.DB object at 0x2b63a7b04470>
+    E       AssertionError: <conftest.DB object at 0x2b058db494a8>
+    E       assert 0
     
     a/test_db2.py:2: AssertionError
     ========== 3 failed, 2 passed, 1 xfailed, 1 error in 0.03 seconds ==========
@@ -553,7 +555,7 @@ and run them::
 
     $ py.test test_module.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py FF
@@ -561,7 +563,7 @@ and run them::
     ================================= FAILURES =================================
     ________________________________ test_fail1 ________________________________
     
-    tmpdir = local('/tmp/pytest-509/test_fail10')
+    tmpdir = local('/tmp/pytest-112/test_fail10')
     
         def test_fail1(tmpdir):
     >       assert 0
@@ -580,7 +582,7 @@ and run them::
 you will have a "failures" file which contains the failing test ids::
 
     $ cat failures
-    test_module.py::test_fail1 (/tmp/pytest-509/test_fail10)
+    test_module.py::test_fail1 (/tmp/pytest-112/test_fail10)
     test_module.py::test_fail2
 
 Making test result information available in fixtures
@@ -613,10 +615,10 @@ here is a little example implemented via a local plugin::
             # request.node is an "item" because we use the default
             # "function" scope
             if request.node.rep_setup.failed:
-                print "setting up a test failed!", request.node.nodeid
+                print ("setting up a test failed!", request.node.nodeid)
             elif request.node.rep_setup.passed:
                 if request.node.rep_call.failed:
-                    print "executing test failed", request.node.nodeid
+                    print ("executing test failed", request.node.nodeid)
         request.addfinalizer(fin)
 
 
@@ -642,29 +644,41 @@ if you then have failing tests::
 and run it::
 
     $ py.test -s test_module.py
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 513, in getconftestmodules
-        return self._path2confmods[path]
-    KeyError: local('/tmp/doc-exec-243/test_module.py')
+    =========================== test session starts ============================
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
+    collected 3 items
     
-    During handling of the above exception, another exception occurred:
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 537, in importconftest
-        return self._conftestpath2mod[conftestpath]
-    KeyError: local('/tmp/doc-exec-243/conftest.py')
+    test_module.py Esetting up a test failed! test_module.py::test_setup_fails
+    Fexecuting test failed test_module.py::test_call_fails
+    F
     
-    During handling of the above exception, another exception occurred:
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 543, in importconftest
-        mod = conftestpath.pyimport()
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/py/_path/local.py", line 620, in pyimport
-        __import__(modname)
-      File "/tmp/doc-exec-243/conftest.py", line 22
-        print "setting up a test failed!", request.node.nodeid
-                                        ^
-    SyntaxError: invalid syntax
-    ERROR: could not load /tmp/doc-exec-243/conftest.py
+    ================================== ERRORS ==================================
+    ____________________ ERROR at setup of test_setup_fails ____________________
     
+        @pytest.fixture
+        def other():
+    >       assert 0
+    E       assert 0
+    
+    test_module.py:6: AssertionError
+    ================================= FAILURES =================================
+    _____________________________ test_call_fails ______________________________
+    
+    something = None
+    
+        def test_call_fails(something):
+    >       assert 0
+    E       assert 0
+    
+    test_module.py:12: AssertionError
+    ________________________________ test_fail2 ________________________________
+    
+        def test_fail2():
+    >       assert 0
+    E       assert 0
+    
+    test_module.py:15: AssertionError
+    ==================== 2 failed, 1 error in 0.01 seconds =====================
 
 You'll see that the fixture finalizers could use the precise reporting
 information.
@@ -719,3 +733,4 @@ This makes it convenient to execute your tests from within your frozen
 application, using standard ``py.test`` command-line options::
 
     $ ./app_main --pytest --verbose --tb=long --junit-xml=results.xml test-suite/
+    /bin/sh: 1: ./app_main: not found

doc/en/example/special.txt

@@ -1,7 +1,7 @@
 A session-fixture which can look at all collected tests
 ----------------------------------------------------------------
 
-A session-scoped fixture effectively has access to all 
+A session-scoped fixture effectively has access to all
 collected test items.  Here is an example of a fixture
 function which walks all collected tests and looks
 if their test class defines a ``callme`` method and
@@ -13,7 +13,7 @@ calls it::
 
     @pytest.fixture(scope="session", autouse=True)
     def callattr_ahead_of_alltests(request):
-        print "callattr_ahead_of_alltests called"
+        print ("callattr_ahead_of_alltests called")
         seen = set([None])
         session = request.node
         for item in session.items:
@@ -31,55 +31,42 @@ will be called ahead of running any tests::
     class TestHello:
         @classmethod
         def callme(cls):
-            print "callme called!"
+            print ("callme called!")
 
         def test_method1(self):
-            print "test_method1 called"
-        
+            print ("test_method1 called")
+
         def test_method2(self):
-            print "test_method1 called"
+            print ("test_method1 called")
 
     class TestOther:
         @classmethod
         def callme(cls):
-            print "callme other called"
+            print ("callme other called")
         def test_other(self):
-            print "test other"
+            print ("test other")
 
     # works with unittest as well ...
     import unittest
-    
+
     class SomeTest(unittest.TestCase):
         @classmethod
         def callme(self):
-            print "SomeTest callme called"
+            print ("SomeTest callme called")
 
         def test_unit1(self):
-            print "test_unit1 method called"
+            print ("test_unit1 method called")
 
 If you run this without output capturing::
 
-    $ py.test -q -s test_module.py 
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 513, in getconftestmodules
-        return self._path2confmods[path]
-    KeyError: local('/tmp/doc-exec-244/test_module.py')
-    
-    During handling of the above exception, another exception occurred:
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 537, in importconftest
-        return self._conftestpath2mod[conftestpath]
-    KeyError: local('/tmp/doc-exec-244/conftest.py')
-    
-    During handling of the above exception, another exception occurred:
-    Traceback (most recent call last):
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/config.py", line 543, in importconftest
-        mod = conftestpath.pyimport()
-      File "/home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/py/_path/local.py", line 620, in pyimport
-        __import__(modname)
-      File "/tmp/doc-exec-244/conftest.py", line 6
-        print "callattr_ahead_of_alltests called"
-                                                ^
-    SyntaxError: invalid syntax
-    ERROR: could not load /tmp/doc-exec-244/conftest.py
-    
+    $ py.test -q -s test_module.py
+    callattr_ahead_of_alltests called
+    callme called!
+    callme other called
+    SomeTest callme called
+    test_method1 called
+    .test_method1 called
+    .test other
+    .test_unit1 method called
+    .
+    4 passed in 0.04 seconds

doc/en/fixture.txt

@@ -76,7 +76,7 @@ marked ``smtp`` fixture function.  Running the test looks like this::
 
     $ py.test test_smtpsimple.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.2.dev1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_smtpsimple.py F
@@ -84,7 +84,7 @@ marked ``smtp`` fixture function.  Running the test looks like this::
     ================================= FAILURES =================================
     ________________________________ test_ehlo _________________________________
     
-    smtp = <smtplib.SMTP object at 0x2ade77b37e48>
+    smtp = <smtplib.SMTP object at 0x2b88f2d1b0b8>
     
         def test_ehlo(smtp):
             response, msg = smtp.ehlo()
@@ -93,7 +93,7 @@ marked ``smtp`` fixture function.  Running the test looks like this::
     E       TypeError: Type str doesn't support the buffer API
     
     test_smtpsimple.py:11: TypeError
-    ========================= 1 failed in 0.18 seconds =========================
+    ========================= 1 failed in 0.28 seconds =========================
 
 In the failure traceback we see that the test function was called with a
 ``smtp`` argument, the ``smtplib.SMTP()`` instance created by the fixture
@@ -193,7 +193,7 @@ inspect what is going on and can now run the tests::
 
     $ py.test test_module.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.2.dev1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_module.py FF
@@ -201,7 +201,7 @@ inspect what is going on and can now run the tests::
     ================================= FAILURES =================================
     ________________________________ test_ehlo _________________________________
     
-    smtp = <smtplib.SMTP object at 0x2b4b07e38e48>
+    smtp = <smtplib.SMTP object at 0x2b29b71bd8d0>
     
         def test_ehlo(smtp):
             response = smtp.ehlo()
@@ -212,7 +212,7 @@ inspect what is going on and can now run the tests::
     test_module.py:5: TypeError
     ________________________________ test_noop _________________________________
     
-    smtp = <smtplib.SMTP object at 0x2b4b07e38e48>
+    smtp = <smtplib.SMTP object at 0x2b29b71bd8d0>
     
         def test_noop(smtp):
             response = smtp.noop()
@@ -221,7 +221,7 @@ inspect what is going on and can now run the tests::
     E       assert 0
     
     test_module.py:11: AssertionError
-    ========================= 2 failed in 0.18 seconds =========================
+    ========================= 2 failed in 0.28 seconds =========================
 
 You see the two ``assert 0`` failing and more importantly you can also see
 that the same (module-scoped) ``smtp`` object was passed into the two
@@ -269,7 +269,7 @@ Let's execute it::
     $ py.test -s -q --tb=no
     FFteardown smtp
     
-    2 failed in 0.16 seconds
+    2 failed in 0.21 seconds
 
 We see that the ``smtp`` instance is finalized after the two
 tests finished execution.  Note that if we decorated our fixture
@@ -310,7 +310,7 @@ again, nothing much has changed::
 
     $ py.test -s -q --tb=no
     FF
-    2 failed in 0.17 seconds
+    2 failed in 0.19 seconds
 
 Let's quickly create another test module that actually sets the
 server URL in its module namespace::
@@ -331,6 +331,7 @@ Running it::
     test_anothersmtp.py:5: in test_showhelo
         assert 0, smtp.helo()
     E   AssertionError: (250, b'mail.python.org')
+    E   assert 0
 
 voila! The ``smtp`` fixture function picked up our mail server name
 from the module namespace.
@@ -377,7 +378,7 @@ So let's just do another run::
     ================================= FAILURES =================================
     __________________________ test_ehlo[merlinux.eu] __________________________
     
-    smtp = <smtplib.SMTP object at 0x2b824acf3e80>
+    smtp = <smtplib.SMTP object at 0x2b6b796568d0>
     
         def test_ehlo(smtp):
             response = smtp.ehlo()
@@ -388,7 +389,7 @@ So let's just do another run::
     test_module.py:5: TypeError
     __________________________ test_noop[merlinux.eu] __________________________
     
-    smtp = <smtplib.SMTP object at 0x2b824acf3e80>
+    smtp = <smtplib.SMTP object at 0x2b6b796568d0>
     
         def test_noop(smtp):
             response = smtp.noop()
@@ -399,7 +400,7 @@ So let's just do another run::
     test_module.py:11: AssertionError
     ________________________ test_ehlo[mail.python.org] ________________________
     
-    smtp = <smtplib.SMTP object at 0x2b824b19fb38>
+    smtp = <smtplib.SMTP object at 0x2b6b79656780>
     
         def test_ehlo(smtp):
             response = smtp.ehlo()
@@ -409,10 +410,10 @@ So let's just do another run::
     
     test_module.py:5: TypeError
     -------------------------- Captured stdout setup ---------------------------
-    finalizing <smtplib.SMTP object at 0x2b824acf3e80>
+    finalizing <smtplib.SMTP object at 0x2b6b796568d0>
     ________________________ test_noop[mail.python.org] ________________________
     
-    smtp = <smtplib.SMTP object at 0x2b824b19fb38>
+    smtp = <smtplib.SMTP object at 0x2b6b79656780>
     
         def test_noop(smtp):
             response = smtp.noop()
@@ -421,7 +422,7 @@ So let's just do another run::
     E       assert 0
     
     test_module.py:11: AssertionError
-    4 failed in 6.37 seconds
+    4 failed in 7.02 seconds
 
 We see that our two test functions each ran twice, against the different
 ``smtp`` instances.  Note also, that with the ``mail.python.org``
@@ -461,13 +462,13 @@ Here we declare an ``app`` fixture which receives the previously defined
 
     $ py.test -v test_appsetup.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.2.dev1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 2 items
     
     test_appsetup.py::test_smtp_exists[merlinux.eu] PASSED
     test_appsetup.py::test_smtp_exists[mail.python.org] PASSED
     
-    ========================= 2 passed in 6.11 seconds =========================
+    ========================= 2 passed in 6.63 seconds =========================
 
 Due to the parametrization of ``smtp`` the test will run twice with two
 different ``App`` instances and respective smtp servers.  There is no
@@ -525,7 +526,7 @@ Let's run the tests in verbose mode and with looking at the print-output::
 
     $ py.test -v -s test_module.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.2.dev1 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4 -- /home/hpk/p/pytest/.tox/regen/bin/python3.4
     collecting ... collected 8 items
     
     test_module.py::test_0[1]   test0 1

doc/en/getting-started.txt

@@ -27,7 +27,7 @@ Installation options::
 To check your installation has installed the correct version::
 
     $ py.test --version
-    This is pytest version 2.6.1, imported from /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/pytest.py
+    This is pytest version 2.6.4, imported from /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/pytest.py
 
 If you get an error checkout :ref:`installation issues`.
 
@@ -49,19 +49,19 @@ That's it. You can execute the test function now::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
-
+    
     test_sample.py F
-
+    
     ================================= FAILURES =================================
     _______________________________ test_answer ________________________________
-
+    
         def test_answer():
     >       assert func(3) == 5
     E       assert 4 == 5
     E        +  where 4 = func(3)
-
+    
     test_sample.py:5: AssertionError
     ========================= 1 failed in 0.01 seconds =========================
 
@@ -126,14 +126,14 @@ run the module by passing its filename::
     .F
     ================================= FAILURES =================================
     ____________________________ TestClass.test_two ____________________________
-
-    self = <test_class.TestClass object at 0x2ad4b005b710>
-
+    
+    self = <test_class.TestClass object at 0x2b9209071470>
+    
         def test_two(self):
             x = "hello"
     >       assert hasattr(x, 'check')
     E       assert hasattr('hello', 'check')
-
+    
     test_class.py:8: AssertionError
     1 failed, 1 passed in 0.01 seconds
 
@@ -159,18 +159,21 @@ We list the name ``tmpdir`` in the test function signature and
 before performing the test function call.  Let's just run it::
 
     $ py.test -q test_tmpdir.py
-
-    ================================== ERRORS ==================================
-    _____________________ ERROR collecting test_tmpdir.py ______________________
-    /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/python.py:463: in _importtestmodule
-        mod = self.fspath.pyimport(ensuresyspath=True)
-    /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/py/_path/local.py:620: in pyimport
-        __import__(modname)
-    E     File "/tmp/doc-exec-187/test_tmpdir.py", line 2
-    E       print tmpdir
-    E                  ^
-    E   SyntaxError: invalid syntax
-    1 error in 0.03 seconds
+    F
+    ================================= FAILURES =================================
+    _____________________________ test_needsfiles ______________________________
+    
+    tmpdir = local('/tmp/pytest-108/test_needsfiles0')
+    
+        def test_needsfiles(tmpdir):
+            print (tmpdir)
+    >       assert 0
+    E       assert 0
+    
+    test_tmpdir.py:3: AssertionError
+    --------------------------- Captured stdout call ---------------------------
+    /tmp/pytest-108/test_needsfiles0
+    1 failed in 0.02 seconds
 
 Before the test runs, a unique-per-test-invocation temporary directory
 was created.  More info at :ref:`tmpdir handling`.

doc/en/goodpractises.txt

@@ -233,7 +233,7 @@ get started with setuptools integration::
 
         def initialize_options(self):
             TestCommand.initialize_options(self)
-            self.pytest_args = None
+            self.pytest_args = []
 
         def finalize_options(self):
             TestCommand.finalize_options(self)
@@ -276,7 +276,7 @@ Conventions for Python test discovery
 * collection starts from the initial command line arguments
   which may be directories, filenames or test ids.
 * recurse into directories, unless they match :confval:`norecursedirs`
-* ``test_*.py`` or ``*_test.py`` files, imported by their `package name`_.
+* ``test_*.py`` or ``*_test.py`` files, imported by their `test package name`_.
 * ``Test`` prefixed test classes (without an ``__init__`` method)
 * ``test_`` prefixed test functions or methods are test items
 

doc/en/index.txt

@@ -1,11 +1,6 @@
 
 .. _features:
 
-.. note::
-
-   next training: `professional testing with pytest and tox <http://www.python-academy.com/courses/specialtopics/python_course_testing.html>`_, 24-26th November 2014, Freiburg, Germany
-
-
 pytest: helps you write better programs
 =============================================
 

doc/en/links.inc

@@ -18,4 +18,4 @@
 .. _hudson: http://hudson-ci.org/
 .. _jenkins: http://jenkins-ci.org/
 .. _tox: http://testrun.org/tox
-.. _pylib: http://pylib.org
+.. _pylib: http://py.readthedocs.org/en/latest/

doc/en/parametrize.txt

@@ -53,7 +53,7 @@ them in turn::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 3 items
     
     test_expectation.py ..F
@@ -100,7 +100,7 @@ Let's run this::
 
     $ py.test
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 3 items
     
     test_expectation.py ..x
@@ -170,8 +170,8 @@ Let's also run with a stringinput that will lead to a failing test::
     
         def test_valid_string(stringinput):
     >       assert stringinput.isalpha()
-    E       assert <built-in method isalpha of str object at 0x2ab7463a6b58>()
-    E        +  where <built-in method isalpha of str object at 0x2ab7463a6b58> = '!'.isalpha
+    E       assert <built-in method isalpha of str object at 0x2ae3eb376c00>()
+    E        +  where <built-in method isalpha of str object at 0x2ae3eb376c00> = '!'.isalpha
     
     test_strings.py:3: AssertionError
     1 failed in 0.01 seconds
@@ -185,7 +185,7 @@ listlist::
     $ py.test -q -rs test_strings.py
     s
     ========================= short test summary info ==========================
-    SKIP [1] /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/python.py:1139: got empty parameter set, function test_valid_string at /tmp/doc-exec-195/test_strings.py:1
+    SKIP [1] /home/hpk/p/pytest/.tox/regen/lib/python3.4/site-packages/_pytest/python.py:1139: got empty parameter set, function test_valid_string at /tmp/doc-exec-23/test_strings.py:1
     1 skipped in 0.01 seconds
 
 For further examples, you might want to look at :ref:`more

doc/en/plugins.txt

@@ -29,7 +29,7 @@ and content of files::
             # called for running each test in 'a' directory
             print ("setting up", item)
 
-    a/test_in_subdir.py:
+    a/test_sub.py:
         def test_sub():
             pass
 
@@ -384,6 +384,54 @@ reporting or interaction with exceptions:
 .. autofunction:: pytest_keyboard_interrupt
 .. autofunction:: pytest_exception_interact
 
+
+Declaring new hooks
+------------------------
+
+Plugins and ``conftest.py`` files may declare new hooks that can then be
+implemented by other plugins in order to alter behaviour or interact with
+the new plugin:
+
+.. autofunction:: pytest_addhooks
+
+Hooks are usually declared as do-nothing functions that contain only
+documentation describing when the hook will be called and what return values
+are expected.
+
+For an example, see `newhooks.py`_ from :ref:`xdist`.
+
+.. _`newhooks.py`: https://bitbucket.org/hpk42/pytest-xdist/src/52082f70e7dd04b00361091b8af906c60fd6700f/xdist/newhooks.py?at=default
+
+
+Using hooks from 3rd party plugins
+-------------------------------------
+
+Using new hooks from plugins as explained above might be a little tricky
+because the standard `Hook specification and validation`_ mechanism:
+if you depend on a plugin that is not installed,
+validation will fail and the error message will not make much sense to your users.
+
+One approach is to defer the hook implementation to a new plugin instead of
+declaring the hook functions directly in your plugin module, for example::
+
+    # contents of myplugin.py
+
+    class DeferPlugin(object):
+        """Simple plugin to defer pytest-xdist hook functions."""
+
+        def pytest_testnodedown(self, node, error):
+            """standard xdist hook function.
+            """
+
+    def pytest_configure(config):
+        if config.pluginmanager.hasplugin('xdist'):
+            config.pluginmanager.register(DeferPlugin())
+
+
+This has the added benefit of allowing you to conditionally install hooks
+depending on which plugins are installed.
+
+
 Reference of objects involved in hooks
 ===========================================================
 

doc/en/plugins_index/index.txt

@@ -4,7 +4,7 @@ List of Third-Party Plugins
 ===========================
 
 The table below contains a listing of plugins found in PyPI and
-their status when tested using py.test **2.6.2.dev1** and python 2.7 and
+their status when tested using py.test **2.6.4.dev1** and python 2.7 and
 3.3.
 
 A complete listing can also be found at
@@ -12,154 +12,160 @@ A complete listing can also be found at
 status against other py.test releases.
 
 
-========================================================================================== ================================================================================================================= ================================================================================================================= ======================================================================================== =============================================================================================================================================
-                                           Name                                                                                                  Py27                                                                                                              Py34                                                                                                  Repo                                                                                                              Summary                                                                   
-========================================================================================== ================================================================================================================= ================================================================================================================= ======================================================================================== =============================================================================================================================================
-    `pytest-allure-adaptor-1.4.0 <http://pypi.python.org/pypi/pytest-allure-adaptor>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-allure-adaptor-latest?py=py27&pytest=2.6.2.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-allure-adaptor-latest?py=py34&pytest=2.6.2.dev1                  .. image:: github.png                                                                                                     Plugin for py.test to generate allure xml reports                                              
-                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-allure-adaptor-latest?py=py27&pytest=2.6.2.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-allure-adaptor-latest?py=py34&pytest=2.6.2.dev1                    :target: https://github.com/allure-framework/allure-python                                                                                                                                                            
-               `pytest-bdd-2.3.1 <http://pypi.python.org/pypi/pytest-bdd>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bdd-latest?py=py27&pytest=2.6.2.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bdd-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                                                                   BDD for pytest                                                                
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-bdd-latest?py=py27&pytest=2.6.2.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-bdd-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/olegpidsadnyi/pytest-bdd                                                                                                                                                               
-              `pytest-beds-0.0.1 <http://pypi.python.org/pypi/pytest-beds>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-beds-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-beds-latest?py=py34&pytest=2.6.2.dev1                              .. image:: github.png                                                                                              Fixtures for testing Google Appengine (GAE) apps                                               
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-beds-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-beds-latest?py=py34&pytest=2.6.2.dev1                                :target: https://github.com/kaste/pytest-beds                                                                                                                                                                  
-             `pytest-bench-0.3.0 <http://pypi.python.org/pypi/pytest-bench>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bench-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bench-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                                      Benchmark utility that plugs into pytest.                                                  
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-bench-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-bench-latest?py=py34&pytest=2.6.2.dev1                           :target: http://github.com/concordusapps/pytest-bench                                                                                                                                                              
-           `pytest-blockage-0.1 <http://pypi.python.org/pypi/pytest-blockage>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-blockage-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-blockage-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                                                   Disable network requests during a test run.                                                 
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-blockage-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-blockage-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/rob-b/pytest-blockage                                                                                                                                                                
-   `pytest-browsermob-proxy-0.1 <http://pypi.python.org/pypi/pytest-browsermob-proxy>`_      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-browsermob-proxy-latest?py=py27&pytest=2.6.2.dev1      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-browsermob-proxy-latest?py=py34&pytest=2.6.2.dev1                .. image:: github.png                                                                                                            BrowserMob proxy plugin for py.test.                                                     
-                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-browsermob-proxy-latest?py=py27&pytest=2.6.2.dev1        :target: http://pytest-plugs.herokuapp.com/output/pytest-browsermob-proxy-latest?py=py34&pytest=2.6.2.dev1                  :target: https://github.com/davehunt/pytest-browsermob-proxy                                                                                                                                                           
-           `pytest-bugzilla-0.2 <http://pypi.python.org/pypi/pytest-bugzilla>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                                        py.test bugzilla integration plugin                                                     
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py34&pytest=2.6.2.dev1                           :target: http://github.com/nibrahim/pytest_bugzilla                                                                                                                                                               
-              `pytest-cache-1.0 <http://pypi.python.org/pypi/pytest-cache>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py34&pytest=2.6.2.dev1                           .. image:: bitbucket.png                                                                                        pytest plugin with mechanisms for caching across test runs                                          
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py34&pytest=2.6.2.dev1                             :target: http://bitbucket.org/hpk42/pytest-cache/                                                                                                                                                                
-         `pytest-capturelog-0.7 <http://pypi.python.org/pypi/pytest-capturelog>`_               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py34&pytest=2.6.2.dev1                .. image:: bitbucket.png                                                                                                           py.test plugin to capture log messages                                                    
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py34&pytest=2.6.2.dev1                  :target: http://bitbucket.org/memedough/pytest-capturelog/overview                                                                                                                                                        
-       `pytest-codecheckers-0.2 <http://pypi.python.org/pypi/pytest-codecheckers>`_            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py27&pytest=2.6.2.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py34&pytest=2.6.2.dev1              .. image:: bitbucket.png                                                                                               pytest plugin to add source code sanity checks (pep8 and friends)                                      
-                                                                                                  :target: http://pytest-plugs.herokuapp.com/output/pytest-codecheckers-latest?py=py27&pytest=2.6.2.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-codecheckers-latest?py=py34&pytest=2.6.2.dev1                :target: http://bitbucket.org/RonnyPfannschmidt/pytest-codecheckers/                                                                                                                                                       
-           `pytest-config-0.0.10 <http://pypi.python.org/pypi/pytest-config>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-config-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-config-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                         Base configurations and utilities for developing     your Python project test suite with pytest.                       
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-config-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-config-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/buzzfeed/pytest_config                                                                                                                                                                
-    `pytest-contextfixture-0.1.1 <http://pypi.python.org/pypi/pytest-contextfixture>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-contextfixture-latest?py=py27&pytest=2.6.2.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-contextfixture-latest?py=py34&pytest=2.6.2.dev1                    .. image:: github.png                                                                                                      Define pytest fixtures as context managers.                                                 
-                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-contextfixture-latest?py=py27&pytest=2.6.2.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-contextfixture-latest?py=py34&pytest=2.6.2.dev1                      :target: http://github.com/pelme/pytest-contextfixture/                                                                                                                                                             
-        `pytest-couchdbkit-0.5.1 <http://pypi.python.org/pypi/pytest-couchdbkit>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-couchdbkit-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-couchdbkit-latest?py=py34&pytest=2.6.2.dev1                 .. image:: bitbucket.png                                                                                             py.test extension for per-test couchdb databases using couchdbkit                                      
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-couchdbkit-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-couchdbkit-latest?py=py34&pytest=2.6.2.dev1                   :target: http://bitbucket.org/RonnyPfannschmidt/pytest-couchdbkit                                                                                                                                                        
-               `pytest-cov-1.8.0 <http://pypi.python.org/pypi/pytest-cov>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cov-latest?py=py27&pytest=2.6.2.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cov-latest?py=py34&pytest=2.6.2.dev1                             .. image:: github.png                                                  py.test plugin for coverage reporting with support for both centralised and distributed testing, including subprocesses and multiprocessing 
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-cov-latest?py=py27&pytest=2.6.2.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-cov-latest?py=py34&pytest=2.6.2.dev1                               :target: https://github.com/schlamar/pytest-cov                                                                                                                                                                 
-               `pytest-cpp-0.3.0 <http://pypi.python.org/pypi/pytest-cpp>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cpp-latest?py=py27&pytest=2.6.2.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cpp-latest?py=py34&pytest=2.6.2.dev1                            .. image:: github.png                                                                                              Use pytest's runner to discover and execute C++ tests                                            
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-cpp-latest?py=py27&pytest=2.6.2.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-cpp-latest?py=py34&pytest=2.6.2.dev1                              :target: http://github.com/nicoddemus/pytest-cpp                                                                                                                                                                 
-        `pytest-dbfixtures-0.5.1 <http://pypi.python.org/pypi/pytest-dbfixtures>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbfixtures-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbfixtures-latest?py=py34&pytest=2.6.2.dev1                     .. image:: github.png                                                                                                         Databases fixtures plugin for py.test.                                                    
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-dbfixtures-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-dbfixtures-latest?py=py34&pytest=2.6.2.dev1                       :target: https://github.com/ClearcodeHQ/pytest-dbfixtures                                                                                                                                                            
- `pytest-dbus-notification-1.0.1 <http://pypi.python.org/pypi/pytest-dbus-notification>`_    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbus-notification-latest?py=py27&pytest=2.6.2.dev1     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbus-notification-latest?py=py34&pytest=2.6.2.dev1              .. image:: github.png                                                                                                            D-BUS notifications for pytest results.                                                   
-                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-dbus-notification-latest?py=py27&pytest=2.6.2.dev1       :target: http://pytest-plugs.herokuapp.com/output/pytest-dbus-notification-latest?py=py34&pytest=2.6.2.dev1                :target: https://github.com/bmathieu33/pytest-dbus-notification                                                                                                                                                         
-         `pytest-diffeo-0.1.8.dev1 <http://pypi.python.org/pypi/pytest-diffeo>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-diffeo-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-diffeo-latest?py=py34&pytest=2.6.2.dev1                           .. image:: github.png                                                                                                   Common py.test support for Diffeo packages                                                  
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-diffeo-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-diffeo-latest?py=py34&pytest=2.6.2.dev1                             :target: https://github.com/diffeo/pytest-diffeo                                                                                                                                                                 
-            `pytest-django-2.6.2 <http://pypi.python.org/pypi/pytest-django>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-latest?py=py34&pytest=2.6.2.dev1             `http://pytest-django.readthedocs.org/ <http://pytest-django.readthedocs.org/>`_                                                             A Django plugin for py.test.                                                         
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-django-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-django-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                              
-   `pytest-django-haystack-0.1.1 <http://pypi.python.org/pypi/pytest-django-haystack>`_       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-haystack-latest?py=py27&pytest=2.6.2.dev1       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-haystack-latest?py=py34&pytest=2.6.2.dev1                  .. image:: github.png                                                                                                       Cleanup your Haystack indexes between tests                                                 
-                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-django-haystack-latest?py=py27&pytest=2.6.2.dev1         :target: http://pytest-plugs.herokuapp.com/output/pytest-django-haystack-latest?py=py34&pytest=2.6.2.dev1                    :target: http://github.com/rouge8/pytest-django-haystack                                                                                                                                                             
-       `pytest-django-lite-0.1.1 <http://pypi.python.org/pypi/pytest-django-lite>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-lite-latest?py=py27&pytest=2.6.2.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-lite-latest?py=py34&pytest=2.6.2.dev1                     .. image:: github.png                                                                                                  The bare minimum to integrate py.test with Django.                                              
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-django-lite-latest?py=py27&pytest=2.6.2.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-django-lite-latest?py=py34&pytest=2.6.2.dev1                       :target: https://github.com/dcramer/pytest-django-lite                                                                                                                                                              
-               `pytest-echo-1.3 <http://pypi.python.org/pypi/pytest-echo>`_                        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-echo-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-echo-latest?py=py34&pytest=2.6.2.dev1           `http://pypi.python.org/pypi/pytest-echo/ <http://pypi.python.org/pypi/pytest-echo/>`_                     pytest plugin with mechanisms for echoing environment variables, package version and generic attributes                   
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-echo-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-echo-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                               
-         `pytest-eradicate-0.0.2 <http://pypi.python.org/pypi/pytest-eradicate>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py34&pytest=2.6.2.dev1                      .. image:: github.png                                                                                                     pytest plugin to check for commented out code                                                
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py34&pytest=2.6.2.dev1                        :target: https://github.com/spil-johan/pytest-eradicate                                                                                                                                                             
-            `pytest-figleaf-1.0 <http://pypi.python.org/pypi/pytest-figleaf>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py27&pytest=2.6.2.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py34&pytest=2.6.2.dev1                         .. image:: bitbucket.png                                                                                                       py.test figleaf coverage plugin                                                       
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py27&pytest=2.6.2.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py34&pytest=2.6.2.dev1                           :target: http://bitbucket.org/hpk42/pytest-figleaf                                                                                                                                                                
-     `pytest-fixture-tools-1.0.0 <http://pypi.python.org/pypi/pytest-fixture-tools>`_          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py27&pytest=2.6.2.dev1         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py34&pytest=2.6.2.dev1                                                ?                                                                                          Plugin for pytest which provides tools for fixtures                                             
-                                                                                                  :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py27&pytest=2.6.2.dev1           :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                          
-             `pytest-flakes-0.2 <http://pypi.python.org/pypi/pytest-flakes>`_                     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                                                 pytest plugin to check source code with pyflakes                                               
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-flakes-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-flakes-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/fschulze/pytest-flakes                                                                                                                                                                
-          `pytest-greendots-0.3 <http://pypi.python.org/pypi/pytest-greendots>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-greendots-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-greendots-latest?py=py34&pytest=2.6.2.dev1                                                  ?                                                                                                          Green progress dots                                                             
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-greendots-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-greendots-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                            
-              `pytest-growl-0.2 <http://pypi.python.org/pypi/pytest-growl>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-growl-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-growl-latest?py=py34&pytest=2.6.2.dev1                                                    ?                                                                                                Growl notifications for pytest results.                                                   
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-growl-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-growl-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                              
-           `pytest-httpbin-0.0.2 <http://pypi.python.org/pypi/pytest-httpbin>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpbin-latest?py=py27&pytest=2.6.2.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpbin-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                            Easily test your HTTP library against a local copy of httpbin                                        
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-httpbin-latest?py=py27&pytest=2.6.2.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-httpbin-latest?py=py34&pytest=2.6.2.dev1                          :target: https://github.com/kevin1024/pytest-httpbin                                                                                                                                                               
-         `pytest-httpretty-0.2.0 <http://pypi.python.org/pypi/pytest-httpretty>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpretty-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpretty-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                                      A thin wrapper of HTTPretty for pytest                                                    
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-httpretty-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-httpretty-latest?py=py34&pytest=2.6.2.dev1                          :target: http://github.com/papaeye/pytest-httpretty                                                                                                                                                               
-       `pytest-incremental-0.3.0 <http://pypi.python.org/pypi/pytest-incremental>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-incremental-latest?py=py27&pytest=2.6.2.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-incremental-latest?py=py34&pytest=2.6.2.dev1                  .. image:: bitbucket.png                                                                                                      an incremental test runner (pytest plugin)                                                  
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-incremental-latest?py=py27&pytest=2.6.2.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-incremental-latest?py=py34&pytest=2.6.2.dev1                    :target: https://bitbucket.org/schettino72/pytest-incremental                                                                                                                                                          
-         `pytest-instafail-0.2.0 <http://pypi.python.org/pypi/pytest-instafail>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-instafail-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-instafail-latest?py=py34&pytest=2.6.2.dev1                       .. image:: github.png                                                                                                      py.test plugin to show failures instantly                                                  
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-instafail-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-instafail-latest?py=py34&pytest=2.6.2.dev1                         :target: https://github.com/jpvanhal/pytest-instafail                                                                                                                                                              
-         `pytest-ipdb-0.1-prerelease <http://pypi.python.org/pypi/pytest-ipdb>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ipdb-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ipdb-latest?py=py34&pytest=2.6.2.dev1                            .. image:: github.png                                                                                       A py.test plug-in to enable drop to ipdb debugger on test failure.                                      
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-ipdb-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-ipdb-latest?py=py34&pytest=2.6.2.dev1                              :target: https://github.com/mverteuil/pytest-ipdb                                                                                                                                                                
-              `pytest-jira-0.01 <http://pypi.python.org/pypi/pytest-jira>`_                        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-jira-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-jira-latest?py=py34&pytest=2.6.2.dev1                              .. image:: github.png                                                                                               py.test JIRA integration plugin, using markers                                                
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-jira-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-jira-latest?py=py34&pytest=2.6.2.dev1                                :target: http://github.com/jlaska/pytest_jira                                                                                                                                                                  
-             `pytest-knows-0.1.5 <http://pypi.python.org/pypi/pytest-knows>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-knows-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-knows-latest?py=py34&pytest=2.6.2.dev1                               .. image:: github.png                                                                    A pytest plugin that can automaticly skip test case based on dependence info calculated by trace                       
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-knows-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-knows-latest?py=py34&pytest=2.6.2.dev1                                 :target: https://github.com/mapix/ptknows                                                                                                                                                                    
-             `pytest-konira-0.2 <http://pypi.python.org/pypi/pytest-konira>`_                     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-konira-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-konira-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                                          Run Konira DSL tests with py.test                                                      
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-konira-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-konira-latest?py=py34&pytest=2.6.2.dev1                           :target: http://github.com/alfredodeza/pytest-konira                                                                                                                                                               
-       `pytest-localserver-0.3.2 <http://pypi.python.org/pypi/pytest-localserver>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-localserver-latest?py=py27&pytest=2.6.2.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-localserver-latest?py=py34&pytest=2.6.2.dev1                     .. image:: bitbucket.png                                                                                               py.test plugin to test server connections locally.                                              
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-localserver-latest?py=py27&pytest=2.6.2.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-localserver-latest?py=py34&pytest=2.6.2.dev1                       :target: http://bitbucket.org/basti/pytest-localserver/                                                                                                                                                             
-   `pytest-marker-bugzilla-0.06 <http://pypi.python.org/pypi/pytest-marker-bugzilla>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marker-bugzilla-latest?py=py27&pytest=2.6.2.dev1       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marker-bugzilla-latest?py=py34&pytest=2.6.2.dev1                 .. image:: github.png                                                                                                    py.test bugzilla integration plugin, using markers                                              
-                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-marker-bugzilla-latest?py=py27&pytest=2.6.2.dev1         :target: http://pytest-plugs.herokuapp.com/output/pytest-marker-bugzilla-latest?py=py34&pytest=2.6.2.dev1                   :target: http://github.com/eanxgeek/pytest_marker_bugzilla                                                                                                                                                            
-     `pytest-markfiltration-0.8 <http://pypi.python.org/pypi/pytest-markfiltration>`_         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-markfiltration-latest?py=py27&pytest=2.6.2.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-markfiltration-latest?py=py34&pytest=2.6.2.dev1                 .. image:: github.png                                                                                                                           UNKNOWN                                                                   
-                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-markfiltration-latest?py=py27&pytest=2.6.2.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-markfiltration-latest?py=py34&pytest=2.6.2.dev1                   :target: https://github.com/adamgoucher/pytest-markfiltration                                                                                                                                                          
-              `pytest-marks-0.4 <http://pypi.python.org/pypi/pytest-marks>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marks-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marks-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                                                       UNKNOWN                                                                   
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-marks-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-marks-latest?py=py34&pytest=2.6.2.dev1                           :target: https://github.com/adamgoucher/pytest-marks                                                                                                                                                               
-              `pytest-mock-0.3.0 <http://pypi.python.org/pypi/pytest-mock>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mock-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mock-latest?py=py34&pytest=2.6.2.dev1                           .. image:: github.png                                                                                         Thin-wrapper around the mock package for easier use with py.test                                       
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-mock-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-mock-latest?py=py34&pytest=2.6.2.dev1                             :target: https://github.com/nicoddemus/pytest-mock/                                                                                                                                                               
-        `pytest-monkeyplus-1.1.0 <http://pypi.python.org/pypi/pytest-monkeyplus>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-monkeyplus-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-monkeyplus-latest?py=py34&pytest=2.6.2.dev1                      .. image:: bitbucket.png                                                                                            pytest's monkeypatch subclass with extra functionalities                                           
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-monkeyplus-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-monkeyplus-latest?py=py34&pytest=2.6.2.dev1                        :target: http://bitbucket.org/hsoft/pytest-monkeyplus/                                                                                                                                                              
-          `pytest-mozwebqa-1.1.1 <http://pypi.python.org/pypi/pytest-mozwebqa>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mozwebqa-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mozwebqa-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                                          Mozilla WebQA plugin for py.test.                                                      
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-mozwebqa-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-mozwebqa-latest?py=py34&pytest=2.6.2.dev1                          :target: https://github.com/davehunt/pytest-mozwebqa                                                                                                                                                               
-              `pytest-oerp-0.2.0 <http://pypi.python.org/pypi/pytest-oerp>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-oerp-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-oerp-latest?py=py34&pytest=2.6.2.dev1                            .. image:: github.png                                                                                                      pytest plugin to test OpenERP modules                                                    
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-oerp-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-oerp-latest?py=py34&pytest=2.6.2.dev1                              :target: http://github.com/santagada/pytest-oerp/                                                                                                                                                                
-           `pytest-ordering-0.3 <http://pypi.python.org/pypi/pytest-ordering>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ordering-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ordering-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                                pytest plugin to run your tests in a specific order                                             
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-ordering-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-ordering-latest?py=py34&pytest=2.6.2.dev1                           :target: https://github.com/ftobia/pytest-ordering                                                                                                                                                                
-         `pytest-osxnotify-0.1.4 <http://pypi.python.org/pypi/pytest-osxnotify>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-osxnotify-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-osxnotify-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                                      OS X notifications for py.test results.                                                   
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-osxnotify-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-osxnotify-latest?py=py34&pytest=2.6.2.dev1                          :target: https://github.com/dbader/pytest-osxnotify                                                                                                                                                               
-       `pytest-paste-config-0.1 <http://pypi.python.org/pypi/pytest-paste-config>`_            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py27&pytest=2.6.2.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py34&pytest=2.6.2.dev1                                                 ?                                                                                             Allow setting the path to a paste config file                                                
-                                                                                                  :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py27&pytest=2.6.2.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                           
-              `pytest-pep8-1.0.6 <http://pypi.python.org/pypi/pytest-pep8>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py34&pytest=2.6.2.dev1                            .. image:: bitbucket.png                                                                                                 pytest plugin to check PEP8 requirements                                                   
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py34&pytest=2.6.2.dev1                              :target: http://bitbucket.org/hpk42/pytest-pep8/                                                                                                                                                                 
-          `pytest-pipeline-0.1.0 <http://pypi.python.org/pypi/pytest-pipeline>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py34&pytest=2.6.2.dev1                           .. image:: github.png                                                                                        Pytest plugin for functional testing of data analysis pipelines                                       
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py34&pytest=2.6.2.dev1                             :target: https://github.com/bow/pytest_pipeline                                                                                                                                                                 
-                `pytest-poo-0.2 <http://pypi.python.org/pypi/pytest-poo>`_                          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py27&pytest=2.6.2.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py34&pytest=2.6.2.dev1                               .. image:: github.png                                                                                                        Visualize your crappy tests                                                         
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-poo-latest?py=py27&pytest=2.6.2.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-poo-latest?py=py34&pytest=2.6.2.dev1                                 :target: http://github.com/pelme/pytest-poo                                                                                                                                                                   
-           `pytest-pycharm-0.1.0 <http://pypi.python.org/pypi/pytest-pycharm>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pycharm-latest?py=py27&pytest=2.6.2.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pycharm-latest?py=py34&pytest=2.6.2.dev1                         .. image:: github.png                                                                                        Plugin for py.test to enter PyCharm debugger on uncaught exceptions                                     
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-pycharm-latest?py=py27&pytest=2.6.2.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-pycharm-latest?py=py34&pytest=2.6.2.dev1                           :target: https://github.com/jlubcke/pytest-pycharm                                                                                                                                                                
-              `pytest-pydev-0.1 <http://pypi.python.org/pypi/pytest-pydev>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pydev-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pydev-latest?py=py34&pytest=2.6.2.dev1                           .. image:: bitbucket.png                                                                                 py.test plugin to connect to a remote debug server with PyDev or PyCharm.                                  
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-pydev-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-pydev-latest?py=py34&pytest=2.6.2.dev1                             :target: http://bitbucket.org/basti/pytest-pydev/                                                                                                                                                                
-         `pytest-pythonpath-0.3 <http://pypi.python.org/pypi/pytest-pythonpath>`_               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pythonpath-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pythonpath-latest?py=py34&pytest=2.6.2.dev1                      .. image:: github.png                                                                                       pytest plugin for adding to the PYTHONPATH from command line or configs.                                   
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-pythonpath-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-pythonpath-latest?py=py34&pytest=2.6.2.dev1                        :target: https://github.com/bigsassy/pytest-pythonpath                                                                                                                                                              
-                `pytest-qt-1.2.0 <http://pypi.python.org/pypi/pytest-qt>`_                          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-qt-latest?py=py27&pytest=2.6.2.dev1                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-qt-latest?py=py34&pytest=2.6.2.dev1                              .. image:: github.png                                                                                                pytest support for PyQt and PySide applications                                               
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-qt-latest?py=py27&pytest=2.6.2.dev1                      :target: http://pytest-plugs.herokuapp.com/output/pytest-qt-latest?py=py34&pytest=2.6.2.dev1                                :target: http://github.com/nicoddemus/pytest-qt                                                                                                                                                                 
-         `pytest-quickcheck-0.8 <http://pypi.python.org/pypi/pytest-quickcheck>`_               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-quickcheck-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-quickcheck-latest?py=py34&pytest=2.6.2.dev1                       .. image:: bitbucket.png                                                                                         pytest plugin to generate random data inspired by QuickCheck                                         
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-quickcheck-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-quickcheck-latest?py=py34&pytest=2.6.2.dev1                         :target: http://bitbucket.org/t2y/pytest-quickcheck/                                                                                                                                                               
-               `pytest-rage-0.1 <http://pypi.python.org/pypi/pytest-rage>`_                        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rage-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rage-latest?py=py34&pytest=2.6.2.dev1                            .. image:: github.png                                                                                                        pytest plugin to implement PEP712                                                      
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-rage-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-rage-latest?py=py34&pytest=2.6.2.dev1                              :target: http://github.com/santagada/pytest-rage/                                                                                                                                                                
-       `pytest-raisesregexp-1.0 <http://pypi.python.org/pypi/pytest-raisesregexp>`_            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-raisesregexp-latest?py=py27&pytest=2.6.2.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-raisesregexp-latest?py=py34&pytest=2.6.2.dev1                     .. image:: github.png                                                                                                 Simple pytest plugin to look for regex in Exceptions                                             
-                                                                                                  :target: http://pytest-plugs.herokuapp.com/output/pytest-raisesregexp-latest?py=py27&pytest=2.6.2.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-raisesregexp-latest?py=py34&pytest=2.6.2.dev1                       :target: https://github.com/Walkman/pytest_raisesregexp                                                                                                                                                             
-            `pytest-random-0.02 <http://pypi.python.org/pypi/pytest-random>`_                     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-random-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-random-latest?py=py34&pytest=2.6.2.dev1                            .. image:: github.png                                                                                                       py.test plugin to randomize tests                                                      
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-random-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-random-latest?py=py34&pytest=2.6.2.dev1                              :target: https://github.com/klrmn/pytest-random                                                                                                                                                                 
-     `pytest-rerunfailures-0.05 <http://pypi.python.org/pypi/pytest-rerunfailures>`_           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rerunfailures-latest?py=py27&pytest=2.6.2.dev1         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rerunfailures-latest?py=py34&pytest=2.6.2.dev1                    .. image:: github.png                                                                                              py.test plugin to re-run tests to eliminate flakey failures                                         
-                                                                                                  :target: http://pytest-plugs.herokuapp.com/output/pytest-rerunfailures-latest?py=py27&pytest=2.6.2.dev1           :target: http://pytest-plugs.herokuapp.com/output/pytest-rerunfailures-latest?py=py34&pytest=2.6.2.dev1                      :target: https://github.com/klrmn/pytest-rerunfailures                                                                                                                                                              
-          `pytest-runfailed-0.3 <http://pypi.python.org/pypi/pytest-runfailed>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runfailed-latest?py=py27&pytest=2.6.2.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runfailed-latest?py=py34&pytest=2.6.2.dev1                     .. image:: github.png                                                                                                         implement a --failed option for pytest                                                    
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-runfailed-latest?py=py27&pytest=2.6.2.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-runfailed-latest?py=py34&pytest=2.6.2.dev1                       :target: http://github.com/dmerejkowsky/pytest-runfailed                                                                                                                                                             
-             `pytest-runner-2.1 <http://pypi.python.org/pypi/pytest-runner>`_                     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runner-latest?py=py27&pytest=2.6.2.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runner-latest?py=py34&pytest=2.6.2.dev1                          .. image:: bitbucket.png                                                                                                                   UNKNOWN                                                                   
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-runner-latest?py=py27&pytest=2.6.2.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-runner-latest?py=py34&pytest=2.6.2.dev1                            :target: https://bitbucket.org/jaraco/pytest-runner                                                                                                                                                               
-        `pytest-sftpserver-1.0.2 <http://pypi.python.org/pypi/pytest-sftpserver>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sftpserver-latest?py=py27&pytest=2.6.2.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sftpserver-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                              py.test plugin to locally test sftp server connections.                                           
-                                                                                                   :target: http://pytest-plugs.herokuapp.com/output/pytest-sftpserver-latest?py=py27&pytest=2.6.2.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-sftpserver-latest?py=py34&pytest=2.6.2.dev1                          :target: http://github.com/ulope/pytest-sftpserver/                                                                                                                                                               
-             `pytest-spec-0.2.22 <http://pypi.python.org/pypi/pytest-spec>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-spec-latest?py=py27&pytest=2.6.2.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-spec-latest?py=py34&pytest=2.6.2.dev1                             .. image:: github.png                                                                                      pytest plugin to display test execution output like a SPECIFICATION                                     
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-spec-latest?py=py27&pytest=2.6.2.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-spec-latest?py=py34&pytest=2.6.2.dev1                               :target: https://github.com/pchomik/pytest-spec                                                                                                                                                                 
-          `pytest-splinter-1.0.3 <http://pypi.python.org/pypi/pytest-splinter>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-splinter-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-splinter-latest?py=py34&pytest=2.6.2.dev1                        .. image:: github.png                                                                                                      Splinter subplugin for Pytest BDD plugin                                                   
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-splinter-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-splinter-latest?py=py34&pytest=2.6.2.dev1                          :target: https://github.com/paylogic/pytest-splinter                                                                                                                                                               
-           `pytest-stepwise-0.2 <http://pypi.python.org/pypi/pytest-stepwise>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-stepwise-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-stepwise-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                                                  Run a test suite one failing test at a time.                                                 
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-stepwise-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-stepwise-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/nip3o/pytest-stepwise                                                                                                                                                                
-             `pytest-sugar-0.3.4 <http://pypi.python.org/pypi/pytest-sugar>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sugar-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sugar-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                       py.test is a plugin for py.test that changes the default look and feel of py.test (e.g. progressbar, show tests that fail instantly).    
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-sugar-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-sugar-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/Frozenball/pytest-sugar                                                                                                                                                               
-            `pytest-timeout-0.4 <http://pypi.python.org/pypi/pytest-timeout>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-timeout-latest?py=py27&pytest=2.6.2.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-timeout-latest?py=py34&pytest=2.6.2.dev1                         .. image:: bitbucket.png                                                                                                    py.test plugin to abort hanging tests                                                    
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-timeout-latest?py=py27&pytest=2.6.2.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-timeout-latest?py=py34&pytest=2.6.2.dev1                           :target: http://bitbucket.org/flub/pytest-timeout/                                                                                                                                                                
-            `pytest-twisted-1.5 <http://pypi.python.org/pypi/pytest-twisted>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py27&pytest=2.6.2.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py34&pytest=2.6.2.dev1                          .. image:: github.png                                                                                                          A twisted plugin for py.test.                                                        
-                                                                                                     :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py27&pytest=2.6.2.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py34&pytest=2.6.2.dev1                            :target: https://github.com/schmir/pytest-twisted                                                                                                                                                                
-             `pytest-xdist-1.10 <http://pypi.python.org/pypi/pytest-xdist>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py27&pytest=2.6.2.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py34&pytest=2.6.2.dev1                           .. image:: bitbucket.png                                                                                  py.test xdist plugin for distributed testing and loop-on-failing modes                                    
-                                                                                                      :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py27&pytest=2.6.2.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py34&pytest=2.6.2.dev1                             :target: http://bitbucket.org/hpk42/pytest-xdist                                                                                                                                                                 
-           `pytest-xprocess-0.8 <http://pypi.python.org/pypi/pytest-xprocess>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py34&pytest=2.6.2.dev1                        .. image:: bitbucket.png                                                                                          pytest plugin to manage external processes across test runs                                         
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py34&pytest=2.6.2.dev1                          :target: http://bitbucket.org/hpk42/pytest-xprocess/                                                                                                                                                               
-           `pytest-yamlwsgi-0.6 <http://pypi.python.org/pypi/pytest-yamlwsgi>`_                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py27&pytest=2.6.2.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py34&pytest=2.6.2.dev1                                                   ?                                                                                              Run tests against wsgi apps defined in yaml                                                 
-                                                                                                    :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py27&pytest=2.6.2.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py34&pytest=2.6.2.dev1                                                                                                                                                                                                                                             
-                `pytest-zap-0.2 <http://pypi.python.org/pypi/pytest-zap>`_                          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py27&pytest=2.6.2.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py34&pytest=2.6.2.dev1                             .. image:: github.png                                                                                                         OWASP ZAP plugin for py.test.                                                        
-                                                                                                       :target: http://pytest-plugs.herokuapp.com/output/pytest-zap-latest?py=py27&pytest=2.6.2.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-zap-latest?py=py34&pytest=2.6.2.dev1                               :target: https://github.com/davehunt/pytest-zap                                                                                                                                                                 
+==================================================================================== ================================================================================================================= ================================================================================================================= =========================================================================== =============================================================================================================================================
+                                        Name                                                                                               Py27                                                                                                              Py34                                                                                           Home                                                                                                        Summary                                                                   
+==================================================================================== ================================================================================================================= ================================================================================================================= =========================================================================== =============================================================================================================================================
+    `pytest-allure-adaptor <http://pypi.python.org/pypi/pytest-allure-adaptor>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-allure-adaptor-latest?py=py27&pytest=2.6.4.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-allure-adaptor-latest?py=py34&pytest=2.6.4.dev1            .. image:: github.png                                                                                              Plugin for py.test to generate allure xml reports                                              
+                                                                                           :target: http://pytest-plugs.herokuapp.com/output/pytest-allure-adaptor-latest?py=py27&pytest=2.6.4.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-allure-adaptor-latest?py=py34&pytest=2.6.4.dev1              :target: https://github.com/allure-framework/allure-python                                                                                                                                                     
+               `pytest-bdd <http://pypi.python.org/pypi/pytest-bdd>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bdd-latest?py=py27&pytest=2.6.4.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bdd-latest?py=py34&pytest=2.6.4.dev1                    .. image:: github.png                                                                                                            BDD for pytest                                                                
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-bdd-latest?py=py27&pytest=2.6.4.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-bdd-latest?py=py34&pytest=2.6.4.dev1                      :target: https://github.com/olegpidsadnyi/pytest-bdd                                                                                                                                                        
+              `pytest-beds <http://pypi.python.org/pypi/pytest-beds>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-beds-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-beds-latest?py=py34&pytest=2.6.4.dev1                       .. image:: github.png                                                                                        Fixtures for testing Google Appengine (GAE) apps                                               
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-beds-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-beds-latest?py=py34&pytest=2.6.4.dev1                         :target: https://github.com/kaste/pytest-beds                                                                                                                                                            
+             `pytest-bench <http://pypi.python.org/pypi/pytest-bench>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bench-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bench-latest?py=py34&pytest=2.6.4.dev1                  .. image:: github.png                                                                                                Benchmark utility that plugs into pytest.                                                  
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-bench-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-bench-latest?py=py34&pytest=2.6.4.dev1                    :target: http://github.com/concordusapps/pytest-bench                                                                                                                                                        
+          `pytest-blockage <http://pypi.python.org/pypi/pytest-blockage>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-blockage-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-blockage-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                             Disable network requests during a test run.                                                 
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-blockage-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-blockage-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/rob-b/pytest-blockage                                                                                                                                                          
+  `pytest-browsermob-proxy <http://pypi.python.org/pypi/pytest-browsermob-proxy>`_     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-browsermob-proxy-latest?py=py27&pytest=2.6.4.dev1      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-browsermob-proxy-latest?py=py34&pytest=2.6.4.dev1          .. image:: github.png                                                                                                     BrowserMob proxy plugin for py.test.                                                     
+                                                                                          :target: http://pytest-plugs.herokuapp.com/output/pytest-browsermob-proxy-latest?py=py27&pytest=2.6.4.dev1        :target: http://pytest-plugs.herokuapp.com/output/pytest-browsermob-proxy-latest?py=py34&pytest=2.6.4.dev1            :target: https://github.com/davehunt/pytest-browsermob-proxy                                                                                                                                                    
+          `pytest-bugzilla <http://pypi.python.org/pypi/pytest-bugzilla>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py34&pytest=2.6.4.dev1                  .. image:: github.png                                                                                                  py.test bugzilla integration plugin                                                     
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py34&pytest=2.6.4.dev1                    :target: http://github.com/nibrahim/pytest_bugzilla                                                                                                                                                         
+             `pytest-cache <http://pypi.python.org/pypi/pytest-cache>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py34&pytest=2.6.4.dev1                    .. image:: bitbucket.png                                                                                  pytest plugin with mechanisms for caching across test runs                                          
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py34&pytest=2.6.4.dev1                      :target: http://bitbucket.org/hpk42/pytest-cache/                                                                                                                                                          
+        `pytest-capturelog <http://pypi.python.org/pypi/pytest-capturelog>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py34&pytest=2.6.4.dev1          .. image:: bitbucket.png                                                                                                    py.test plugin to capture log messages                                                    
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py34&pytest=2.6.4.dev1            :target: http://bitbucket.org/memedough/pytest-capturelog/overview                                                                                                                                                 
+      `pytest-codecheckers <http://pypi.python.org/pypi/pytest-codecheckers>`_           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py27&pytest=2.6.4.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py34&pytest=2.6.4.dev1        .. image:: bitbucket.png                                                                                        pytest plugin to add source code sanity checks (pep8 and friends)                                      
+                                                                                            :target: http://pytest-plugs.herokuapp.com/output/pytest-codecheckers-latest?py=py27&pytest=2.6.4.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-codecheckers-latest?py=py34&pytest=2.6.4.dev1          :target: http://bitbucket.org/RonnyPfannschmidt/pytest-codecheckers/                                                                                                                                                
+            `pytest-config <http://pypi.python.org/pypi/pytest-config>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-config-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-config-latest?py=py34&pytest=2.6.4.dev1                    .. image:: github.png                                                                  Base configurations and utilities for developing     your Python project test suite with pytest.                       
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-config-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-config-latest?py=py34&pytest=2.6.4.dev1                      :target: https://github.com/buzzfeed/pytest_config                                                                                                                                                         
+    `pytest-contextfixture <http://pypi.python.org/pypi/pytest-contextfixture>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-contextfixture-latest?py=py27&pytest=2.6.4.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-contextfixture-latest?py=py34&pytest=2.6.4.dev1             .. image:: github.png                                                                                                Define pytest fixtures as context managers.                                                 
+                                                                                           :target: http://pytest-plugs.herokuapp.com/output/pytest-contextfixture-latest?py=py27&pytest=2.6.4.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-contextfixture-latest?py=py34&pytest=2.6.4.dev1               :target: http://github.com/pelme/pytest-contextfixture/                                                                                                                                                       
+        `pytest-couchdbkit <http://pypi.python.org/pypi/pytest-couchdbkit>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-couchdbkit-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-couchdbkit-latest?py=py34&pytest=2.6.4.dev1          .. image:: bitbucket.png                                                                                       py.test extension for per-test couchdb databases using couchdbkit                                      
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-couchdbkit-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-couchdbkit-latest?py=py34&pytest=2.6.4.dev1            :target: http://bitbucket.org/RonnyPfannschmidt/pytest-couchdbkit                                                                                                                                                  
+               `pytest-cov <http://pypi.python.org/pypi/pytest-cov>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cov-latest?py=py27&pytest=2.6.4.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cov-latest?py=py34&pytest=2.6.4.dev1                      .. image:: github.png                                            py.test plugin for coverage reporting with support for both centralised and distributed testing, including subprocesses and multiprocessing 
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-cov-latest?py=py27&pytest=2.6.4.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-cov-latest?py=py34&pytest=2.6.4.dev1                        :target: https://github.com/schlamar/pytest-cov                                                                                                                                                           
+               `pytest-cpp <http://pypi.python.org/pypi/pytest-cpp>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cpp-latest?py=py27&pytest=2.6.4.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cpp-latest?py=py34&pytest=2.6.4.dev1                      .. image:: github.png                                                                                       Use pytest's runner to discover and execute C++ tests                                            
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-cpp-latest?py=py27&pytest=2.6.4.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-cpp-latest?py=py34&pytest=2.6.4.dev1                        :target: http://github.com/nicoddemus/pytest-cpp                                                                                                                                                          
+        `pytest-dbfixtures <http://pypi.python.org/pypi/pytest-dbfixtures>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbfixtures-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbfixtures-latest?py=py34&pytest=2.6.4.dev1              .. image:: github.png                                                                                                   Databases fixtures plugin for py.test.                                                    
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-dbfixtures-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-dbfixtures-latest?py=py34&pytest=2.6.4.dev1                :target: https://github.com/ClearcodeHQ/pytest-dbfixtures                                                                                                                                                      
+ `pytest-dbus-notification <http://pypi.python.org/pypi/pytest-dbus-notification>`_    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbus-notification-latest?py=py27&pytest=2.6.4.dev1     .. image:: http://pytest-plugs.herokuapp.com/status/pytest-dbus-notification-latest?py=py34&pytest=2.6.4.dev1       .. image:: github.png                                                                                                      D-BUS notifications for pytest results.                                                   
+                                                                                          :target: http://pytest-plugs.herokuapp.com/output/pytest-dbus-notification-latest?py=py27&pytest=2.6.4.dev1       :target: http://pytest-plugs.herokuapp.com/output/pytest-dbus-notification-latest?py=py34&pytest=2.6.4.dev1         :target: https://github.com/bmathieu33/pytest-dbus-notification                                                                                                                                                   
+          `pytest-describe <http://pypi.python.org/pypi/pytest-describe>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-describe-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-describe-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                                  Describe-style plugin for pytest                                                       
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-describe-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-describe-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/ropez/pytest-describe                                                                                                                                                          
+            `pytest-diffeo <http://pypi.python.org/pypi/pytest-diffeo>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-diffeo-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-diffeo-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                            Common py.test support for Diffeo packages                                                  
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-diffeo-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-diffeo-latest?py=py34&pytest=2.6.4.dev1                       :target: https://github.com/diffeo/pytest-diffeo                                                                                                                                                          
+            `pytest-django <http://pypi.python.org/pypi/pytest-django>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-latest?py=py34&pytest=2.6.4.dev1                       `link <http://pytest-django.readthedocs.org/>`_                                                                       A Django plugin for py.test.                                                         
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-django-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-django-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                                 
+   `pytest-django-haystack <http://pypi.python.org/pypi/pytest-django-haystack>`_       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-haystack-latest?py=py27&pytest=2.6.4.dev1       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-haystack-latest?py=py34&pytest=2.6.4.dev1            .. image:: github.png                                                                                                Cleanup your Haystack indexes between tests                                                 
+                                                                                           :target: http://pytest-plugs.herokuapp.com/output/pytest-django-haystack-latest?py=py27&pytest=2.6.4.dev1         :target: http://pytest-plugs.herokuapp.com/output/pytest-django-haystack-latest?py=py34&pytest=2.6.4.dev1              :target: http://github.com/rouge8/pytest-django-haystack                                                                                                                                                      
+       `pytest-django-lite <http://pypi.python.org/pypi/pytest-django-lite>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-lite-latest?py=py27&pytest=2.6.4.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-django-lite-latest?py=py34&pytest=2.6.4.dev1               .. image:: github.png                                                                                           The bare minimum to integrate py.test with Django.                                              
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-django-lite-latest?py=py27&pytest=2.6.4.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-django-lite-latest?py=py34&pytest=2.6.4.dev1                 :target: https://github.com/dcramer/pytest-django-lite                                                                                                                                                       
+              `pytest-echo <http://pypi.python.org/pypi/pytest-echo>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-echo-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-echo-latest?py=py34&pytest=2.6.4.dev1                      `link <http://pypi.python.org/pypi/pytest-echo/>`_                                 pytest plugin with mechanisms for echoing environment variables, package version and generic attributes                   
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-echo-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-echo-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                                  
+         `pytest-eradicate <http://pypi.python.org/pypi/pytest-eradicate>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py34&pytest=2.6.4.dev1               .. image:: github.png                                                                                               pytest plugin to check for commented out code                                                
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py34&pytest=2.6.4.dev1                 :target: https://github.com/spil-johan/pytest-eradicate                                                                                                                                                       
+           `pytest-figleaf <http://pypi.python.org/pypi/pytest-figleaf>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py34&pytest=2.6.4.dev1                   .. image:: bitbucket.png                                                                                                py.test figleaf coverage plugin                                                       
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py34&pytest=2.6.4.dev1                     :target: http://bitbucket.org/hpk42/pytest-figleaf                                                                                                                                                         
+     `pytest-fixture-tools <http://pypi.python.org/pypi/pytest-fixture-tools>`_          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py27&pytest=2.6.4.dev1         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py34&pytest=2.6.4.dev1                                          ?                                                                                   Plugin for pytest which provides tools for fixtures                                             
+                                                                                            :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py27&pytest=2.6.4.dev1           :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                             
+            `pytest-flakes <http://pypi.python.org/pypi/pytest-flakes>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py34&pytest=2.6.4.dev1                    .. image:: github.png                                                                                          pytest plugin to check source code with pyflakes                                               
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-flakes-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-flakes-latest?py=py34&pytest=2.6.4.dev1                      :target: https://github.com/fschulze/pytest-flakes                                                                                                                                                         
+             `pytest-flask <http://pypi.python.org/pypi/pytest-flask>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flask-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flask-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                       A set of py.test fixtures to test Flask applications.                                            
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-flask-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-flask-latest?py=py34&pytest=2.6.4.dev1                       :target: https://github.com/vitalk/pytest-flask                                                                                                                                                           
+         `pytest-greendots <http://pypi.python.org/pypi/pytest-greendots>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-greendots-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-greendots-latest?py=py34&pytest=2.6.4.dev1                                            ?                                                                                                   Green progress dots                                                             
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-greendots-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-greendots-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                               
+             `pytest-growl <http://pypi.python.org/pypi/pytest-growl>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-growl-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-growl-latest?py=py34&pytest=2.6.4.dev1                                              ?                                                                                         Growl notifications for pytest results.                                                   
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-growl-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-growl-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                                 
+           `pytest-httpbin <http://pypi.python.org/pypi/pytest-httpbin>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpbin-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpbin-latest?py=py34&pytest=2.6.4.dev1                  .. image:: github.png                                                                                     Easily test your HTTP library against a local copy of httpbin                                        
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-httpbin-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-httpbin-latest?py=py34&pytest=2.6.4.dev1                    :target: https://github.com/kevin1024/pytest-httpbin                                                                                                                                                        
+         `pytest-httpretty <http://pypi.python.org/pypi/pytest-httpretty>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpretty-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-httpretty-latest?py=py34&pytest=2.6.4.dev1                 .. image:: github.png                                                                                                A thin wrapper of HTTPretty for pytest                                                    
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-httpretty-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-httpretty-latest?py=py34&pytest=2.6.4.dev1                   :target: http://github.com/papaeye/pytest-httpretty                                                                                                                                                         
+       `pytest-incremental <http://pypi.python.org/pypi/pytest-incremental>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-incremental-latest?py=py27&pytest=2.6.4.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-incremental-latest?py=py34&pytest=2.6.4.dev1           .. image:: bitbucket.png                                                                                                an incremental test runner (pytest plugin)                                                  
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-incremental-latest?py=py27&pytest=2.6.4.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-incremental-latest?py=py34&pytest=2.6.4.dev1             :target: https://bitbucket.org/schettino72/pytest-incremental                                                                                                                                                    
+         `pytest-instafail <http://pypi.python.org/pypi/pytest-instafail>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-instafail-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-instafail-latest?py=py34&pytest=2.6.4.dev1                .. image:: github.png                                                                                                py.test plugin to show failures instantly                                                  
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-instafail-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-instafail-latest?py=py34&pytest=2.6.4.dev1                  :target: https://github.com/jpvanhal/pytest-instafail                                                                                                                                                        
+              `pytest-ipdb <http://pypi.python.org/pypi/pytest-ipdb>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ipdb-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ipdb-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                 A py.test plug-in to enable drop to ipdb debugger on test failure.                                      
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-ipdb-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-ipdb-latest?py=py34&pytest=2.6.4.dev1                       :target: https://github.com/mverteuil/pytest-ipdb                                                                                                                                                          
+              `pytest-jira <http://pypi.python.org/pypi/pytest-jira>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-jira-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-jira-latest?py=py34&pytest=2.6.4.dev1                       .. image:: github.png                                                                                         py.test JIRA integration plugin, using markers                                                
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-jira-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-jira-latest?py=py34&pytest=2.6.4.dev1                         :target: http://github.com/jlaska/pytest_jira                                                                                                                                                            
+             `pytest-knows <http://pypi.python.org/pypi/pytest-knows>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-knows-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-knows-latest?py=py34&pytest=2.6.4.dev1                        .. image:: github.png                                                              A pytest plugin that can automaticly skip test case based on dependence info calculated by trace                       
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-knows-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-knows-latest?py=py34&pytest=2.6.4.dev1                          :target: https://github.com/mapix/ptknows                                                                                                                                                              
+            `pytest-konira <http://pypi.python.org/pypi/pytest-konira>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-konira-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-konira-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                                   Run Konira DSL tests with py.test                                                      
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-konira-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-konira-latest?py=py34&pytest=2.6.4.dev1                     :target: http://github.com/alfredodeza/pytest-konira                                                                                                                                                        
+       `pytest-localserver <http://pypi.python.org/pypi/pytest-localserver>`_             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-localserver-latest?py=py27&pytest=2.6.4.dev1           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-localserver-latest?py=py34&pytest=2.6.4.dev1              .. image:: bitbucket.png                                                                                         py.test plugin to test server connections locally.                                              
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-localserver-latest?py=py27&pytest=2.6.4.dev1             :target: http://pytest-plugs.herokuapp.com/output/pytest-localserver-latest?py=py34&pytest=2.6.4.dev1                :target: http://bitbucket.org/basti/pytest-localserver/                                                                                                                                                       
+   `pytest-marker-bugzilla <http://pypi.python.org/pypi/pytest-marker-bugzilla>`_       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marker-bugzilla-latest?py=py27&pytest=2.6.4.dev1       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marker-bugzilla-latest?py=py34&pytest=2.6.4.dev1           .. image:: github.png                                                                                             py.test bugzilla integration plugin, using markers                                              
+                                                                                           :target: http://pytest-plugs.herokuapp.com/output/pytest-marker-bugzilla-latest?py=py27&pytest=2.6.4.dev1         :target: http://pytest-plugs.herokuapp.com/output/pytest-marker-bugzilla-latest?py=py34&pytest=2.6.4.dev1             :target: http://github.com/eanxgeek/pytest_marker_bugzilla                                                                                                                                                     
+    `pytest-markfiltration <http://pypi.python.org/pypi/pytest-markfiltration>`_        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-markfiltration-latest?py=py27&pytest=2.6.4.dev1        .. image:: http://pytest-plugs.herokuapp.com/status/pytest-markfiltration-latest?py=py34&pytest=2.6.4.dev1          .. image:: github.png                                                                                                                     UNKNOWN                                                                   
+                                                                                           :target: http://pytest-plugs.herokuapp.com/output/pytest-markfiltration-latest?py=py27&pytest=2.6.4.dev1          :target: http://pytest-plugs.herokuapp.com/output/pytest-markfiltration-latest?py=py34&pytest=2.6.4.dev1            :target: https://github.com/adamgoucher/pytest-markfiltration                                                                                                                                                    
+             `pytest-marks <http://pypi.python.org/pypi/pytest-marks>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marks-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-marks-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                                                UNKNOWN                                                                   
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-marks-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-marks-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/adamgoucher/pytest-marks                                                                                                                                                        
+              `pytest-mock <http://pypi.python.org/pypi/pytest-mock>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mock-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mock-latest?py=py34&pytest=2.6.4.dev1                    .. image:: github.png                                                                                   Thin-wrapper around the mock package for easier use with py.test                                       
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-mock-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-mock-latest?py=py34&pytest=2.6.4.dev1                      :target: https://github.com/nicoddemus/pytest-mock/                                                                                                                                                         
+        `pytest-monkeyplus <http://pypi.python.org/pypi/pytest-monkeyplus>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-monkeyplus-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-monkeyplus-latest?py=py34&pytest=2.6.4.dev1                .. image:: bitbucket.png                                                                                     pytest's monkeypatch subclass with extra functionalities                                           
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-monkeyplus-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-monkeyplus-latest?py=py34&pytest=2.6.4.dev1                  :target: http://bitbucket.org/hsoft/pytest-monkeyplus/                                                                                                                                                       
+          `pytest-mozwebqa <http://pypi.python.org/pypi/pytest-mozwebqa>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mozwebqa-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-mozwebqa-latest?py=py34&pytest=2.6.4.dev1                  .. image:: github.png                                                                                                   Mozilla WebQA plugin for py.test.                                                      
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-mozwebqa-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-mozwebqa-latest?py=py34&pytest=2.6.4.dev1                    :target: https://github.com/davehunt/pytest-mozwebqa                                                                                                                                                        
+              `pytest-oerp <http://pypi.python.org/pypi/pytest-oerp>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-oerp-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-oerp-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                                pytest plugin to test OpenERP modules                                                    
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-oerp-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-oerp-latest?py=py34&pytest=2.6.4.dev1                       :target: http://github.com/santagada/pytest-oerp/                                                                                                                                                          
+          `pytest-ordering <http://pypi.python.org/pypi/pytest-ordering>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ordering-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-ordering-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                         pytest plugin to run your tests in a specific order                                             
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-ordering-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-ordering-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/ftobia/pytest-ordering                                                                                                                                                         
+         `pytest-osxnotify <http://pypi.python.org/pypi/pytest-osxnotify>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-osxnotify-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-osxnotify-latest?py=py34&pytest=2.6.4.dev1                 .. image:: github.png                                                                                                OS X notifications for py.test results.                                                   
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-osxnotify-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-osxnotify-latest?py=py34&pytest=2.6.4.dev1                   :target: https://github.com/dbader/pytest-osxnotify                                                                                                                                                         
+      `pytest-paste-config <http://pypi.python.org/pypi/pytest-paste-config>`_           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py27&pytest=2.6.4.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py34&pytest=2.6.4.dev1                                           ?                                                                                      Allow setting the path to a paste config file                                                
+                                                                                            :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py27&pytest=2.6.4.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                              
+              `pytest-pep8 <http://pypi.python.org/pypi/pytest-pep8>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py34&pytest=2.6.4.dev1                      .. image:: bitbucket.png                                                                                          pytest plugin to check PEP8 requirements                                                   
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py34&pytest=2.6.4.dev1                        :target: http://bitbucket.org/hpk42/pytest-pep8/                                                                                                                                                          
+          `pytest-pipeline <http://pypi.python.org/pypi/pytest-pipeline>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py34&pytest=2.6.4.dev1                    .. image:: github.png                                                                                  Pytest plugin for functional testing of data analysis pipelines                                       
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py34&pytest=2.6.4.dev1                      :target: https://github.com/bow/pytest_pipeline                                                                                                                                                           
+               `pytest-poo <http://pypi.python.org/pypi/pytest-poo>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py27&pytest=2.6.4.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py34&pytest=2.6.4.dev1                        .. image:: github.png                                                                                                  Visualize your crappy tests                                                         
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-poo-latest?py=py27&pytest=2.6.4.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-poo-latest?py=py34&pytest=2.6.4.dev1                          :target: http://github.com/pelme/pytest-poo                                                                                                                                                             
+           `pytest-pycharm <http://pypi.python.org/pypi/pytest-pycharm>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pycharm-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pycharm-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                 Plugin for py.test to enter PyCharm debugger on uncaught exceptions                                     
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-pycharm-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-pycharm-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/jlubcke/pytest-pycharm                                                                                                                                                         
+             `pytest-pydev <http://pypi.python.org/pypi/pytest-pydev>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pydev-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pydev-latest?py=py34&pytest=2.6.4.dev1                    .. image:: bitbucket.png                                                                           py.test plugin to connect to a remote debug server with PyDev or PyCharm.                                  
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-pydev-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-pydev-latest?py=py34&pytest=2.6.4.dev1                      :target: http://bitbucket.org/basti/pytest-pydev/                                                                                                                                                          
+        `pytest-pythonpath <http://pypi.python.org/pypi/pytest-pythonpath>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pythonpath-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pythonpath-latest?py=py34&pytest=2.6.4.dev1                .. image:: github.png                                                                                pytest plugin for adding to the PYTHONPATH from command line or configs.                                   
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-pythonpath-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-pythonpath-latest?py=py34&pytest=2.6.4.dev1                  :target: https://github.com/bigsassy/pytest-pythonpath                                                                                                                                                       
+                `pytest-qt <http://pypi.python.org/pypi/pytest-qt>`_                          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-qt-latest?py=py27&pytest=2.6.4.dev1                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-qt-latest?py=py34&pytest=2.6.4.dev1                       .. image:: github.png                                                                                          pytest support for PyQt and PySide applications                                               
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-qt-latest?py=py27&pytest=2.6.4.dev1                      :target: http://pytest-plugs.herokuapp.com/output/pytest-qt-latest?py=py34&pytest=2.6.4.dev1                         :target: http://github.com/nicoddemus/pytest-qt                                                                                                                                                           
+        `pytest-quickcheck <http://pypi.python.org/pypi/pytest-quickcheck>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-quickcheck-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-quickcheck-latest?py=py34&pytest=2.6.4.dev1                 .. image:: bitbucket.png                                                                                  pytest plugin to generate random data inspired by QuickCheck                                         
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-quickcheck-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-quickcheck-latest?py=py34&pytest=2.6.4.dev1                   :target: http://bitbucket.org/t2y/pytest-quickcheck/                                                                                                                                                        
+              `pytest-rage <http://pypi.python.org/pypi/pytest-rage>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rage-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rage-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                                  pytest plugin to implement PEP712                                                      
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-rage-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-rage-latest?py=py34&pytest=2.6.4.dev1                       :target: http://github.com/santagada/pytest-rage/                                                                                                                                                          
+      `pytest-raisesregexp <http://pypi.python.org/pypi/pytest-raisesregexp>`_           .. image:: http://pytest-plugs.herokuapp.com/status/pytest-raisesregexp-latest?py=py27&pytest=2.6.4.dev1          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-raisesregexp-latest?py=py34&pytest=2.6.4.dev1              .. image:: github.png                                                                                           Simple pytest plugin to look for regex in Exceptions                                             
+                                                                                            :target: http://pytest-plugs.herokuapp.com/output/pytest-raisesregexp-latest?py=py27&pytest=2.6.4.dev1            :target: http://pytest-plugs.herokuapp.com/output/pytest-raisesregexp-latest?py=py34&pytest=2.6.4.dev1                :target: https://github.com/Walkman/pytest_raisesregexp                                                                                                                                                       
+            `pytest-random <http://pypi.python.org/pypi/pytest-random>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-random-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-random-latest?py=py34&pytest=2.6.4.dev1                     .. image:: github.png                                                                                                 py.test plugin to randomize tests                                                      
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-random-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-random-latest?py=py34&pytest=2.6.4.dev1                       :target: https://github.com/klrmn/pytest-random                                                                                                                                                           
+           `pytest-regtest <http://pypi.python.org/pypi/pytest-regtest>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-regtest-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-regtest-latest?py=py34&pytest=2.6.4.dev1         `link <https://sissource.ethz.ch/uweschmitt/pytest-regtest/tree/master>`_                                                       py.test plugin for regression tests                                                     
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-regtest-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-regtest-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                                
+     `pytest-rerunfailures <http://pypi.python.org/pypi/pytest-rerunfailures>`_          .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rerunfailures-latest?py=py27&pytest=2.6.4.dev1         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-rerunfailures-latest?py=py34&pytest=2.6.4.dev1              .. image:: github.png                                                                                       py.test plugin to re-run tests to eliminate flakey failures                                         
+                                                                                            :target: http://pytest-plugs.herokuapp.com/output/pytest-rerunfailures-latest?py=py27&pytest=2.6.4.dev1           :target: http://pytest-plugs.herokuapp.com/output/pytest-rerunfailures-latest?py=py34&pytest=2.6.4.dev1                :target: https://github.com/klrmn/pytest-rerunfailures                                                                                                                                                       
+         `pytest-runfailed <http://pypi.python.org/pypi/pytest-runfailed>`_                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runfailed-latest?py=py27&pytest=2.6.4.dev1             .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runfailed-latest?py=py34&pytest=2.6.4.dev1               .. image:: github.png                                                                                                  implement a --failed option for pytest                                                    
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-runfailed-latest?py=py27&pytest=2.6.4.dev1               :target: http://pytest-plugs.herokuapp.com/output/pytest-runfailed-latest?py=py34&pytest=2.6.4.dev1                 :target: http://github.com/dmerejkowsky/pytest-runfailed                                                                                                                                                      
+            `pytest-runner <http://pypi.python.org/pypi/pytest-runner>`_                    .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runner-latest?py=py27&pytest=2.6.4.dev1                .. image:: http://pytest-plugs.herokuapp.com/status/pytest-runner-latest?py=py34&pytest=2.6.4.dev1                   .. image:: bitbucket.png                                                                                 Invoke py.test as distutils command with dependency resolution.                                       
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-runner-latest?py=py27&pytest=2.6.4.dev1                  :target: http://pytest-plugs.herokuapp.com/output/pytest-runner-latest?py=py34&pytest=2.6.4.dev1                     :target: https://bitbucket.org/jaraco/pytest-runner                                                                                                                                                         
+        `pytest-sftpserver <http://pypi.python.org/pypi/pytest-sftpserver>`_              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sftpserver-latest?py=py27&pytest=2.6.4.dev1            .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sftpserver-latest?py=py34&pytest=2.6.4.dev1                 .. image:: github.png                                                                                        py.test plugin to locally test sftp server connections.                                           
+                                                                                             :target: http://pytest-plugs.herokuapp.com/output/pytest-sftpserver-latest?py=py27&pytest=2.6.4.dev1              :target: http://pytest-plugs.herokuapp.com/output/pytest-sftpserver-latest?py=py34&pytest=2.6.4.dev1                   :target: http://github.com/ulope/pytest-sftpserver/                                                                                                                                                         
+              `pytest-spec <http://pypi.python.org/pypi/pytest-spec>`_                       .. image:: http://pytest-plugs.herokuapp.com/status/pytest-spec-latest?py=py27&pytest=2.6.4.dev1                  .. image:: http://pytest-plugs.herokuapp.com/status/pytest-spec-latest?py=py34&pytest=2.6.4.dev1                      .. image:: github.png                                                                                pytest plugin to display test execution output like a SPECIFICATION                                     
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-spec-latest?py=py27&pytest=2.6.4.dev1                    :target: http://pytest-plugs.herokuapp.com/output/pytest-spec-latest?py=py34&pytest=2.6.4.dev1                        :target: https://github.com/pchomik/pytest-spec                                                                                                                                                           
+          `pytest-splinter <http://pypi.python.org/pypi/pytest-splinter>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-splinter-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-splinter-latest?py=py34&pytest=2.6.4.dev1                 .. image:: github.png                                                                                              Splinter plugin for pytest testing framework                                                 
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-splinter-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-splinter-latest?py=py34&pytest=2.6.4.dev1                   :target: https://github.com/pytest-dev/pytest-splinter                                                                                                                                                       
+          `pytest-stepwise <http://pypi.python.org/pypi/pytest-stepwise>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-stepwise-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-stepwise-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                            Run a test suite one failing test at a time.                                                 
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-stepwise-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-stepwise-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/nip3o/pytest-stepwise                                                                                                                                                          
+             `pytest-sugar <http://pypi.python.org/pypi/pytest-sugar>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sugar-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-sugar-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                 py.test is a plugin for py.test that changes the default look and feel of py.test (e.g. progressbar, show tests that fail instantly).    
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-sugar-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-sugar-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/Frozenball/pytest-sugar                                                                                                                                                         
+           `pytest-timeout <http://pypi.python.org/pypi/pytest-timeout>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-timeout-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-timeout-latest?py=py34&pytest=2.6.4.dev1                   .. image:: bitbucket.png                                                                                             py.test plugin to abort hanging tests                                                    
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-timeout-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-timeout-latest?py=py34&pytest=2.6.4.dev1                     :target: http://bitbucket.org/flub/pytest-timeout/                                                                                                                                                         
+           `pytest-twisted <http://pypi.python.org/pypi/pytest-twisted>`_                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py27&pytest=2.6.4.dev1               .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py34&pytest=2.6.4.dev1                   .. image:: github.png                                                                                                    A twisted plugin for py.test.                                                        
+                                                                                               :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py27&pytest=2.6.4.dev1                 :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py34&pytest=2.6.4.dev1                     :target: https://github.com/schmir/pytest-twisted                                                                                                                                                          
+             `pytest-xdist <http://pypi.python.org/pypi/pytest-xdist>`_                      .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py27&pytest=2.6.4.dev1                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py34&pytest=2.6.4.dev1                     .. image:: bitbucket.png                                                                           py.test xdist plugin for distributed testing and loop-on-failing modes                                    
+                                                                                                :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py27&pytest=2.6.4.dev1                   :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py34&pytest=2.6.4.dev1                       :target: http://bitbucket.org/hpk42/pytest-xdist                                                                                                                                                          
+          `pytest-xprocess <http://pypi.python.org/pypi/pytest-xprocess>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py34&pytest=2.6.4.dev1                  .. image:: bitbucket.png                                                                                   pytest plugin to manage external processes across test runs                                         
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py34&pytest=2.6.4.dev1                    :target: http://bitbucket.org/hpk42/pytest-xprocess/                                                                                                                                                        
+          `pytest-yamlwsgi <http://pypi.python.org/pypi/pytest-yamlwsgi>`_                 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py27&pytest=2.6.4.dev1              .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py34&pytest=2.6.4.dev1                                             ?                                                                                       Run tests against wsgi apps defined in yaml                                                 
+                                                                                              :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py27&pytest=2.6.4.dev1                :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py34&pytest=2.6.4.dev1                                                                                                                                                                                                                                
+               `pytest-zap <http://pypi.python.org/pypi/pytest-zap>`_                         .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py27&pytest=2.6.4.dev1                   .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py34&pytest=2.6.4.dev1                      .. image:: github.png                                                                                                   OWASP ZAP plugin for py.test.                                                        
+                                                                                                 :target: http://pytest-plugs.herokuapp.com/output/pytest-zap-latest?py=py27&pytest=2.6.4.dev1                     :target: http://pytest-plugs.herokuapp.com/output/pytest-zap-latest?py=py34&pytest=2.6.4.dev1                        :target: https://github.com/davehunt/pytest-zap                                                                                                                                                           
 
-========================================================================================== ================================================================================================================= ================================================================================================================= ======================================================================================== =============================================================================================================================================
+==================================================================================== ================================================================================================================= ================================================================================================================= =========================================================================== =============================================================================================================================================
 
-*(Updated on 2014-08-26)*
+*(Updated on 2014-09-27)*

doc/en/plugins_index/plugins_index.py

@@ -61,7 +61,7 @@ def get_latest_versions(plugins):
         yield name, str(loose_version)
 
 
-def obtain_plugins_table(plugins, client):
+def obtain_plugins_table(plugins, client, verbose):
     """
     Returns information to populate a table of plugins, their versions,
     authors, etc.
@@ -72,6 +72,7 @@ def obtain_plugins_table(plugins, client):
 
     :param plugins: list of (name, version)
     :param client: ServerProxy
+    :param verbose: print plugin name and version as they are fetch
     """
     def get_repo_markup(repo):
         """
@@ -96,7 +97,7 @@ def obtain_plugins_table(plugins, client):
             pad_right = ('%-' + str(len(target_markup)) + 's')
             return pad_right % image_markup, target_markup
         else:
-            return ('`%s <%s>`_' % (target, target)), ''
+            return ('`link <%s>`_' % target), ''
     
     def sanitize_summary(summary):
         """Make sure summaries don't break our table formatting.
@@ -105,13 +106,14 @@ def obtain_plugins_table(plugins, client):
 
     rows = []
     ColumnData = namedtuple('ColumnData', 'text link')
-    headers = ['Name', 'Py27', 'Py34', 'Repo', 'Summary']
+    headers = ['Name', 'Py27', 'Py34', 'Home', 'Summary']
     pytest_version = pytest.__version__
     repositories = obtain_override_repositories()
-    print('*** pytest-{0} ***'.format(pytest_version))
+    print('Generating plugins_index page (pytest-{0})'.format(pytest_version))
     plugins = list(plugins)
     for index, (package_name, version) in enumerate(plugins):
-        print(package_name, version, '...', end='')
+        if verbose:
+            print(package_name, version, '...', end='')
 
         release_data = client.release_data(package_name, version)
 
@@ -128,7 +130,7 @@ def obtain_plugins_table(plugins, client):
         image_url = url.format(**common_params)
         image_url += '?py={py}&pytest={pytest}'
         row = (
-            ColumnData(package_name + "-" + version, release_data['package_url']),
+            ColumnData(package_name, release_data['package_url']),
             ColumnData(image_url.format(py='py27', pytest=pytest_version),
                        None),
             ColumnData(image_url.format(py='py34', pytest=pytest_version),
@@ -159,7 +161,10 @@ def obtain_plugins_table(plugins, client):
         assert len(row) == len(headers)
         rows.append(row)
 
-        print('OK (%d%%)' % ((index + 1) * 100 / len(plugins)))
+        if verbose:
+            print('OK (%d%%)' % ((index + 1) * 100 / len(plugins)))
+
+    print('Done: %d plugins' % len(plugins))
 
     return headers, rows
 
@@ -235,16 +240,17 @@ def generate_plugins_index_from_table(filename, headers, rows):
         print('*(Updated on %s)*' % today, file=f)
 
 
-def generate_plugins_index(client, filename):
+def generate_plugins_index(client, filename, verbose):
     """
     Generates an RST file with a table of the latest pytest plugins found in
     PyPI.
 
     :param client: ServerProxy
     :param filename: output filename
+    :param verbose: print name and version of each plugin as they are fetch
     """
     plugins = get_latest_versions(iter_plugins(client))
-    headers, rows = obtain_plugins_table(plugins, client)
+    headers, rows = obtain_plugins_table(plugins, client, verbose)
     generate_plugins_index_from_table(filename, headers, rows)
 
 
@@ -262,13 +268,15 @@ def main(argv):
                       help='output filename [default: %default]')
     parser.add_option('-u', '--url', default=url,
                       help='url of PyPI server to obtain data from [default: %default]')
+    parser.add_option('-v', '--verbose', default=False, action='store_true',
+                      help='verbose output')
     (options, _) = parser.parse_args(argv[1:])
 
     client = get_proxy(options.url)
-    generate_plugins_index(client, options.filename)
+    generate_plugins_index(client, options.filename, options.verbose)
 
     print()
-    print('%s Updated.' % options.filename)
+    print('%s updated.' % options.filename)
     return 0
 
 

doc/en/skipping.txt

@@ -164,7 +164,7 @@ Running it with the report-on-xfail option gives this output::
 
     example $ py.test -rx xfail_demo.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 7 items
     
     xfail_demo.py xxxxxxx
@@ -182,7 +182,7 @@ Running it with the report-on-xfail option gives this output::
       reason: reason
     XFAIL xfail_demo.py::test_hello7
     
-    ======================== 7 xfailed in 0.05 seconds =========================
+    ======================== 7 xfailed in 0.04 seconds =========================
 
 .. _`skip/xfail with parametrize`:
 

doc/en/tmpdir.txt

@@ -29,7 +29,7 @@ Running this would result in a passed test except for the last
 
     $ py.test test_tmpdir.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 1 items
     
     test_tmpdir.py F
@@ -37,7 +37,7 @@ Running this would result in a passed test except for the last
     ================================= FAILURES =================================
     _____________________________ test_create_file _____________________________
     
-    tmpdir = local('/tmp/pytest-506/test_create_file0')
+    tmpdir = local('/tmp/pytest-109/test_create_file0')
     
         def test_create_file(tmpdir):
             p = tmpdir.mkdir("sub").join("hello.txt")

doc/en/unittest.txt

@@ -88,7 +88,7 @@ the ``self.db`` values in the traceback::
 
     $ py.test test_unittest_db.py
     =========================== test session starts ============================
-    platform linux -- Python 3.4.0 -- py-1.4.23 -- pytest-2.6.1
+    platform linux -- Python 3.4.0 -- py-1.4.26 -- pytest-2.6.4
     collected 2 items
     
     test_unittest_db.py FF
@@ -101,7 +101,8 @@ the ``self.db`` values in the traceback::
         def test_method1(self):
             assert hasattr(self, "db")
     >       assert 0, self.db   # fail for demo purposes
-    E       AssertionError: <conftest.db_class.<locals>.DummyDB object at 0x2b12849f90b8>
+    E       AssertionError: <conftest.db_class.<locals>.DummyDB object at 0x2b98cc5a2e80>
+    E       assert 0
     
     test_unittest_db.py:9: AssertionError
     ___________________________ MyTest.test_method2 ____________________________
@@ -110,10 +111,11 @@ the ``self.db`` values in the traceback::
     
         def test_method2(self):
     >       assert 0, self.db   # fail for demo purposes
-    E       AssertionError: <conftest.db_class.<locals>.DummyDB object at 0x2b12849f90b8>
+    E       AssertionError: <conftest.db_class.<locals>.DummyDB object at 0x2b98cc5a2e80>
+    E       assert 0
     
     test_unittest_db.py:12: AssertionError
-    ========================= 2 failed in 0.05 seconds =========================
+    ========================= 2 failed in 0.04 seconds =========================
 
 This default pytest traceback shows that the two test methods
 share the same ``self.db`` instance which was our intention

doc/ja/Makefile

@@ -1,159 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS    =
-SPHINXBUILD   = sphinx-build
-PAPER         =
-BUILDDIR      = _build
-
-# Internal variables.
-PAPEROPT_a4     = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
-
-regen:
-	PYTHONDONTWRITEBYTECODE=1 COLUMNS=76 regendoc --update *.txt */*.txt
-    
-help:
-	@echo "Please use \`make <target>' where <target> is one of"
-	@echo "  html       to make standalone HTML files"
-	@echo "  dirhtml    to make HTML files named index.html in directories"
-	@echo "  singlehtml to make a single large HTML file"
-	@echo "  pickle     to make pickle files"
-	@echo "  json       to make JSON files"
-	@echo "  htmlhelp   to make HTML files and a HTML help project"
-	@echo "  qthelp     to make HTML files and a qthelp project"
-	@echo "  devhelp    to make HTML files and a Devhelp project"
-	@echo "  epub       to make an epub"
-	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
-	@echo "  texinfo    to make Texinfo files"
-	@echo "  info       to make Texinfo files and run them through makeinfo"
-	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-	@echo "  text       to make text files"
-	@echo "  man        to make manual pages"
-	@echo "  changes    to make an overview of all changed/added/deprecated items"
-	@echo "  linkcheck  to check all external links for integrity"
-	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
-
-clean:
-	-rm -rf $(BUILDDIR)/*
-
-install: html
-	 rsync -avz _build/html/ pytest.org:/www/pytest.org/latest-ja
-
-installpdf: latexpdf
-	@scp $(BUILDDIR)/latex/pytest.pdf pytest.org:/www/pytest.org/latest
-
-installall: clean install installpdf
-	@echo "done"
-
-html:
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-dirhtml:
-	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-singlehtml:
-	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-	@echo
-	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-	@echo
-	@echo "Build finished; now you can process the pickle files."
-
-json:
-	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-	@echo
-	@echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-	@echo
-	@echo "Build finished; now you can run HTML Help Workshop with the" \
-	      ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-	@echo
-	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
-	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/pytest.qhcp"
-	@echo "To view the help file:"
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/pytest.qhc"
-
-devhelp:
-	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
-	@echo
-	@echo "Build finished."
-	@echo "To view the help file:"
-	@echo "# mkdir -p $$HOME/.local/share/devhelp/pytest"
-	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/pytest"
-	@echo "# devhelp"
-
-epub:
-	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
-	@echo
-	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
-
-latex:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo
-	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
-	@echo "Run \`make' in that directory to run these through (pdf)latex" \
-	      "(use \`make latexpdf' here to do that automatically)."
-
-latexpdf:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo "Running LaTeX files through pdflatex..."
-	make -C $(BUILDDIR)/latex all-pdf
-	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
-
-text:
-	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
-	@echo
-	@echo "Build finished. The text files are in $(BUILDDIR)/text."
-
-man:
-	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
-	@echo
-	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
-
-changes:
-	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
-	@echo
-	@echo "The overview file is in $(BUILDDIR)/changes."
-
-linkcheck:
-	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
-	@echo
-	@echo "Link check complete; look for any errors in the above output " \
-	      "or in $(BUILDDIR)/linkcheck/output.txt."
-
-doctest:
-	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
-	@echo "Testing of doctests in the sources finished, look at the " \
-	      "results in $(BUILDDIR)/doctest/output.txt."
-
-texinfo:
-	mkdir -p $(BUILDDIR)/texinfo
-	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
-	@echo
-	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
-	@echo "Run \`make' in that directory to run these through makeinfo" \
-	      "(use \`make info' here to do that automatically)."
-
-info:
-	mkdir -p $(BUILDDIR)/texinfo
-	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
-	@echo "Running Texinfo files through makeinfo..."
-	make -C $(BUILDDIR)/texinfo info
-	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."

doc/ja/_static/sphinxdoc.css

@@ -1,343 +0,0 @@
-/*
- * sphinxdoc.css_t
- * ~~~~~~~~~~~~~~~
- *
- * Sphinx stylesheet -- sphinxdoc theme.  Originally created by
- * Armin Ronacher for Werkzeug.
- *
- * :copyright: Copyright 2007-2010 by the Sphinx team, see AUTHORS.
- * :license: BSD, see LICENSE for details.
- *
- */
-
-@import url("basic.css");
-
-/* -- page layout ----------------------------------------------------------- */
-
-body {
-    font-family: 'Lucida Grande', 'Lucida Sans Unicode', 'Geneva',
-                 'Verdana', sans-serif;
-    font-size: 1.1em;
-    letter-spacing: -0.01em;
-    line-height: 150%;
-    text-align: center;
-    background-color: #BFD1D4;
-    color: black;
-    padding: 0;
-    border: 1px solid #aaa;
-
-    margin: 0px 80px 0px 80px;
-    min-width: 740px;
-}
-
-div.document {
-    background-color: white;
-    text-align: left;
-    background-image: url(contents.png);
-    background-repeat: repeat-x;
-}
-
-div.bodywrapper {
-    margin: 0 290px 0 0;
-    border-right: 1px solid #ccc;
-}
-
-div.body {
-    margin: 0;
-    padding: 0.5em 20px 20px 20px;
-}
-
-div.related {
-    font-size: 0.8em;
-}
-
-div.related ul {
-    background-image: url(navigation.png);
-    height: 2em;
-    border-top: 1px solid #ddd;
-    border-bottom: 1px solid #ddd;
-}
-
-div.related ul li {
-    margin: 0;
-    padding: 0;
-    height: 2em;
-    float: left;
-}
-
-div.related ul li.right {
-    float: right;
-    margin-right: 5px;
-}
-
-div.related ul li a {
-    margin: 0;
-    padding: 0 5px 0 5px;
-    line-height: 1.75em;
-    color: #EE9816;
-}
-
-div.related ul li a:hover {
-    color: #3CA8E7;
-}
-
-div.sphinxsidebarwrapper {
-    padding: 0;
-}
-
-div.sphinxsidebar {
-    margin: 0;
-    padding: 0.5em 15px 15px 0;
-    width: 260px;
-    float: right;
-    font-size: 1em;
-    text-align: left;
-}
-
-div.sphinxsidebar h3, div.sphinxsidebar h4 {
-    margin: 1em 0 0.5em 0;
-    font-size: 1em;
-    padding: 0.1em 0 0.1em 0.5em;
-    color: white;
-    border: 1px solid #86989B;
-    background-color: #AFC1C4;
-}
-
-div.sphinxsidebar h3 a {
-    color: white;
-}
-
-div.sphinxsidebar ul {
-    padding-left: 1.5em;
-    margin-top: 7px;
-    padding: 0;
-    line-height: 130%;
-}
-
-div.sphinxsidebar ul ul {
-    margin-left: 20px;
-}
-
-div.sphinxsidebar #searchbox input[type="submit"] {
-    width: 55px;
-}
-
-div.footer {
-    background-color: #E3EFF1;
-    color: #86989B;
-    padding: 3px 8px 3px 0;
-    clear: both;
-    font-size: 0.8em;
-    text-align: right;
-}
-
-div.footer a {
-    color: #86989B;
-    text-decoration: underline;
-}
-
-/* -- body styles ----------------------------------------------------------- */
-
-p {    
-    margin: 0.8em 0 0.5em 0;
-}
-
-a {
-    color: #CA7900;
-    text-decoration: none;
-}
-
-a:hover {
-    color: #2491CF;
-}
-
-div.body a {
-    text-decoration: underline;
-}
-
-h1 {
-    margin: 0;
-    padding: 0.7em 0 0.3em 0;
-    font-size: 1.5em;
-    color: #11557C;
-}
-
-h2 {
-    margin: 1.3em 0 0.2em 0;
-    font-size: 1.35em;
-    padding: 0;
-}
-
-h3 {
-    margin: 1em 0 -0.3em 0;
-    font-size: 1.2em;
-}
-
-div.body h1 a, div.body h2 a, div.body h3 a, div.body h4 a, div.body h5 a, div.body h6 a {
-    color: black!important;
-}
-
-h1 a.anchor, h2 a.anchor, h3 a.anchor, h4 a.anchor, h5 a.anchor, h6 a.anchor {
-    display: none;
-    margin: 0 0 0 0.3em;
-    padding: 0 0.2em 0 0.2em;
-    color: #aaa!important;
-}
-
-h1:hover a.anchor, h2:hover a.anchor, h3:hover a.anchor, h4:hover a.anchor,
-h5:hover a.anchor, h6:hover a.anchor {
-    display: inline;
-}
-
-h1 a.anchor:hover, h2 a.anchor:hover, h3 a.anchor:hover, h4 a.anchor:hover,
-h5 a.anchor:hover, h6 a.anchor:hover {
-    color: #777;
-    background-color: #eee;
-}
-
-a.headerlink {
-    color: #c60f0f!important;
-    font-size: 1em;
-    margin-left: 6px;
-    padding: 0 4px 0 4px;
-    text-decoration: none!important;
-}
-
-a.headerlink:hover {
-    background-color: #ccc;
-    color: white!important;
-}
-
-cite, code, tt {
-    font-family: 'Consolas', 'Deja Vu Sans Mono',
-                 'Bitstream Vera Sans Mono', monospace;
-    font-size: 0.95em;
-    letter-spacing: 0.01em;
-}
-
-tt {
-    background-color: #f2f2f2;
-    border-bottom: 1px solid #ddd;
-    color: #333;
-}
-
-tt.descname, tt.descclassname, tt.xref {
-    border: 0;
-}
-
-hr {
-    border: 1px solid #abc;
-    margin: 2em;
-}
-
-a tt {
-    border: 0;
-    color: #CA7900;
-}
-
-a tt:hover {
-    color: #2491CF;
-}
-
-pre {
-    font-family: 'Consolas', 'Deja Vu Sans Mono',
-                 'Bitstream Vera Sans Mono', monospace;
-    font-size: 0.95em;
-    letter-spacing: 0.015em;
-    line-height: 120%;
-    padding: 0.5em;
-    border: 1px solid #ccc;
-    background-color: #f8f8f8;
-}
-
-pre a {
-    color: inherit;
-    text-decoration: underline;
-}
-
-td.linenos pre {
-    padding: 0.5em 0;
-}
-
-div.quotebar {
-    background-color: #f8f8f8;
-    max-width: 250px;
-    float: right;
-    padding: 2px 7px;
-    border: 1px solid #ccc;
-}
-
-div.topic {
-    background-color: #f8f8f8;
-}
-
-table {
-    border-collapse: collapse;
-    margin: 0 -0.5em 0 -0.5em;
-}
-
-table td, table th {
-    padding: 0.2em 0.5em 0.2em 0.5em;
-}
-
-div.admonition, div.warning {
-    font-size: 0.9em;
-    margin: 1em 0 1em 0;
-    border: 1px solid #86989B;
-    background-color: #f7f7f7;
-    padding: 0;
-}
-
-div.admonition p, div.warning p {
-    margin: 0.5em 1em 0.5em 1em;
-    padding: 0;
-}
-
-div.admonition pre, div.warning pre {
-    margin: 0.4em 1em 0.4em 1em;
-}
-
-div.admonition p.admonition-title,
-div.warning p.admonition-title {
-    margin: 0;
-    padding: 0.1em 0 0.1em 0.5em;
-    color: white;
-    border-bottom: 1px solid #86989B;
-    font-weight: bold;
-    background-color: #AFC1C4;
-}
-
-div.warning {
-    border: 1px solid #940000;
-}
-
-div.warning p.admonition-title {
-    background-color: #CF0000;
-    border-bottom-color: #940000;
-}
-
-div.admonition ul, div.admonition ol,
-div.warning ul, div.warning ol {
-    margin: 0.1em 0.5em 0.5em 3em;
-    padding: 0;
-}
-
-div.versioninfo {
-    margin: 1em 0 0 0;
-    border: 1px solid #ccc;
-    background-color: #DDEAF0;
-    padding: 8px;
-    line-height: 1.3em;
-    font-size: 0.9em;
-}
-
-.viewcode-back {
-    font-family: 'Lucida Grande', 'Lucida Sans Unicode', 'Geneva',
-                 'Verdana', sans-serif;
-}
-
-div.viewcode-block:target {
-    background-color: #f4debf;
-    border-top: 1px solid #ac9;
-    border-bottom: 1px solid #ac9;
-}

doc/ja/announce/index.txt

@@ -1,24 +0,0 @@
-
-..
-    Release announcements
-    ===========================================
-
-リリースアナウンス
-==================
-
-.. toctree::
-   :maxdepth: 2
-
-   release-2.2.4
-   release-2.2.2
-   release-2.2.1
-   release-2.2.0
-   release-2.1.3
-   release-2.1.2
-   release-2.1.1
-   release-2.1.0
-   release-2.0.3
-   release-2.0.2
-   release-2.0.1
-   release-2.0.0
-

doc/ja/announce/release-2.0.0.txt

@@ -1,129 +0,0 @@
-py.test 2.0.0: asserts++, unittest++, reporting++, config++, docs++
-===========================================================================
-
-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 enhancements,
-see below for summary and detailed lists.  A lot of long-deprecated code
-has been removed, resulting in a much smaller and cleaner
-implementation.  See the new docs with examples here:
-
-    http://pytest.org/2.0.0/index.html
-
-A note on packaging: pytest used to part of the "py" distribution up
-until version py-1.3.4 but this has changed now:  pytest-2.0.0 only
-contains py.test related code and is expected to be backward-compatible
-to existing test code. If you want to install pytest, just type one of::
-
-    pip install -U pytest
-    easy_install -U pytest
-
-Many thanks to all issue reporters and people asking questions or
-complaining.  Particular thanks to Floris Bruynooghe and Ronny Pfannschmidt
-for their great coding contributions and many others for feedback and help.
-
-best,
-holger krekel
-
-
-New Features
------------------------
-
-- new invocations through Python interpreter and from Python::
-
-    python -m pytest      # on all pythons >= 2.5
-
-  or from a python program::
-
-    import pytest ; pytest.main(arglist, pluginlist)
-
-  see http://pytest.org/2.0.0/usage.html for details.
-
-- new and better reporting information in assert expressions
-  if comparing lists, sequences or strings.
-
-  see http://pytest.org/2.0.0/assert.html#newreport
-
-- new configuration through ini-files (setup.cfg or tox.ini recognized),
-  for example::
-
-    [pytest]
-    norecursedirs = .hg data*  # don't ever recurse in such dirs
-    addopts = -x --pyargs      # add these command line options by default
-
-  see http://pytest.org/2.0.0/customize.html
-
-- improved standard unittest support.  In general py.test should now
-  better be able to run custom unittest.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 many more detailed improvements details
-
-Fixes
------------------------
-
-- fix issue126 - introduce py.test.set_trace() to trace execution via
-  PDB during the running of tests even if capturing is ongoing.
-- fix issue124 - make reporting more resilient against tests opening
-  files on filedescriptor 1 (stdout).
-- fix issue109 - sibling conftest.py files will not be loaded.
-  (and Directory collectors cannot be customized anymore from a Directory's
-  conftest.py - this needs to happen at least one level up).
-- fix issue88 (finding custom test nodes from command line arg)
-- fix issue93 stdout/stderr is captured while importing conftest.py
-- fix bug: unittest collected functions now also can have "pytestmark"
-  applied at class/module level
-
-Important 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.
-
-* 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
------------------------------
-
-- py.test.config is now only available if you are in a test run.
-
-- the following (mostly already deprecated) functionality was removed:
-
-  - removed support for Module/Class/... collection node definitions
-    in conftest.py files.  They will cause nothing special.
-  - removed support for calling the pre-1.0 collection API of "run()" and "join"
-  - removed reading option values from conftest.py files or env variables.
-    This can now be done much much better and easier through the ini-file
-    mechanism and the "addopts" entry in particular.
-  - removed the "disabled" attribute in test classes.  Use the skipping
-    and pytestmark mechanism to skip or xfail a test class.
-
-- 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
-  in contact.  We'll figure something out.
-
-  Note that pytest_collect_directory() is still called but
-  any return value will be ignored.  This allows to keep
-  old code working that performed for example "py.test.skip()"
-  in collect() to prevent recursion into directory trees
-  if a certain dependency or command line option is missing.
-
-
-see :ref:`changelog` for more detailed changes.

doc/ja/announce/release-2.0.1.txt

@@ -1,67 +0,0 @@
-py.test 2.0.1: bug fixes
-===========================================================================
-
-Welcome to pytest-2.0.1, a maintenance and bug fix release of pytest,
-a mature testing tool for Python, supporting CPython 2.4-3.2, Jython
-and latest PyPy interpreters.  See extensive docs with tested examples here:
-
-    http://pytest.org/
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Many thanks to all issue reporters and people asking questions or
-complaining.  Particular thanks to Floris Bruynooghe and Ronny Pfannschmidt
-for their great coding contributions and many others for feedback and help.
-
-best,
-holger krekel
-
-Changes between 2.0.0 and 2.0.1
-----------------------------------------------
-
-- refine and unify initial capturing so that it works nicely
-  even if the logging module is used on an early-loaded conftest.py
-  file or plugin.
-- fix issue12 - show plugin versions with "--version" and
-  "--traceconfig" and also document how to add extra information
-  to reporting test header
-- fix issue17 (import-* reporting issue on python3) by
-  requiring py>1.4.0 (1.4.1 is going to include it)
-- fix issue10 (numpy arrays truth checking) by refining
-  assertion interpretation in py lib
-- fix issue15: make nose compatibility tests compatible
-  with python3 (now that nose-1.0 supports python3)
-- remove somewhat surprising "same-conftest" detection because
-  it ignores conftest.py when they appear in several subdirs.
-- improve assertions ("not in"), thanks Floris Bruynooghe
-- improve behaviour/warnings when running on top of "python -OO"
-  (assertions and docstrings are turned off, leading to potential
-  false positives)
-- introduce a pytest_cmdline_processargs(args) hook
-  to allow dynamic computation of command line arguments.
-  This fixes a regression because py.test prior to 2.0
-  allowed to set command line options from conftest.py
-  files which so far pytest-2.0 only allowed from ini-files now.
-- fix issue7: assert failures in doctest modules.
-  unexpected failures in doctests will not generally
-  show nicer, i.e. within the doctest failing context.
-- fix issue9: setup/teardown functions for an xfail-marked
-  test will report as xfail if they fail but report as normally
-  passing (not xpassing) if they succeed.  This only is true
-  for "direct" setup/teardown invocations because teardown_class/
-  teardown_module cannot closely relate to a single test.
-- fix issue14: no logging errors at process exit
-- refinements to "collecting" output on non-ttys
-- refine internal plugin registration and --traceconfig output
-- introduce a mechanism to prevent/unregister plugins from the
-  command line, see http://pytest.org/plugins.html#cmdunregister
-- activate resultlog plugin by default
-- fix regression wrt yielded tests which due to the
-  collection-before-running semantics were not
-  setup as with pytest 1.3.4.  Note, however, that
-  the recommended and much cleaner way to do test
-  parametrization remains the "pytest_generate_tests"
-  mechanism, see the docs.

doc/ja/announce/release-2.0.2.txt

@@ -1,73 +0,0 @@
-py.test 2.0.2: bug fixes, improved xfail/skip expressions, speed ups
-===========================================================================
-
-Welcome to pytest-2.0.2, a maintenance and bug fix release of pytest,
-a mature testing tool for Python, supporting CPython 2.4-3.2, Jython
-and latest PyPy interpreters.  See the extensive docs with tested examples here:
-
-    http://pytest.org/
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Many thanks to all issue reporters and people asking questions
-or complaining, particularly Jurko for his insistence,
-Laura, Victor and Brianna for helping with improving
-and Ronny for his general advise.
-
-best,
-holger krekel
-
-Changes between 2.0.1 and 2.0.2
-----------------------------------------------
-
-- tackle issue32 - speed up test runs of very quick test functions
-  by reducing the relative overhead
-
-- fix issue30 - extended xfail/skipif handling and improved reporting.
-  If you have a syntax error in your skip/xfail
-  expressions you now get nice error reports.
-
-  Also you can now access module globals from xfail/skipif
-  expressions so that this for example works now::
-
-    import pytest
-    import mymodule
-    @pytest.mark.skipif("mymodule.__version__[0] == "1")
-    def test_function():
-        pass
-
-  This will not run the test function if the module's version string
-  does not start with a "1".  Note that specifying a string instead
-  of a boolean expressions allows py.test to report meaningful information
-  when summarizing a test run as to what conditions lead to skipping
-  (or xfail-ing) tests.
-
-- fix issue28 - setup_method and pytest_generate_tests work together
-  The setup_method fixture method now gets called also for
-  test function invocations generated from the pytest_generate_tests
-  hook.
-
-- fix issue27 - collectonly and keyword-selection (-k) now work together
-  Also, if you do "py.test --collectonly -q" you now get a flat list
-  of test ids that you can use to paste to the py.test commandline
-  in order to execute a particular test.
-
-- fix issue25 avoid reported problems with --pdb and python3.2/encodings output
-
-- fix issue23 - tmpdir argument now works on Python3.2 and WindowsXP
-  Starting with Python3.2 os.symlink may be supported. By requiring
-  a newer py lib version the py.path.local() implementation acknowledges
-  this.
-
-- fixed typos in the docs (thanks Victor Garcia, Brianna Laugher) and particular
-  thanks to Laura Creighton who also revieved parts of the documentation.
-
-- fix slighly wrong output of verbose progress reporting for classes
-  (thanks Amaury)
-
-- more precise (avoiding of) deprecation warnings for node.Class|Function accesses
-
-- avoid std unittest assertion helper code in tracebacks (thanks Ronny)

doc/ja/announce/release-2.0.3.txt

@@ -1,40 +0,0 @@
-py.test 2.0.3: bug fixes and speed ups 
-===========================================================================
-
-Welcome to pytest-2.0.3, a maintenance and bug fix release of pytest,
-a mature testing tool for Python, supporting CPython 2.4-3.2, Jython
-and latest PyPy interpreters.  See the extensive docs with tested examples here:
-
-    http://pytest.org/
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-There also is a bugfix release 1.6 of pytest-xdist, the plugin
-that enables seemless distributed and "looponfail" testing for Python.
-
-best,
-holger krekel
-
-Changes between 2.0.2 and 2.0.3
-----------------------------------------------
-
-- fix issue38: nicer tracebacks on calls to hooks, particularly early
-  configure/sessionstart ones
-
-- fix missing skip reason/meta information in junitxml files, reported
-  via http://lists.idyll.org/pipermail/testing-in-python/2011-March/003928.html
-
-- fix issue34: avoid collection failure with "test" prefixed classes
-  deriving from object.
-
-- don't require zlib (and other libs) for genscript plugin without
-  --genscript actually being used.
-
-- speed up skips (by not doing a full traceback represenation
-  internally)
-
-- fix issue37: avoid invalid characters in junitxml's output
-

doc/ja/announce/release-2.1.0.txt

@@ -1,47 +0,0 @@
-py.test 2.1.0: perfected assertions and bug fixes
-===========================================================================
-
-Welcome to the release of pytest-2.1, a mature testing tool for Python,
-supporting CPython 2.4-3.2, Jython and latest PyPy interpreters.  See
-the improved extensive docs (now also as PDF!) with tested examples here:
-
-     http://pytest.org/
-
-The single biggest news about this release are **perfected assertions**
-courtesy of Benjamin Peterson.  You can now safely use ``assert``
-statements in test modules without having to worry about side effects
-or python optimization ("-OO") options.  This is achieved by rewriting
-assert statements in test modules upon import, using a PEP302 hook.
-See http://pytest.org/assert.html#advanced-assertion-introspection for
-detailed information.  The work has been partly sponsored by my company,
-merlinux GmbH.
-
-For further details on bug fixes and smaller enhancements see below.
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-best,
-holger krekel / http://merlinux.eu
-
-Changes between 2.0.3 and 2.1.0
-----------------------------------------------
-
-- fix issue53 call nosestyle setup functions with correct ordering
-- fix issue58 and issue59: new assertion code fixes
-- merge Benjamin's assertionrewrite branch: now assertions
-  for test modules on python 2.6 and above are done by rewriting
-  the AST and saving the pyc file before the test module is imported.
-  see doc/assert.txt for more info.
-- fix issue43: improve doctests with better traceback reporting on
-  unexpected exceptions
-- fix issue47: timing output in junitxml for test cases is now correct
-- fix issue48: typo in MarkInfo repr leading to exception
-- fix issue49: avoid confusing error when initialization partially fails
-- fix issue44: env/username expansion for junitxml file path
-- show releaselevel information in test runs for pypy
-- reworked doc pages for better navigation and PDF generation
-- report KeyboardInterrupt even if interrupted during session startup
-- fix issue 35 - provide PDF doc version and download link from index page

doc/ja/announce/release-2.1.1.txt

@@ -1,37 +0,0 @@
-py.test 2.1.1: assertion fixes and improved junitxml output
-===========================================================================
-
-pytest-2.1.1 is a backward compatible maintenance release of the
-popular py.test testing tool.  See extensive docs with examples here:
-
-     http://pytest.org/
-
-Most bug fixes address remaining issues with the perfected assertions
-introduced with 2.1.0 - many thanks to the bug reporters and to Benjamin
-Peterson for helping to fix them.  Also, junitxml output now produces
-system-out/err tags which lead to better displays of tracebacks with Jenkins.
-
-Also a quick note to package maintainers and others interested: there now
-is a "pytest" man page which can be generated with "make man" in doc/.
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-best,
-holger krekel / http://merlinux.eu
-
-Changes between 2.1.0 and 2.1.1
-----------------------------------------------
-
-- fix issue64 / pytest.set_trace now works within pytest_generate_tests hooks
-- fix issue60 / fix error conditions involving the creation of __pycache__
-- fix issue63 / assertion rewriting on inserts involving strings containing '%'
-- fix assertion rewriting on calls with a ** arg
-- don't cache rewritten modules if bytecode generation is disabled
-- fix assertion rewriting in read-only directories
-- fix issue59: provide system-out/err tags for junitxml output
-- fix issue61: assertion rewriting on boolean operations with 3 or more operands
-- you can now build a man page with "cd doc ; make man"
-

doc/ja/announce/release-2.1.2.txt

@@ -1,33 +0,0 @@
-py.test 2.1.2: bug fixes and fixes for jython
-===========================================================================
-
-pytest-2.1.2 is a minor backward compatible maintenance release of the
-popular py.test testing tool.  pytest is commonly used for unit,
-functional- and integration testing.  See extensive docs with examples
-here:
-
-     http://pytest.org/
-
-Most bug fixes address remaining issues with the perfected assertions
-introduced in the 2.1 series - many thanks to the bug reporters and to Benjamin
-Peterson for helping to fix them.  pytest should also work better with
-Jython-2.5.1 (and Jython trunk).
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-best,
-holger krekel / http://merlinux.eu
-
-Changes between 2.1.1 and 2.1.2
-----------------------------------------
-
-- fix assertion rewriting on files with windows newlines on some Python versions
-- refine test discovery by package/module name (--pyargs), thanks Florian Mayer
-- fix issue69 / assertion rewriting fixed on some boolean operations
-- fix issue68 / packages now work with assertion rewriting
-- fix issue66: use different assertion rewriting caches when the -O option is passed
-- don't try assertion rewriting on Jython, use reinterp
-

doc/ja/announce/release-2.1.3.txt

@@ -1,32 +0,0 @@
-py.test 2.1.3: just some more fixes
-===========================================================================
-
-pytest-2.1.3 is a minor backward compatible maintenance release of the
-popular py.test testing tool.  It is commonly used for unit, functional-
-and integration testing.  See extensive docs with examples here:
-
-     http://pytest.org/
-
-The release contains another fix to the perfected assertions introduced
-with the 2.1 series as well as the new possibility to customize reporting
-for assertion expressions on a per-directory level.  
-
-If you want to install or upgrade pytest, just type one of::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Thanks to the bug reporters and to Ronny Pfannschmidt, Benjamin Peterson
-and Floris Bruynooghe who implemented the fixes.
-
-best,
-holger krekel
-
-Changes between 2.1.2 and 2.1.3
-----------------------------------------
-
-- fix issue79: assertion rewriting failed on some comparisons in boolops,
-- correctly handle zero length arguments (a la pytest '')
-- fix issue67 / junitxml now contains correct test durations
-- fix issue75 / skipping test failure on jython
-- fix issue77 / Allow assertrepr_compare hook to apply to a subset of tests

doc/ja/announce/release-2.2.0.txt

@@ -1,95 +0,0 @@
-py.test 2.2.0: test marking++, parametrization++ and duration profiling
-===========================================================================
-
-pytest-2.2.0 is a test-suite compatible release of the popular
-py.test testing tool.  Plugins might need upgrades. It comes
-with these improvements:
-
-* easier and more powerful parametrization of tests:
-
-  - new @pytest.mark.parametrize decorator to run tests with different arguments
-  - new metafunc.parametrize() API for parametrizing arguments independently
-  - see examples at http://pytest.org/latest/example/parametrize.html
-  - NOTE that parametrize() related APIs are still a bit experimental
-    and might change in future releases.
-
-* improved handling of test markers and refined marking mechanism:
-
-  - "-m markexpr" option for selecting tests according to their mark
-  - a new "markers" ini-variable for registering test markers for your project
-  - the new "--strict" bails out with an error if using unregistered markers.
-  - see examples at http://pytest.org/latest/example/markers.html
-
-* duration profiling: new "--duration=N" option showing the N slowest test
-  execution or setup/teardown calls. This is most useful if you want to
-  find out where your slowest test code is.
-
-* also 2.2.0 performs more eager calling of teardown/finalizers functions
-  resulting in better and more accurate reporting when they fail
-
-Besides there is the usual set of bug fixes along with a cleanup of
-pytest's own test suite allowing it to run on a wider range of environments.
-
-For general information, see extensive docs with examples here:
-
-     http://pytest.org/
-
-If you want to install or upgrade pytest you might just type::
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Thanks to Ronny Pfannschmidt, David Burns, Jeff Donner, Daniel Nouri, Alfredo Deza and all who gave feedback or sent bug reports.
-
-best,
-holger krekel
-
-
-notes on incompatibility
-------------------------------
-
-While test suites should work unchanged you might need to upgrade plugins:
-
-* You need a new version of the pytest-xdist plugin (1.7) for distributing
-  test runs.
-
-* Other plugins might need an upgrade if they implement
-  the ``pytest_runtest_logreport`` hook which now is called unconditionally
-  for the setup/teardown fixture phases of a test. You may choose to
-  ignore setup/teardown failures by inserting "if rep.when != 'call': return"
-  or something similar. Note that most code probably "just" works because
-  the hook was already called for failing setup/teardown phases of a test
-  so a plugin should have been ready to grok such reports already.
-
-
-Changes between 2.1.3 and 2.2.0
-----------------------------------------
-
-- fix issue90: introduce eager tearing down of test items so that
-  teardown function are called earlier.
-- add an all-powerful metafunc.parametrize function which allows to
-  parametrize test function arguments in multiple steps and therefore
-  from independent plugins and places.
-- add a @pytest.mark.parametrize helper which allows to easily
-  call a test function with different argument values.
-- Add examples to the "parametrize" example page, including a quick port
-  of Test scenarios and the new parametrize function and decorator.
-- introduce registration for "pytest.mark.*" helpers via ini-files
-  or through plugin hooks.  Also introduce a "--strict" option which
-  will treat unregistered markers as errors
-  allowing to avoid typos and maintain a well described set of markers
-  for your test suite.  See examples at http://pytest.org/latest/mark.html
-  and its links.
-- issue50: introduce "-m marker" option to select tests based on markers
-  (this is a stricter and more predictable version of "-k" in that "-m"
-  only matches complete markers and has more obvious rules for and/or
-  semantics.
-- new feature to help optimizing the speed of your tests:
-  --durations=N option for displaying N slowest test calls
-  and setup/teardown methods.
-- fix issue87: --pastebin now works with python3
-- fix issue89: --pdb with unexpected exceptions in doctest work more sensibly
-- fix and cleanup pytest's own test suite to not leak FDs
-- fix issue83: link to generated funcarg list
-- fix issue74: pyarg module names are now checked against imp.find_module false positives
-- fix compatibility with twisted/trial-11.1.0 use cases

doc/ja/announce/release-2.2.1.txt

@@ -1,41 +0,0 @@
-pytest-2.2.1: bug fixes, perfect teardowns
-===========================================================================
-
-
-pytest-2.2.1 is a minor backward-compatible release of the the py.test
-testing tool.   It contains bug fixes and little improvements, including
-documentation fixes.  If you are using the distributed testing
-pluginmake sure to upgrade it to pytest-xdist-1.8.
-
-For general information see here:
-
-     http://pytest.org/
-
-To install or upgrade pytest:
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Special thanks for helping on this release to Ronny Pfannschmidt, Jurko
-Gospodnetic and Ralf Schmitt.
-
-best,
-holger krekel
-
-
-Changes between 2.2.0 and 2.2.1
-----------------------------------------
-
-- fix issue99 (in pytest and py) internallerrors with resultlog now
-  produce better output - fixed by normalizing pytest_internalerror 
-  input arguments.
-- fix issue97 / traceback issues (in pytest and py) improve traceback output
-  in conjunction with jinja2 and cython which hack tracebacks
-- fix issue93 (in pytest and pytest-xdist) avoid "delayed teardowns":
-  the final test in a test node will now run its teardown directly
-  instead of waiting for the end of the session. Thanks Dave Hunt for
-  the good reporting and feedback.  The pytest_runtest_protocol as well
-  as the pytest_runtest_teardown hooks now have "nextitem" available 
-  which will be None indicating the end of the test run.
-- fix collection crash due to unknown-source collected items, thanks
-  to Ralf Schmitt (fixed by depending on a more recent pylib)

doc/ja/announce/release-2.2.2.txt

@@ -1,43 +0,0 @@
-pytest-2.2.2: bug fixes
-===========================================================================
-
-pytest-2.2.2 (updated to 2.2.3 to fix packaging issues) is a minor
-backward-compatible release of the versatile py.test testing tool.   It
-contains bug fixes and a few refinements particularly to reporting with
-"--collectonly", see below for betails.  
-
-For general information see here:
-
-     http://pytest.org/
-
-To install or upgrade pytest:
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Special thanks for helping on this release to Ronny Pfannschmidt
-and Ralf Schmitt and the contributors of issues.
-
-best,
-holger krekel
-
-
-Changes between 2.2.1 and 2.2.2
-----------------------------------------
-
-- fix issue101: wrong args to unittest.TestCase test function now
-  produce better output
-- fix issue102: report more useful errors and hints for when a 
-  test directory was renamed and some pyc/__pycache__ remain
-- fix issue106: allow parametrize to be applied multiple times
-  e.g. from module, class and at function level.
-- fix issue107: actually perform session scope finalization
-- don't check in parametrize if indirect parameters are funcarg names
-- add chdir method to monkeypatch funcarg
-- fix crash resulting from calling monkeypatch undo a second time
-- fix issue115: make --collectonly robust against early failure
-  (missing files/directories)
-- "-qq --collectonly" now shows only files and the number of tests in them
-- "-q --collectonly" now shows test ids 
-- allow adding of attributes to test reports such that it also works
-  with distributed testing (no upgrade of pytest-xdist needed)

doc/ja/announce/release-2.2.4.txt

@@ -1,39 +0,0 @@
-pytest-2.2.4: bug fixes, better junitxml/unittest/python3 compat
-===========================================================================
-
-pytest-2.2.4 is a minor backward-compatible release of the versatile
-py.test testing tool.   It contains bug fixes and a few refinements
-to junitxml reporting, better unittest- and python3 compatibility.
-
-For general information see here:
-
-     http://pytest.org/
-
-To install or upgrade pytest:
-
-    pip install -U pytest # or
-    easy_install -U pytest
-
-Special thanks for helping on this release to Ronny Pfannschmidt
-and Benjamin Peterson and the contributors of issues.
-
-best,
-holger krekel
-
-Changes between 2.2.3 and 2.2.4
------------------------------------
-
-- fix error message for rewritten assertions involving the % operator
-- fix issue 126: correctly match all invalid xml characters for junitxml
-  binary escape
-- fix issue with unittest: now @unittest.expectedFailure markers should
-  be processed correctly (you can also use @pytest.mark markers)
-- document integration with the extended distribute/setuptools test commands
-- fix issue 140: propperly get the real functions
-  of bound classmethods for setup/teardown_class
-- fix issue #141: switch from the deceased paste.pocoo.org to bpaste.net
-- fix issue #143: call unconfigure/sessionfinish always when
-  configure/sessionstart where called
-- fix issue #144: better mangle test ids to junitxml classnames
-- upgrade distribute_setup.py to 0.6.27
-

doc/ja/apiref.txt

@@ -1,29 +0,0 @@
-
-.. _apiref:
-
-py.test リファレンスドキュメント
-================================
-
-..
-    py.test reference documentation
-    ================================================
-
-.. toctree::
-   :maxdepth: 2
-
-   builtin.txt
-   customize.txt
-   assert.txt
-   funcargs.txt
-   xunit_setup.txt
-   capture.txt
-   monkeypatch.txt
-   xdist.txt
-   tmpdir.txt
-   skipping.txt
-   mark.txt
-   recwarn.txt
-   unittest.txt
-   nose.txt
-   doctest.txt
-

doc/ja/assert.txt

@@ -1,362 +0,0 @@
-
-..
-    The writing and reporting of assertions in tests
-    ==================================================
-
-テストのアサーションにおける書き込みとレポート
-==============================================
-
-.. _`assert with the assert statement`:
-
-``assert`` 文によるアサーション
--------------------------------
-
-..
-    Asserting with the ``assert`` statement
-    ---------------------------------------------------------
-
-..
-    ``py.test`` allows you to use the standard python ``assert`` for verifying
-    expectations and values in Python tests.  For example, you can write the
-    following::
-
-``py.test`` は、テストで期待値と実際の値を検証するのに Python 標準の ``assert`` 文が使えます。例えば、次のようにテストを作成します::
-
-    # test_assert1.py の内容
-    def f():
-        return 3
-
-    def test_function():
-        assert f() == 4
-
-..
-    to assert that your function returns a certain value. If this assertion fails
-    you will see the return value of the function call::
-
-このサンプルは、関数が特定の値を返すのをアサートします。このアサーションが失敗した場合、関数呼び出しの返り値が表示されます::
-
-    $ py.test test_assert1.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_assert1.py F
-    
-    ================================= FAILURES =================================
-    ______________________________ test_function _______________________________
-    
-        def test_function():
-    >       assert f() == 4
-    E       assert 3 == 4
-    E        +  where 3 = f()
-    
-    test_assert1.py:5: AssertionError
-    ========================= 1 failed in 0.01 seconds =========================
-
-..
-    py.test has support for showing the values of the most common subexpressions
-    including calls, attributes, comparisons, and binary and unary
-    operators. (See :ref:`tbreportdemo`).  This allows you to use the
-    idiomatic python constructs without boilerplate code while not losing
-    introspection information.
-
-py.test は、関数呼び出し、属性、比較、バイナリや単項演算子といった処理を含む通常の部分式の値を表示する機能があります (:ref:`tbreportdemo` を参照) 。この機能により、定型的なコードを必要とせず、Python イディオム的な概念も利用できます。その上でイントロスペクション情報を失うこともありません。
-
-..
-    However, if you specify a message with the assertion like this::
-
-但し、次のようにアサーションと一緒にメッセージを指定した場合::
-
-    assert a % 2 == 0, "value was odd, should be even"
-
-..
-    then no assertion introspection takes places at all and the message
-    will be simply shown in the traceback.
-
-そこでアサートイントロスペクションを行わず、このメッセージは単純にトレースバックで表示されます。
-
-..
-    See :ref:`assert-details` for more information on assertion introspection.
-
-アサートイントロスペクションの詳細については :ref:`assert-details` を参照してください。
-
-..
-    Assertions about expected exceptions
-    ------------------------------------------
-
-例外発生を期待するアサーション
-------------------------------
-
-..
-    In order to write assertions about raised exceptions, you can use
-    ``pytest.raises`` as a context manager like this::
-
-発生した例外のアサーションを行うには、次のようにコンテキスト マネージャーとして ``pytest.raises`` を使います::
-
-    import pytest
-    with pytest.raises(ZeroDivisionError):
-        1 / 0
-
-..
-    and if you need to have access to the actual exception info you may use::
-
-もし実際の例外の情報を調べる必要があるなら、次のように行います::
-
-    with pytest.raises(RuntimeError) as excinfo:
-        def f():
-            f()
-        f()
-
-    # excinfo.type, excinfo.value, excinfo.traceback といった関連する値を確認する
-
-..
-    If you want to write test code that works on Python 2.4 as well,
-    you may also use two other ways to test for an expected exception::
-
-Python 2.4 でも同じように動作するテストコードを書きたいなら、例外発生を期待するテストを行う別の方法が2つあります::
-
-    pytest.raises(ExpectedException, func, *args, **kwargs)
-    pytest.raises(ExpectedException, "func(*args, **kwargs)")
-
-..
-    both of which execute the specified function with args and kwargs and
-    asserts that the given ``ExpectedException`` is raised.  The reporter will
-    provide you with helpful output in case of failures such as *no
-    exception* or *wrong exception*.
-
-両方とも指定した関数へ args と kwargs を渡して実行し、引数として与えた ``ExpectedException`` が発生することをアサートします。このレポートは *no exception* または *wrong exception* といったテストに失敗したときに分かりやすい内容を表示します。
-
-.. _newreport:
-
-コンテキストに依存した内容の比較
---------------------------------
-
-..
-    Making use of context-sensitive comparisons
-    -------------------------------------------------
-
-.. versionadded:: 2.0
-
-..
-    py.test has rich support for providing context-sensitive information
-    when it encounters comparisons.  For example::
-
-py.test は、比較するときにコンテキスト依存の情報を分かりやすく表示します。例えば、::
-
-    # test_assert2.py の内容
-
-    def test_set_comparison():
-        set1 = set("1308")
-        set2 = set("8035")
-        assert set1 == set2
-
-..
-    if you run this module::
-
-このモジュールを実行すると::
-
-    $ py.test test_assert2.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_assert2.py F
-    
-    ================================= FAILURES =================================
-    ___________________________ test_set_comparison ____________________________
-    
-        def test_set_comparison():
-            set1 = set("1308")
-            set2 = set("8035")
-    >       assert set1 == set2
-    E       assert set(['0', '1', '3', '8']) == set(['0', '3', '5', '8'])
-    E         Extra items in the left set:
-    E         '1'
-    E         Extra items in the right set:
-    E         '5'
-    
-    test_assert2.py:5: AssertionError
-    ========================= 1 failed in 0.01 seconds =========================
-
-..
-    Special comparisons are done for a number of cases:
-
-複数のケースにおいて、特別な比較が行われます:
-
-..
-    * comparing long strings: a context diff is shown
-    * comparing long sequences: first failing indices
-    * comparing dicts: different entries
-
-* 長い文字列の比較: コンテキスト diff を表示
-* 長いシーケンスの比較: 最初に失敗したインデックス
-* ディクショナリの比較: 異なるエントリ
-
-..
-    See the :ref:`reporting demo <tbreportdemo>` for many more examples.
-
-より多くのサンプルについては :ref:`レポートのデモ <tbreportdemo>` 参照してください。
-
-..
-    Defining your own assertion comparison
-    ----------------------------------------------
-
-アサーション比較の定義
-----------------------
-
-..
-    It is possible to add your own detailed explanations by implementing
-    the ``pytest_assertrepr_compare`` hook.
-
-``pytest_assertrepr_compare`` フックを実装することで独自の詳細説明を追加できます。
-
-.. autofunction:: _pytest.hookspec.pytest_assertrepr_compare
-
-..
-    As an example consider adding the following hook in a conftest.py which
-    provides an alternative explanation for ``Foo`` objects::
-
-例として、conftest.py に次のフックを追加してみます。これは ``Foo`` オブジェクトの別の説明を提供します::
-
-   # conftest.py の内容
-   from test_foocompare import Foo
-   def pytest_assertrepr_compare(op, left, right):
-       if isinstance(left, Foo) and isinstance(right, Foo) and op == "==":
-        return ['Comparing Foo instances:',
-                  '   vals: %s != %s' % (left.val, right.val)]
-
-..
-    now, given this test module::
-
-ここで次のテストモジュールがあります::
-
-   # test_foocompare.py の内容
-   class Foo:
-       def __init__(self, val):
-            self.val = val
-
-   def test_compare():
-       f1 = Foo(1)
-       f2 = Foo(2)
-       assert f1 == f2
-
-..
-    you can run the test module and get the custom output defined in 
-    the conftest file::
-
-このテストモジュールを実行すると、conftest ファイルで定義した独自の出力内容が表示されます::
-
-   $ py.test -q test_foocompare.py
-   collecting ... collected 1 items
-   F
-   ================================= FAILURES =================================
-   _______________________________ test_compare _______________________________
-   
-       def test_compare():
-           f1 = Foo(1)
-           f2 = Foo(2)
-   >       assert f1 == f2
-   E       assert Comparing Foo instances:
-   E            vals: 1 != 2
-   
-   test_foocompare.py:8: AssertionError
-   1 failed in 0.01 seconds
-
-.. _assert-details:
-.. _`assert introspection`:
-
-高度なアサートイントロスペクション
-----------------------------------
-
-..
-    Advanced assertion introspection
-    ----------------------------------
-
-.. versionadded:: 2.1
-
-..
-    Reporting details about a failing assertion is achieved either by rewriting
-    assert statements before they are run or re-evaluating the assert expression and
-    recording the intermediate values. Which technique is used depends on the
-    location of the assert, py.test's configuration, and Python version being used
-    to run py.test.  Note that for assert statements with a manually provided
-    message, i.e. ``assert expr, message``, no assertion introspection takes place
-    and the manually provided message will be rendered in tracebacks.
-
-失敗するアサーションに関する詳細のレポートは、実行前に assert 文を書き換えるか、または assert 式を再評価して中間値を記録するかのどちらかの方法で行われます。どちらの方法を使うかは assert の位置、pytest の設定、pytest を実行するのに使われる Python バージョンに依存します。 ``assert expr, message`` のように直接コード内でメッセージを記述した assert 文は、アサートイントロスペクションが行われず、指定したメッセージがトレースバックに表示されることに注意してください。
-
-..
-    By default, if the Python version is greater than or equal to 2.6, py.test
-    rewrites assert statements in test modules. Rewritten assert statements put
-    introspection information into the assertion failure message. py.test only
-    rewrites test modules directly discovered by its test collection process, so
-    asserts in supporting modules which are not themselves test modules will not be
-    rewritten.
-
-デフォルトでは、Python バージョンが 2.6 以上の場合、py.test はテストモジュールの assert 文を書き換えます。書き換えられた assert 文は、イントロスペクション情報をアサーションの失敗メッセージに追加します。py.test は、テストコレクション処理で検出したテストモジュールのみを直接書き換えます。そのため、テストモジュールではないサポートライブラリの assert 文は書き換えられません。
-
-.. note::
-
-   ..
-       py.test rewrites test modules on import. It does this by using an import hook
-       to write a new pyc files. Most of the time this works transparently. However,
-       if you are messing with import yourself, the import hook may interfere. If
-       this is the case, simply use ``--assert=reinterp`` or
-       ``--assert=plain``. Additionally, rewriting will fail silently if it cannot
-       write new pycs, i.e. in a read-only filesystem or a zipfile.
-
-   py.test は、インポート時にテストモジュールを書き換えます。新たに pyc ファイルを書き込むためにインポートフックを使うことでこの処理を行います。この処理はほとんど透過的に行われます。但し、自分でインポートを行ってごちゃごちゃになっている場合、そのインポートフックがインターフェースになる可能性があります。このようなケースでは、単純に ``--assert=reinterp`` か ``--assert=plain`` を使ってください。さらに、新たに pyc ファイルを書き込めない場合、書き換えはサイレントモードで失敗します。例えば、読み込み専用ファイルシステムや zip ファイルで行うようなときです。
-
-..
-    If an assert statement has not been rewritten or the Python version is less than
-    2.6, py.test falls back on assert reinterpretation. In assert reinterpretation,
-    py.test walks the frame of the function containing the assert statement to
-    discover sub-expression results of the failing assert statement. You can force
-    py.test to always use assertion reinterpretation by passing the
-    ``--assert=reinterp`` option.
-
-assert 文が書き換えられない、または Python バージョン 2.6 よりも小さい場合、py.test はアサーションの再解釈を行います。アサーションの再解釈では、py.test が、assert 文の失敗する部分式を見つけるために assert 文を含む関数のフレームを辿ります。py.test にアサーションの再解釈を行うよう強制するには ``--assert=reinterp`` オプションを指定します。
-
-..
-    Assert reinterpretation has a caveat not present with assert rewriting: If
-    evaluating the assert expression has side effects you may get a warning that the
-    intermediate values could not be determined safely.  A common example of this
-    issue is an assertion which reads from a file::
-
-アサーションの再解釈は、assert 文の書き換えを行わないことの注意が必要です: それは assert 式の評価が副作用をもつ場合、中間値が安全に決定しないという警告を受け取るかもしれません。この問題の一般的な例として、ファイルを読み込むアサーションがあります::
-
-        assert f.read() != '...'
-
-..
-    If this assertion fails then the re-evaluation will probably succeed!
-    This is because ``f.read()`` will return an empty string when it is
-    called the second time during the re-evaluation.  However, it is
-    easy to rewrite the assertion and avoid any trouble::
-
-このアサーションが失敗した場合、その再評価はおそらく成功します！つまり再評価において2回目に呼び出されたときに ``f.read()`` が空の文字列を返すからです。とはいえ、このアサーションを書き換えて、そういったトラブルを避けるのは簡単です::
-
-        content = f.read()
-        assert content != '...'
-
-..
-    All assert introspection can be turned off by passing ``--assert=plain``.
-
-全てのアサートイントロスペクションを無効にするには ``--assert=plain`` を指定します。
-
-..
-    For further information, Benjamin Peterson wrote up `Behind the scenes of py.test's new assertion rewriting <http://pybites.blogspot.com/2011/07/behind-scenes-of-pytests-new-assertion.html>`_.
-
-詳細については、Benjamin Peterson が詳しくまとめた `Behind the scenes of py.test's new assertion rewriting <http://pybites.blogspot.com/2011/07/behind-scenes-of-pytests-new-assertion.html>`_ を参照してください。
-
-..
-    Add assert rewriting as an alternate introspection technique.
-
-.. versionadded:: 2.1
-   代替イントロスペクション手法として assert 書き換え機能を追加
-
-..
-   Introduce the ``--assert`` option. Deprecate ``--no-assert`` and
-   ``--nomagic``.
-
-.. versionchanged:: 2.1
-   ``--assert`` オプションを追加。 ``--no-assert`` と ``--nomagic`` を廃止。

doc/ja/builtin.txt

@@ -1,152 +0,0 @@
-
-.. _`pytest helpers`:
-
-Pytest 組み込みヘルパー機能
-===========================
-
-..
-    Pytest builtin helpers
-    ================================================
-
-..
-    builtin pytest.* functions and helping objects
-    -----------------------------------------------------
-
-組み込みの pytest.* 関数とヘルパーオブジェクト
-----------------------------------------------
-
-..
-    You can always use an interactive Python prompt and type::
-
-Python インタープリターの対話モードから次のように入力すると::
-
-    import pytest
-    help(pytest)
-
-..
-    to get an overview on the globally available helpers.
-
-グローバルに利用できるヘルパー機能の概要を把握できます。
-
-.. automodule:: pytest
-    :members:
-
-
-.. _builtinfuncargs:
-
-組み込み関数の引数
-------------------
-
-..
-    Builtin function arguments
-    -----------------------------------------------------
-
-..
-    You can ask for available builtin or project-custom
-    :ref:`function arguments <funcargs>` by typing::
-
-次のように入力して、利用できる組み込みまたはプロジェクトカスタムの :ref:`関数の引数 <funcargs>` を確認できます。
-
-    | $ py.test --fixtures
-    | ====================== test session starts =======================
-    | platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    | collected 0 items
-    | pytestconfig
-    |     pytest の config オブジェクトとコマンドラインオプションへのアクセス
-    |
-    | capsys
-    |     sys.stdout/sys.stderr への書き込み内容を取得できる
-    |     キャプチャした出力内容は ``(out, err)`` のタプルを返す
-    |     ``capsys.readouterr()`` メソッドで利用できる
-    |
-    | capfd
-    |     ファイルディスクリプタ 1 と 2 へ書き込み内容を取得できる
-    |     キャプチャした出力内容は ``(out, err)`` のタプルを返す
-    |     ``capsys.readouterr()`` メソッドで利用できる
-    |
-    | tmpdir
-    |     基本となる一時ディレクトリ配下にサブディレクトリを作成して、
-    |     テスト関数の実行毎に一意な一時ディレクトリのオブジェクトを返す
-    |     これは py.path.local のパスオブジェクトが返される
-    |
-    | monkeypatch
-    |     オブジェクト、ディクショナリ、os.environ を変更する
-    |     次のヘルパーメソッドを提供する ``monkeypatch`` オブジェクトが返される
-    |     
-    |     monkeypatch.setattr(obj, name, value, raising=True)
-    |     monkeypatch.delattr(obj, name, raising=True)
-    |     monkeypatch.setitem(mapping, name, value)
-    |     monkeypatch.delitem(obj, name, raising=True)
-    |     monkeypatch.setenv(name, value, prepend=False)
-    |     monkeypatch.delenv(name, value, raising=True)
-    |     monkeypatch.syspath_prepend(path)
-    |     monkeypatch.chdir(path)
-    |    
-    |     全ての変更はテスト関数の呼び出しが終わった後で元に戻ります
-    |     ``raising`` パラメーターは、セット／削除の操作対象がないときに
-    |     KeyError や AttributeError を発生させるかどうかを決めます
-    |
-    | recwarn
-    |     次のメソッドを提供する WarningsRecorder インスタンスを返す
-    |     
-    |     * ``pop(category=None)``: category に一致する最後の警告を返す
-    |     * ``clear()``: 警告のリストを削除する
-    |     
-    |     警告については http://docs.python.org/library/warnings.html を
-    |     参照してください
-    |
-    | ========================  in 0.00 seconds ========================
-
-..
-        $ py.test --fixtures
-        =========================== test session starts ============================
-        platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-        collected 0 items
-        pytestconfig
-            the pytest config object with access to command line opts.
-        capsys
-            enables capturing of writes to sys.stdout/sys.stderr and makes
-            captured output available via ``capsys.readouterr()`` method calls
-            which return a ``(out, err)`` tuple.
-            
-        capfd
-            enables capturing of writes to file descriptors 1 and 2 and makes
-            captured output available via ``capsys.readouterr()`` method calls
-            which return a ``(out, err)`` tuple.
-            
-        tmpdir
-            return a temporary directory path object
-            which is unique to each test function invocation,
-            created as a sub directory of the base temporary
-            directory.  The returned object is a `py.path.local`_
-            path object.
-            
-        monkeypatch
-            The returned ``monkeypatch`` funcarg provides these
-            helper methods to modify objects, dictionaries or os.environ::
-            
-            monkeypatch.setattr(obj, name, value, raising=True)
-            monkeypatch.delattr(obj, name, raising=True)
-            monkeypatch.setitem(mapping, name, value)
-            monkeypatch.delitem(obj, name, raising=True)
-            monkeypatch.setenv(name, value, prepend=False)
-            monkeypatch.delenv(name, value, raising=True)
-            monkeypatch.syspath_prepend(path)
-            monkeypatch.chdir(path)
-            
-            All modifications will be undone after the requesting
-            test function has finished. The ``raising``
-            parameter determines if a KeyError or AttributeError
-            will be raised if the set/deletion operation has no target.
-            
-        recwarn
-            Return a WarningsRecorder instance that provides these methods:
-            
-            * ``pop(category=None)``: return last warning matching the category.
-            * ``clear()``: clear list of warnings
-            
-            See http://docs.python.org/library/warnings.html for information
-            on warning categories.
-            
-        
-        =============================  in 0.00 seconds =============================

doc/ja/capture.txt

@@ -1,170 +0,0 @@
-
-.. _`captures`:
-
-標準出力/標準エラーのキャプチャ
-===============================
-
-..
-    Capturing of the stdout/stderr output
-    =========================================================
-
-..
-    Default stdout/stderr/stdin capturing behaviour
-    ---------------------------------------------------------
-
-デフォルトの stdout/stderr/stdin のキャプチャ処理
--------------------------------------------------
-
-..
-    During test execution any output sent to ``stdout`` and ``stderr`` is
-    captured.  If a test or a setup method fails its according captured
-    output will usually be shown along with the failure traceback.
-
-テストの実行中 ``stdout`` と ``stderr`` へ送られる全ての出力内容はキャプチャされます。テストまたはセットアップメソッドが失敗した場合、そこでキャプチャされた出力は、通常、エラートレースバックと一緒に表示されます。
-
-..
-    In addition, ``stdin`` is set to a "null" object which will
-    fail on attempts to read from it because it is rarely desired
-    to wait for interactive input when running automated tests.
-
-加えて ``stdin`` は、その読み込みに失敗する "null" オブジェクトがセットされます。その理由は自動テストを実行するときに対話式の入力を待つのを考慮することはほとんどないからです。
-
-..
-    By default capturing is done by intercepting writes to low level
-    file descriptors.  This allows to capture output from simple
-    print statements as well as output from a subprocess started by
-    a test.
-
-デフォルトのキャプチャは、低レベルのファイルディスクリプタへの書き込みを横取りします。単純な print 文からの出力も、あるテストが生成したサブプロセスからの出力も同じようにキャプチャできます。
-
-..
-    Setting capturing methods or disabling capturing
-    -------------------------------------------------
-
-メソッドをキャプチャする、または無効にする設定
-----------------------------------------------
-
-..
-    There are two ways in which ``py.test`` can perform capturing:
-
-``py.test`` でキャプチャを実行する方法が2つあります:
-
-..
-    * file descriptor (FD) level capturing (default): All writes going to the
-      operating system file descriptors 1 and 2 will be captured.
-
-* ファイルディスクリプタ (FD) レベルのキャプチャ (デフォルト): オペレーティングシステムのファイルディスクリプタ1と2への全ての書き込みをキャプチャする
-
-..
-    * ``sys`` level capturing: Only writes to Python files ``sys.stdout``
-      and ``sys.stderr`` will be captured.  No capturing of writes to
-      filedescriptors is performed.
-
-* ``sys`` レベルのキャプチャ: Python ファイル ``sys.stdout`` と ``sys.stderr`` への書き込みのみキャプチャする、ファイルディスクリプタへの書き込みはキャプチャしない
-
-..
-    You can influence output capturing mechanisms from the command line::
-
-.. _`disable capturing`:
-
-コマンドラインから出力内容のキャプチャ設定を制御できます::
-
-    py.test -s            # 全てのキャプチャを無効にする
-    py.test --capture=sys # sys.stdout/stderr を in-mem ファイルに置き換える
-    py.test --capture=fd  # ファイルディスクリプタ1と2を一時ファイルに差し向ける
-
-.. _printdebugging:
-
-デバッグに print 文を使う
--------------------------
-
-..
-    Using print statements for debugging
-    ---------------------------------------------------
-
-..
-    One primary benefit of the default capturing of stdout/stderr output
-    is that you can use print statements for debugging::
-
-デフォルトで stdout/stderr の出力をキャプチャする主な利点の1つとして、デバッグに print 文が使えます::
-
-    # test_module.py の内容
-    def setup_function(function):
-        print ("setting up %s" % function)
-
-    def test_func1():
-        assert True
-
-    def test_func2():
-        assert False
-
-..
-    and running this module will show you precisely the output
-    of the failing function and hide the other one::
-
-このモジュールを実行すると、失敗するテスト関数の出力を適切に表示して、成功するもう1つのテストを非表示にします::
-
-    $ py.test
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    
-    test_module.py .F
-    
-    ================================= FAILURES =================================
-    ________________________________ test_func2 ________________________________
-    
-        def test_func2():
-    >       assert False
-    E       assert False
-    
-    test_module.py:9: AssertionError
-    ----------------------------- Captured stdout ------------------------------
-    setting up <function test_func2 at 0x20160c8>
-    ==================== 1 failed, 1 passed in 0.01 seconds ====================
-
-..
-    Accessing captured output from a test function
-    ---------------------------------------------------
-
-テスト関数からキャプチャされた出力へのアクセス
-----------------------------------------------
-
-..
-    The :ref:`funcarg mechanism` allows test function a very easy
-    way to access the captured output by simply using the names
-    ``capsys`` or ``capfd`` in the test function signature.  Here
-    is an example test function that performs some output related
-    checks::
-
-:ref:`funcarg mechanism` により、テスト関数のシグネチャに ``capsys`` または ``capfd`` という名前を使うだけで、簡単にキャプチャされた出力へアクセスできます。次に関連する値の確認を行うテスト関数のサンプルを紹介します::
-
-    def test_myoutput(capsys): # または fd レベルの "capfd" を使う
-        print ("hello")
-        sys.stderr.write("world\n")
-        out, err = capsys.readouterr()
-        assert out == "hello\n"
-        assert err == "world\n"
-        print "next"
-        out, err = capsys.readouterr()
-        assert out == "next\n"
-
-..
-    The ``readouterr()`` call snapshots the output so far -
-    and capturing will be continued.  After the test
-    function finishes the original streams will
-    be restored.  Using ``capsys`` this way frees your
-    test from having to care about setting/resetting
-    output streams and also interacts well with py.test's
-    own per-test capturing.
-
-``readouterr()`` 呼び出しは、その時点での出力内容のスナップショットを返し、その後もキャプチャが続行されます。テスト関数が終了した後、元のストリームが復元されます。 ``capsys`` を使うことで、テスト内で出力ストリームをセット/リセットすることに注意を払わなくてよくなります。また、pytest が保持するテスト単位のキャプチャも扱えます。
-
-..
-    If you want to capture on ``fd`` level you can use
-    the ``capfd`` function argument which offers the exact
-    same interface.
-
-``fd`` レベルのキャプチャを行う場合も全く同じインターフェースを提供する ``capfd`` という関数の引数を使います。
-
-.. include:: links.inc

doc/ja/changelog.txt

@@ -1,11 +0,0 @@
-
-.. _changelog:
-
-変更履歴
-========
-
-..
-    Changelog history
-    =================================
-
-.. include:: ../../CHANGELOG

doc/ja/check_sphinx.py

@@ -1,17 +0,0 @@
-import py
-import subprocess
-def test_build_docs(tmpdir):
-    doctrees = tmpdir.join("doctrees")
-    htmldir = tmpdir.join("html")
-    subprocess.check_call([
-        "sphinx-build", "-W", "-bhtml",
-          "-d", str(doctrees), ".", str(htmldir)])
-
-def test_linkcheck(tmpdir):
-    doctrees = tmpdir.join("doctrees")
-    htmldir = tmpdir.join("html")
-    subprocess.check_call(
-        ["sphinx-build", "-blinkcheck",
-          "-d", str(doctrees), ".", str(htmldir)])
-
-

doc/ja/conf.py

@@ -1,284 +0,0 @@
-# -*- coding: utf-8 -*-
-#
-# pytest documentation build configuration file, created by
-# sphinx-quickstart on Fri Oct  8 17:54:28 2010.
-#
-# This file is execfile()d with the current directory set to its containing dir.
-#
-# Note that not all possible configuration values are present in this
-# autogenerated file.
-#
-# All configuration values have a default; values that are commented out
-# serve to show the default.
-
-import sys, os
-
-# If extensions (or modules to document with autodoc) are in another directory,
-# add these directories to sys.path here. If the directory is relative to the
-# documentation root, use os.path.abspath to make it absolute, like shown here.
-#sys.path.insert(0, os.path.abspath('.'))
-
-# -- General configuration -----------------------------------------------------
-
-# If your documentation needs a minimal Sphinx version, state it here.
-#needs_sphinx = '1.0'
-
-# Add any Sphinx extension module names here, as strings. They can be extensions
-# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
-extensions = ['sphinx.ext.autodoc', 'sphinx.ext.todo', 'sphinx.ext.autosummary',
-    'sphinx.ext.intersphinx', 'sphinx.ext.viewcode']
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix of source filenames.
-source_suffix = '.txt'
-
-# The encoding of source files.
-#source_encoding = 'utf-8-sig'
-
-# The master toctree document.
-master_doc = 'contents'
-
-# General information about the project.
-project = u'pytest'
-copyright = u'2011, holger krekel et alii'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The full version, including alpha/beta/rc tags.
-# The short X.Y version.
-version = release = "2.2.4.0"
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-language = "ja"
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-#today = ''
-# Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-exclude_patterns = ['links.inc', '_build', 'naming20.txt', 'test/*',
-    'example/attic.txt',
-    ]
-
-
-# The reST default role (used for this markup: `text`) to use for all documents.
-#default_role = None
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-#add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-#show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# A list of ignored prefixes for module index sorting.
-#modindex_common_prefix = []
-
-
-# -- Options for HTML output ---------------------------------------------------
-
-# The theme to use for HTML and HTML Help pages.  See the documentation for
-# a list of builtin themes.
-html_theme = 'sphinxdoc'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further.  For a list of options available for each theme, see the
-# documentation.
-html_theme_options = {}
-
-# Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
-
-# The name for this set of Sphinx documents.  If None, it defaults to
-# "<project> v<release> documentation".
-html_title = None
-
-# A shorter title for the navigation bar.  Default is the same as html_title.
-html_short_title = "pytest-%s" % release
-
-# The name of an image file (relative to this directory) to place at the top
-# of the sidebar.
-#html_logo = None
-
-# The name of an image file (within the static path) to use as favicon of the
-# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
-# pixels large.
-#html_favicon = None
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-#html_last_updated_fmt = '%b %d, %Y'
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-#html_use_smartypants = True
-
-# Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
-#html_sidebars = {'index': 'indexsidebar.html'}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-#html_additional_pages = {}
-#html_additional_pages = {'index': 'index.html'}
-
-
-# If false, no module index is generated.
-html_domain_indices = True
-
-# If false, no index is generated.
-html_use_index = False
-
-# If true, the index is split into individual pages for each letter.
-#html_split_index = False
-
-# If true, links to the reST sources are added to the pages.
-html_show_sourcelink = False
-
-# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
-#html_show_sphinx = True
-
-# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
-#html_show_copyright = True
-
-# If true, an OpenSearch description file will be output, and all pages will
-# contain a <link> tag referring to it.  The value of this option must be the
-# base URL from which the finished HTML is served.
-#html_use_opensearch = ''
-
-# This is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = None
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'pytestdoc'
-
-
-# -- Options for LaTeX output --------------------------------------------------
-
-# The paper size ('letter' or 'a4').
-#latex_paper_size = 'letter'
-
-# The font size ('10pt', '11pt' or '12pt').
-#latex_font_size = '10pt'
-
-# Grouping the document tree into LaTeX files. List of tuples
-# (source start file, target name, title, author, documentclass [howto/manual]).
-latex_documents = [
-  ('contents', 'pytest.tex', u'pytest Documentation',
-   u'holger krekel et alii', 'manual'),
-]
-
-# The name of an image file (relative to this directory) to place at the top of
-# the title page.
-#latex_logo = None
-
-# For "manual" documents, if this is true, then toplevel headings are parts,
-# not chapters.
-#latex_use_parts = False
-
-# If true, show page references after internal links.
-#latex_show_pagerefs = False
-
-# If true, show URL addresses after external links.
-#latex_show_urls = False
-
-# Additional stuff for the LaTeX preamble.
-#latex_preamble = ''
-
-# Documents to append as an appendix to all manuals.
-#latex_appendices = []
-
-# If false, no module index is generated.
-latex_domain_indices = False
-
-# -- Options for manual page output --------------------------------------------
-
-# One entry per manual page. List of tuples
-# (source start file, name, description, authors, manual section).
-man_pages = [
-    ('usage', 'pytest', u'pytest usage',
-     [u'holger krekel at merlinux eu'], 1)
-]
-
-
-# -- Options for Epub output ---------------------------------------------------
-
-# Bibliographic Dublin Core info.
-epub_title = u'pytest'
-epub_author = u'holger krekel at merlinux eu'
-epub_publisher = u'holger krekel at merlinux eu'
-epub_copyright = u'2011, holger krekel et alii'
-
-# The language of the text. It defaults to the language option
-# or en if the language is not set.
-#epub_language = ''
-
-# The scheme of the identifier. Typical schemes are ISBN or URL.
-#epub_scheme = ''
-
-# The unique identifier of the text. This can be a ISBN number
-# or the project homepage.
-#epub_identifier = ''
-
-# A unique identification for the text.
-#epub_uid = ''
-
-# HTML files that should be inserted before the pages created by sphinx.
-# The format is a list of tuples containing the path and title.
-#epub_pre_files = []
-
-# HTML files shat should be inserted after the pages created by sphinx.
-# The format is a list of tuples containing the path and title.
-#epub_post_files = []
-
-# A list of files that should not be packed into the epub file.
-#epub_exclude_files = []
-
-# The depth of the table of contents in toc.ncx.
-#epub_tocdepth = 3
-
-# Allow duplicate toc entries.
-#epub_tocdup = True
-
-
-# -- Options for texinfo output ------------------------------------------------
-
-texinfo_documents = [
-  (master_doc, 'pytest', 'pytest Documentation',
-   ('Holger Krekel@*Benjamin Peterson@*Ronny Pfannschmidt@*'
-    'Floris Bruynooghe@*others'),
-   'pytest',
-   'simple powerful testing with Pytho',
-   'Programming',
-   1),
-]
-
-
-# Example configuration for intersphinx: refer to the Python standard library.
-intersphinx_mapping = {} # 'http://docs.python.org/': None}
-def setup(app):
-    #from sphinx.ext.autodoc import cut_lines
-    #app.connect('autodoc-process-docstring', cut_lines(4, what=['module']))
-    app.add_description_unit('confval', 'confval',
-                             objname='configuration value',
-                             indextemplate='pair: %s; configuration value')

doc/ja/conftest.py

@@ -1 +0,0 @@
-collect_ignore = ["conf.py"]

doc/ja/contact.txt

@@ -1,73 +0,0 @@
-
-.. _`contact channels`:
-.. _`contact`:
-
-連絡先
-======
-
-..
-    Contact channels
-    ===================================
-
-..
-    - `new issue tracker`_ to report bugs or suggest features (for version
-      2.0 and above).  You may also peek at the `old issue tracker`_ but please
-      don't submit bugs there anymore.
-
-- バグ報告や機能提案は `新イシュートラッカー`_ を使ってください (バージョン 2.0 以上) 。 `旧イシュートラッカー`_ を覗くこともあるかもしれませんが、そこには登録しないようにしてください。
-
-..
-    - `Testing In Python`_: a mailing list for Python testing tools and discussion.
-
-- `Python におけるテスト`_ は Python のテストツールとその議論のためのメーリングリストです。
-
-..
-    - `py-dev developers list`_ pytest specific announcements and discussions.
-
-- `py-dev 開発者のメーリングリスト`_ は pytest に特化したアナウンスと議論のメーリングリストです。
-
-..
-    - #pylib on irc.freenode.net IRC channel for random questions.
-
-- あれこれ聞くための irc.freenode.net IRC チャネルは #pylib です。
-
-..
-    - private mail to Holger.Krekel at gmail com if you want to communicate sensitive issues
-
-- 慎重な対応を求める問題があるなら Holger.Krekel at gmail com 宛へメールしてください。
-
-..
-    - `commit mailing list`_
-
-- `コミットメーリングリスト`_ です。
-
-..
-    - `merlinux.eu`_ offers on-site teaching and consulting services.
-
-- `merlinux.eu`_ はオンサイト教育とコンサルティングサービスを提供しています。
-
-.. _`new issue tracker`: http://bitbucket.org/hpk42/pytest/issues/
-.. _`新イシュートラッカー`: http://bitbucket.org/hpk42/pytest/issues/
-.. _`old issue tracker`: http://bitbucket.org/hpk42/py-trunk/issues/
-.. _`旧イシュートラッカー`: http://bitbucket.org/hpk42/py-trunk/issues/
-
-.. _`merlinux.eu`: http://merlinux.eu
-
-.. _`get an account`:
-
-.. _tetamap: http://tetamap.wordpress.com
-
-.. _`@pylibcommit`: http://twitter.com/pylibcommit
-
-
-.. _`Testing in Python`: http://lists.idyll.org/listinfo/testing-in-python
-.. _`Python におけるテスト`: http://lists.idyll.org/listinfo/testing-in-python
-.. _FOAF: http://en.wikipedia.org/wiki/FOAF
-.. _`py-dev`:
-.. _`development mailing list`:
-.. _`py-dev developers list`: http://codespeak.net/mailman/listinfo/py-dev
-.. _`py-dev 開発者のメーリングリスト`: http://codespeak.net/mailman/listinfo/py-dev
-.. _`py-svn`:
-.. _`commit mailing list`: http://codespeak.net/mailman/listinfo/py-svn
-.. _`コミットメーリングリスト`: http://codespeak.net/mailman/listinfo/py-svn
-

doc/ja/contents.txt

@@ -1,34 +0,0 @@
-
-.. _toc:
-
-pytest ドキュメント
-===================
-
-..
-    Full pytest documentation
-    ===========================
-
-..
-    `Download latest version as PDF <pytest.pdf>`_
-
-`PDF で最新バージョンをダウンロードする <pytest.pdf>`_
-
-.. `Download latest version as EPUB <http://media.readthedocs.org/epub/pytest/latest/pytest.epub>`_
-.. `PDF で最新バージョンをダウンロードする <http://media.readthedocs.org/epub/pytest/latest/pytest.epub>`_
-
-.. toctree::
-   :maxdepth: 2
-
-   overview
-   example/index
-   apiref
-   plugins
-   talks
-   develop
-   announce/index
-
-.. toctree::
-   :hidden:
-
-   changelog.txt
-

doc/ja/customize.txt

@@ -1,196 +0,0 @@
-..
-    Basic test configuration
-    ===================================
-
-基本的なテストの設定
-====================
-
-..
-    Command line options and configuration file settings
-    -----------------------------------------------------------------
-
-コマンドラインオプションと構成ファイルの設定
---------------------------------------------
-
-..
-    You can get help on command line options and values in INI-style
-    configurations files by using the general help option::
-
-一般的なヘルプオプションを使って、ini スタイルの構成ファイルのコマンドラインオプションとその値のヘルプを確認できます::
-
-    py.test -h   # オプションと構成ファイルの設定を表示
-
-..
-    This will display command line and configuration file settings
-    which were registered by installed plugins.
-
-これはインストール済みのプラグインが登録したコマンドライン設定と構成ファイル設定も表示します。
-
-..
-    How test configuration is read from configuration INI-files
-    -------------------------------------------------------------
-
-INI 構成ファイルからテスト設定の読み込み方法
---------------------------------------------
-
-..
-    py.test searches for the first matching ini-style configuration file
-    in the directories of command line argument and the directories above.
-    It looks for file basenames in this order::
-
-py.test は、コマンドライン引数のディレクトリとその上位ディレクトリの、最初に一致する ini スタイルの構成ファイルを検索します。次の順番でファイル名を見ていきます::
-
-    pytest.ini
-    tox.ini
-    setup.cfg
-
-..
-    Searching stops when the first ``[pytest]`` section is found.
-    There is no merging of configuration values from multiple files.  Example::
-
-最初の ``[pytest]`` のセクションを見つけたときに検索を中止します。複数の設定ファイルから設定値をマージするようなことはしません。サンプルを紹介します::
-
-    py.test path/to/testdir
-
-次のように構成ファイルを含むディレクトリがあります::
-
-    path/to/testdir/pytest.ini
-    path/to/testdir/tox.ini
-    path/to/testdir/setup.cfg
-    path/to/pytest.ini
-    path/to/tox.ini
-    path/to/setup.cfg
-    ... # ファイルシステムのルートまで上る
-
-..
-    If argument is provided to a py.test run, the current working directory
-    is used to start the search.
-
-引数が py.test を実行するために提供されるものなら、カレントディレクトリがその検索の開始位置に使われます。
-
-.. _`how to change command line options defaults`:
-.. _`adding default options`:
-
-コマンドラインオプションのデフォルト値の変更方法
-------------------------------------------------
-
-..
-    How to change command line options defaults
-    ------------------------------------------------
-
-..
-    It can be tedious to type the same series of command line options
-    every time you use py.test .  For example, if you always want to see
-    detailed info on skipped and xfailed tests, as well as have terser "dot"
-    progress output, you can write it into a configuration file::
-
-py.test を使うときに毎回一連のコマンドラインオプションを入力するのは飽き飽きしてきます。例えば、毎回スキップしたり xfail したテストの詳細情報を見たいなら、進捗状況を簡潔な "ドット" 出力にするのと同様に、構成ファイル内にその設定を記述できます::
-
-    # pytest.ini の内容
-    # (または tox.ini か setup.cfg)
-    [pytest]
-    addopts = -rsxX -q
-
-..
-    From now on, running ``py.test`` will add the specified options.
-
-設定後に実行すると ``py.test`` は指定したオプションを追加します。
-
-..
-    Builtin configuration file options
-    ----------------------------------------------
-
-組み込みの構成ファイルオプション
----------------------------------
-
-.. confval:: minversion
-
-    ..
-       Specifies a minimal pytest version required for running tests.
-            minversion = 2.1  # will fail if we run with pytest-2.0
-
-   テストの実行に必要な pytest の最小バージョンを指定します
-
-        minversion = 2.1  # pytest-2.0 で実行すると失敗する
-
-.. confval:: addopts
-
-   ..
-      Add the specified ``OPTS`` to the set of command line arguments as if they
-      had been specified by the user. Example: if you have this ini file content::
-         [pytest]
-         addopts = --maxfail=2 -rf  # exit after 2 failures, report fail info
-      issuing ``py.test test_hello.py`` actually means::
-         py.test --maxfail=2 -rf test_hello.py
-      Default is to add no options.
-
-   ユーザーが指定するようにコマンドライン引数をセットするのに特化した ``OPTS`` を追加します。次のような ini ファイルがある場合::
-
-      [pytest]
-      addopts = --maxfail=2 -rf  # 2回失敗したら終了して、その内容をレポートする
-
-   ``py.test test_hello.py`` は、実際には次の内容と同じです::
-
-       py.test --maxfail=2 -rf test_hello.py
-
-   デフォルトでは何のオプションを追加しません。
-
-.. confval:: norecursedirs
-
-   ..
-      Set the directory basename patterns to avoid when recursing
-      for test discovery.  The individual (fnmatch-style) patterns are
-      applied to the basename of a directory to decide if to recurse into it.
-      Pattern matching characters::
-        *       matches everything
-        ?       matches any single character
-        [seq]   matches any character in seq
-        [!seq]  matches any char not in seq
-      Default patterns are ``.* _* CVS {args}``. Setting a ``norecursedir``
-      replaces the default.  Here is an example of how to avoid
-      certain directories::
-       # content of setup.cfg
-       [pytest]
-       norecursedirs = .svn _build tmp*
-
-   再帰的に探索しないテストディレクトリのディレクトリ名のパターンを設定します。それぞれ (fnmatch スタイル) のパターンがそのディレクトリ内を再帰的に調べるかを決めるのにディレクトリ名に適用されます。パターンマッチング文字は次の通りです::
-
-        *       全てに一致する
-        ?       任意の1文字に一致する
-        [seq]   seq のうち任意の1文字に一致する
-        [!seq]  seq のどの文字にも一致しない
-
-   デフォルトパターンは ``.* _* CVS {args}`` となっており、 ``norecursedir`` を設定することで置き換えられます。特定のディレクトリを探索しない方法のサンプルは次の通りです::
-
-    # setup.cfg の内容
-    [pytest]
-    norecursedirs = .svn _build tmp*
-
-   これは典型的な subversion と sphinx の build ディレクトリと ``tmp`` という接頭辞をもつディレクトリを再帰探索しない設定です。
-
-.. confval:: python_files
-
-   ..
-      One or more Glob-style file patterns determining which python files
-      are considered as test modules.
-
-   python ファイルをテストモジュールとみなす、1つかそれ以上の Glob スタイルのファイルパターンです。
-
-.. confval:: python_classes
-
-   ..
-      One or more name prefixes determining which test classes
-      are considered as test modules.
-
-   テストクラスをテストモジュールとみなす、1つかそれ以上の接頭辞です。
-
-.. confval:: python_functions
-
-   ..
-      One or more name prefixes determining which test functions
-      and methods are considered as test modules.
-      See :ref:`change naming conventions` for examples.
-
-   テスト関数やメソッドをテストモジュールとみなす、1つかそれ以上の接頭辞です。
-
-   :ref:`change naming conventions` のサンプルもご覧ください。

doc/ja/develop.txt

@@ -1,68 +0,0 @@
-..
-    =================================================
-    Feedback and contribute to py.test
-    =================================================
-
-=================================
-フィードバックや py.test への貢献
-=================================
-
-.. toctree::
-   :maxdepth: 2
-
-   contact.txt
-
-.. _checkout:
-
-バージョン管理や tarball を使った作業
-=====================================
-
-..
-    Working from version control or a tarball
-    =================================================
-
-..
-    To follow development or start experiments, checkout the
-    complete code and documentation source with mercurial_::
-
-開発を追いかけたり実験したりするには、 mercurial_ でドキュメントやプログラムのソースをチェックアウトしてください::
-
-    hg clone https://bitbucket.org/hpk42/pytest/
-
-..
-    You can also go to the python package index and
-    download and unpack a TAR file::
-
-または Python パッケージインデックスから TAR ファイルをダウンロードして解凍します::
-
-    http://pypi.python.org/pypi/pytest/
-
-..
-    Activating a checkout with setuptools
-    --------------------------------------------
-
-setuptools でチェックアウトしたものを有効にする
------------------------------------------------
-
-..
-    With a working Distribute_ or setuptools_ installation you can type::
-
-distribute_ または setuptools_ を使うと、次のようにしてインストールできます::
-
-    python setup.py develop
-
-..
-    in order to work inline with the tools and the lib of your checkout.
-
-チェックアウトしたツールやライブラリを使います。
-
-..
-    If this command complains that it could not find the required version
-    of "py" then you need to use the development pypi repository::
-
-このコマンドが "py" の必要なバージョンを発見できなかったとエラーを発生させる場合、開発版の pypi リポジトリを使う必要があります::
-
-    python setup.py develop -i http://pypi.testrun.org
-
-
-.. include:: links.inc

doc/ja/doctest.txt

@@ -1,83 +0,0 @@
-
-..
-    Doctest integration for modules and test files
-    =========================================================
-
-モジュールやテストファイルの doctest
-====================================
-
-..
-    By default all files matching the ``test*.txt`` pattern will
-    be run through the python standard ``doctest`` module.  You
-    can change the pattern by issuing::
-
-デフォルトで ``test*.txt`` のパターンに一致する全てのファイルは、Python 標準の ``doctest`` モジュールで実行されます。次のようにコマンドラインでこのパターンを変更できます::
-
-    py.test --doctest-glob='*.rst'
-
-..
-    on the command line.  You can also trigger running of doctests
-    from docstrings in all python modules (including regular
-    python test modules)::
-
-Python モジュール (通常 python テストモジュールを含む) の docstring からも doctest を実行できます::
-
-    py.test --doctest-modules
-
-..
-    You can make these changes permanent in your project by
-    putting them into a pytest.ini file like this::
-
-次のように pytest.ini にその設定を追加することで、自分のプロジェクトでそういった変更を永続化できます::
-
-    # pytest.ini の内容
-    [pytest]
-    addopts = --doctest-modules
-
-..
-    If you then have a text file like this::
-
-次のようなテキストファイルが存在して::
-
-    # example.rst の内容
-
-    hello this is a doctest
-    >>> x = 3
-    >>> x
-    3
-
-..
-    and another like this::
-
-他にも次のようなファイルも存在するとします::
-
-    # mymodule.py の内容
-    def something():
-        """ a doctest in a docstring
-        >>> something()
-        42
-        """
-        return 42
-
-..
-    then you can just invoke ``py.test`` without command line options::
-
-コマンドラインオプションを指定せず ``py.test`` を実行するだけです::
-
-    $ py.test
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    mymodule.py .
-    
-    ========================= 1 passed in 0.02 seconds =========================
-
-..
-    It is possible to use fixtures using the ``getfixture`` helper::
-
-それは ``getfixture`` ヘルパーを使ってフィクスチャを使用することが可能である::
-
-    # content of example.rst
-    >>> tmp = getfixture('tmpdir')
-    >>> ...

doc/ja/example/assertion/failure_demo.py

@@ -1,213 +0,0 @@
-from py.test import raises
-import py
-
-def otherfunc(a,b):
-    assert a==b
-
-def somefunc(x,y):
-    otherfunc(x,y)
-
-def otherfunc_multi(a,b):
-    assert (a ==
-            b)
-
-def test_generative(param1, param2):
-    assert param1 * 2 < param2
-
-def pytest_generate_tests(metafunc):
-    if 'param1' in metafunc.fixturenames:
-        metafunc.addcall(funcargs=dict(param1=3, param2=6))
-
-class TestFailing(object):
-    def test_simple(self):
-        def f():
-            return 42
-        def g():
-            return 43
-
-        assert f() == g()
-
-    def test_simple_multiline(self):
-        otherfunc_multi(
-                  42,
-                  6*9)
-
-    def test_not(self):
-        def f():
-            return 42
-        assert not f()
-
-class TestSpecialisedExplanations(object):
-    def test_eq_text(self):
-        assert 'spam' == 'eggs'
-
-    def test_eq_similar_text(self):
-        assert 'foo 1 bar' == 'foo 2 bar'
-
-    def test_eq_multiline_text(self):
-        assert 'foo\nspam\nbar' == 'foo\neggs\nbar'
-
-    def test_eq_long_text(self):
-        a = '1'*100 + 'a' + '2'*100
-        b = '1'*100 + 'b' + '2'*100
-        assert a == b
-
-    def test_eq_long_text_multiline(self):
-        a = '1\n'*100 + 'a' + '2\n'*100
-        b = '1\n'*100 + 'b' + '2\n'*100
-        assert a == b
-
-    def test_eq_list(self):
-        assert [0, 1, 2] == [0, 1, 3]
-
-    def test_eq_list_long(self):
-        a = [0]*100 + [1] + [3]*100
-        b = [0]*100 + [2] + [3]*100
-        assert a == b
-
-    def test_eq_dict(self):
-        assert {'a': 0, 'b': 1} == {'a': 0, 'b': 2}
-
-    def test_eq_set(self):
-        assert set([0, 10, 11, 12]) == set([0, 20, 21])
-
-    def test_eq_longer_list(self):
-        assert [1,2] == [1,2,3]
-
-    def test_in_list(self):
-        assert 1 in [0, 2, 3, 4, 5]
-
-    def test_not_in_text_multiline(self):
-        text = 'some multiline\ntext\nwhich\nincludes foo\nand a\ntail'
-        assert 'foo' not in text
-
-    def test_not_in_text_single(self):
-        text = 'single foo line'
-        assert 'foo' not in text
-
-    def test_not_in_text_single_long(self):
-        text = 'head ' * 50 + 'foo ' + 'tail ' * 20
-        assert 'foo' not in text
-
-    def test_not_in_text_single_long_term(self):
-        text = 'head ' * 50 + 'f'*70 + 'tail ' * 20
-        assert 'f'*70 not in text
-
-
-def test_attribute():
-    class Foo(object):
-        b = 1
-    i = Foo()
-    assert i.b == 2
-
-
-def test_attribute_instance():
-    class Foo(object):
-        b = 1
-    assert Foo().b == 2
-
-
-def test_attribute_failure():
-    class Foo(object):
-        def _get_b(self):
-            raise Exception('Failed to get attrib')
-        b = property(_get_b)
-    i = Foo()
-    assert i.b == 2
-
-
-def test_attribute_multiple():
-    class Foo(object):
-        b = 1
-    class Bar(object):
-        b = 2
-    assert Foo().b == Bar().b
-
-
-def globf(x):
-    return x+1
-
-class TestRaises:
-    def test_raises(self):
-        s = 'qwe'
-        raises(TypeError, "int(s)")
-
-    def test_raises_doesnt(self):
-        raises(IOError, "int('3')")
-
-    def test_raise(self):
-        raise ValueError("demo error")
-
-    def test_tupleerror(self):
-        a,b = [1]
-
-    def test_reinterpret_fails_with_print_for_the_fun_of_it(self):
-        l = [1,2,3]
-        print ("l is %r" % l)
-        a,b = l.pop()
-
-    def test_some_error(self):
-        if namenotexi:
-            pass
-
-    def func1(self):
-        assert 41 == 42
-
-
-# thanks to Matthew Scott for this test
-def test_dynamic_compile_shows_nicely():
-    src = 'def foo():\n assert 1 == 0\n'
-    name = 'abc-123'
-    module = py.std.imp.new_module(name)
-    code = py.code.compile(src, name, 'exec')
-    py.builtin.exec_(code, module.__dict__)
-    py.std.sys.modules[name] = module
-    module.foo()
-
-
-
-class TestMoreErrors:
-    def test_complex_error(self):
-        def f():
-            return 44
-        def g():
-            return 43
-        somefunc(f(), g())
-
-    def test_z1_unpack_error(self):
-        l = []
-        a,b  = l
-
-    def test_z2_type_error(self):
-        l = 3
-        a,b  = l
-
-    def test_startswith(self):
-        s = "123"
-        g = "456"
-        assert s.startswith(g)
-
-    def test_startswith_nested(self):
-        def f():
-            return "123"
-        def g():
-            return "456"
-        assert f().startswith(g())
-
-    def test_global_func(self):
-        assert isinstance(globf(42), float)
-
-    def test_instance(self):
-        self.x = 6*7
-        assert self.x != 42
-
-    def test_compare(self):
-        assert globf(10) < 5
-
-    def test_try_finally(self):
-        x = 1
-        try:
-            assert x == 0
-        finally:
-            x = 0
-

doc/ja/example/assertion/global_testmodule_config/conftest.py

@@ -1,10 +0,0 @@
-import pytest, py
-mydir = py.path.local(__file__).dirpath()
-
-def pytest_runtest_setup(item):
-    if isinstance(item, pytest.Function):
-        if not item.fspath.relto(mydir):
-            return
-        mod = item.getparent(pytest.Module).obj
-        if hasattr(mod, 'hello'):
-            print ("mod.hello %r" % (mod.hello,))

doc/ja/example/assertion/global_testmodule_config/test_hello.py

@@ -1,5 +0,0 @@
-
-hello = "world"
-
-def test_func():
-    pass

doc/ja/example/assertion/test_failures.py

@@ -1,14 +0,0 @@
-
-import py
-failure_demo = py.path.local(__file__).dirpath('failure_demo.py')
-pytest_plugins = 'pytester',
-
-def test_failure_demo_fails_properly(testdir):
-    target = testdir.tmpdir.join(failure_demo.basename)
-    failure_demo.copy(target)
-    failure_demo.copy(testdir.tmpdir.join(failure_demo.basename))
-    result = testdir.runpytest(target)
-    result.stdout.fnmatch_lines([
-        "*39 failed*"
-    ])
-    assert result.ret != 0

doc/ja/example/assertion/test_setup_flow_example.py

@@ -1,42 +0,0 @@
-def setup_module(module):
-    module.TestStateFullThing.classcount = 0
-
-class TestStateFullThing:
-    def setup_class(cls):
-        cls.classcount += 1
-
-    def teardown_class(cls):
-        cls.classcount -= 1
-
-    def setup_method(self, method):
-        self.id = eval(method.__name__[5:])
-
-    def test_42(self):
-        assert self.classcount == 1
-        assert self.id == 42
-
-    def test_23(self):
-        assert self.classcount == 1
-        assert self.id == 23
-
-def teardown_module(module):
-    assert module.TestStateFullThing.classcount == 0
-
-""" For this example the control flow happens as follows::
-    import test_setup_flow_example
-    setup_module(test_setup_flow_example)
-       setup_class(TestStateFullThing)
-           instance = TestStateFullThing()
-           setup_method(instance, instance.test_42)
-              instance.test_42()
-           setup_method(instance, instance.test_23)
-              instance.test_23()
-       teardown_class(TestStateFullThing)
-    teardown_module(test_setup_flow_example)
-
-Note that ``setup_class(TestStateFullThing)`` is called and not
-``TestStateFullThing.setup_class()`` which would require you
-to insert ``setup_class = classmethod(setup_class)`` to make
-your setup function callable.
-"""
-

doc/ja/example/attic.txt

@@ -1,79 +0,0 @@
-
-.. _`accept example`:
-
-example: specifying and selecting acceptance tests
---------------------------------------------------------------
-
-.. sourcecode:: python
-
-    # ./conftest.py
-    def pytest_option(parser):
-        group = parser.getgroup("myproject")
-        group.addoption("-A", dest="acceptance", action="store_true",
-            help="run (slow) acceptance tests")
-
-    def pytest_funcarg__accept(request):
-        return AcceptFixture(request)
-
-    class AcceptFixture:
-        def __init__(self, request):
-            if not request.config.option.acceptance:
-                pytest.skip("specify -A to run acceptance tests")
-            self.tmpdir = request.config.mktemp(request.function.__name__, numbered=True)
-
-        def run(self, cmd):
-            """ called by test code to execute an acceptance test. """
-            self.tmpdir.chdir()
-            return py.process.cmdexec(cmd)
-
-
-and the actual test function example:
-
-.. sourcecode:: python
-
-    def test_some_acceptance_aspect(accept):
-        accept.tmpdir.mkdir("somesub")
-        result = accept.run("ls -la")
-        assert "somesub" in result
-
-If you run this test without specifying a command line option
-the test will get skipped with an appropriate message. Otherwise
-you can start to add convenience and test support methods
-to your AcceptFixture and drive running of tools or
-applications and provide ways to do assertions about
-the output.
-
-.. _`decorate a funcarg`:
-
-example: decorating a funcarg in a test module
---------------------------------------------------------------
-
-For larger scale setups it's sometimes useful to decorate
-a funcarg just for a particular test module.  We can
-extend the `accept example`_ by putting this in our test module:
-
-.. sourcecode:: python
-
-    def pytest_funcarg__accept(request):
-        # call the next factory (living in our conftest.py)
-        arg = request.getfuncargvalue("accept")
-        # create a special layout in our tempdir
-        arg.tmpdir.mkdir("special")
-        return arg
-
-    class TestSpecialAcceptance:
-        def test_sometest(self, accept):
-            assert accept.tmpdir.join("special").check()
-
-Our module level factory will be invoked first and it can
-ask its request object to call the next factory and then
-decorate its result.  This mechanism allows us to stay
-ignorant of how/where the function argument is provided -
-in our example from a `conftest plugin`_.
-
-sidenote: the temporary directory used here are instances of
-the `py.path.local`_ class which provides many of the os.path
-methods in a convenient way.
-
-.. _`py.path.local`: ../path.html#local
-.. _`conftest plugin`: customize.html#conftestplugin

doc/ja/example/conftest.py

@@ -1 +0,0 @@
-collect_ignore = ["nonpython"]

doc/ja/example/costlysetup/conftest.py

@@ -1,17 +0,0 @@
-
-def pytest_funcarg__setup(request):
-    return request.cached_setup(
-        setup=lambda: CostlySetup(),
-        teardown=lambda costlysetup: costlysetup.finalize(),
-        scope="session",
-    )
-
-class CostlySetup:
-    def __init__(self):
-        import time
-        print ("performing costly setup")
-        time.sleep(5)
-        self.timecostly = 1
-
-    def finalize(self):
-        del self.timecostly

doc/ja/example/costlysetup/sub1/__init__.py

@@ -1 +0,0 @@
-#

doc/ja/example/costlysetup/sub1/test_quick.py

@@ -1,3 +0,0 @@
-
-def test_quick(setup):
-    pass

doc/ja/example/costlysetup/sub2/__init__.py

@@ -1 +0,0 @@
-#

doc/ja/example/costlysetup/sub2/test_two.py

@@ -1,6 +0,0 @@
-def test_something(setup):
-    assert setup.timecostly == 1
-
-def test_something_more(setup):
-    assert setup.timecostly == 1
-

doc/ja/example/index.txt

@@ -1,33 +0,0 @@
-
-.. _examples:
-
-使用方法と例
-============
-
-..
-    Usages and Examples
-    ===========================================
-
-..
-    Here is a (growing) list of examples. :ref:`Contact <contact>` us if you
-    need more examples or have questions. Also take a look at the :ref:`comprehensive documentation <toc>` which contains many example snippets as well.
-
-次に pytest の使い方のサンプルリストがあります (さらに増やし続けます) 。もっと良いサンプルや質問があれば :ref:`ご連絡ください <contact>` 。また :ref:`オンラインドキュメント全体 <toc>` を見渡しても多くのサンプルやスニペットがあります。
-
-..
-       see :doc:`../getting-started` for basic introductory examples
-
-.. note::
-
-   基本的な使い方は :doc:`../getting-started` を参照してください 
-
-.. toctree::
-   :maxdepth: 2
-
-   reportingdemo.txt
-   simple.txt
-   mysetup.txt
-   parametrize.txt
-   markers.txt
-   pythoncollection.txt
-   nonpython.txt

doc/ja/example/layout1/setup.cfg

@@ -1,4 +0,0 @@
-[pytest]
-testfilepatterns =
-    ${topdir}/tests/unit/test_${basename}
-    ${topdir}/tests/functional/*.py

doc/ja/example/markers.txt

@@ -1,404 +0,0 @@
-
-.. _`mark examples`:
-
-カスタムマーカーを使う
-======================
-
-..
-    Working with custom markers
-    =================================================
-
-..
-    Here are some example using the :ref:`mark` mechanism.
-
-ここでは :ref:`mark` の仕組みを使ったサンプルを紹介します。
-
-..
-    Marking test functions and selecting them for a run
-    ----------------------------------------------------
-
-テスト関数をマークして実行時に選択
-----------------------------------
-
-..
-    You can "mark" a test function with custom metadata like this::
-
-次のようにカスタムメタデータでテスト関数を "マーク" できます::
-
-    # test_server.py の内容
-
-    import pytest
-    @pytest.mark.webtest
-    def test_send_http():
-        pass # アプリの webtest テストを実行
-    def test_something_quick():
-        pass
-
-.. versionadded:: 2.2
-
-..
-    You can then restrict a test run to only run tests marked with ``webtest``::
-
-``webtest`` でマークされたテストのみを実行するように制限できます::
-
-    $ py.test -v -m webtest
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4 -- /home/hpk/venv/0/bin/python
-    collecting ... collected 2 items
-    
-    test_server.py:3: test_send_http PASSED
-    
-    =================== 1 tests deselected by "-m 'webtest'" ===================
-    ================== 1 passed, 1 deselected in 0.00 seconds ==================
-
-..
-    Or the inverse, running all tests except the webtest ones::
-
-もしくは逆に webtest を除く全てのテストを実行します::
-
-    $ py.test -v -m "not webtest"
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4 -- /home/hpk/venv/0/bin/python
-    collecting ... collected 2 items
-    
-    test_server.py:6: test_something_quick PASSED
-    
-    ================= 1 tests deselected by "-m 'not webtest'" =================
-    ================== 1 passed, 1 deselected in 0.00 seconds ==================
-
-..
-    Registering markers
-    -------------------------------------
-
-マーカーの登録
---------------
-
-.. versionadded:: 2.2
-
-..
-    Registering markers for your test suite is simple::
-
-.. ini-syntax for custom markers:
-
-テストスイートにマーカーを登録するのは登録です:: 
-
-    # pytest.ini の内容
-    [pytest]
-    markers =
-        webtest: mark a test as a webtest.
-
-..
-    You can ask which markers exist for your test suite - the list includes our just defined ``webtest`` markers::
-
-テストスイートに存在するマーカーが調べます。次の一覧では、先ほど定義した ``webtest`` マーカーがあります::
-
-    $ py.test --markers
-    @pytest.mark.webtest: mark a test as a webtest.
-    
-    @pytest.mark.skipif(*conditions): skip the given test function if evaluation of all conditions has a True value.  Evaluation happens within the module global context. Example: skipif('sys.platform == "win32"') skips the test if we are on the win32 platform. 
-    
-    @pytest.mark.xfail(*conditions, reason=None, run=True): mark the the test function as an expected failure. Optionally specify a reason and run=False if you don't even want to execute the test function. Any positional condition strings will be evaluated (like with skipif) and if one is False the marker will not be applied.
-    
-    @pytest.mark.parametrize(argnames, argvalues): call a test function multiple times passing in multiple different argument value sets. Example: @parametrize('arg1', [1,2]) would lead to two calls of the decorated test function, one with arg1=1 and another with arg1=2.
-    
-    @pytest.mark.tryfirst: mark a hook implementation function such that the plugin machinery will try to call it first/as early as possible.
-    
-    @pytest.mark.trylast: mark a hook implementation function such that the plugin machinery will try to call it last/as late as possible.
-
-..
-    For an example on how to add and work with markers from a plugin, see
-    :ref:`adding a custom marker from a plugin`.
-
-プラグインからマーカーを追加して処理するサンプルについては :ref:`adding a custom marker from a plugin` を参照してください。
-
-..
-        It is recommended to explicitely register markers so that:
-
-        * there is one place in your test suite defining your markers
-
-        * asking for existing markers via ``py.test --markers`` gives good output
-
-        * typos in function markers are treated as an error if you use
-          the ``--strict`` option. Later versions of py.test are probably
-          going to treat non-registered markers as an error.
-
-.. note::
-
-    次のように明示的にマーカーを登録することを推奨します:
-
-    * テストスイートの一箇所でマーカーを定義する
-
-    * ``py.test --markers`` で既存のマーカーに関する分かりやすい説明を表示する
-
-    * ``--strict`` オプションを使うと、関数マーカー内の誤字をエラーにします、最近の py.test バージョンでは、未登録マーカーをエラーとして扱うようにしています
-
-.. _`scoped-marking`:
-
-クラスまたはモジュール全体をマーキング
---------------------------------------
-
-..
-    Marking whole classes or modules
-    ----------------------------------------------------
-
-..
-    If you are programming with Python 2.6 or later you may use ``pytest.mark``
-    decorators with classes to apply markers to all of its test methods::
-
-Python 2.6 か、それ以上のバージョンでコーディングしているなら、クラスのテストメソッド全てにマーカーを適用するために ``pytest.mark`` をクラスデコレーターとして使えます::
-
-    # test_mark_classlevel.py の内容
-    import pytest
-    @pytest.mark.webtest
-    class TestClass:
-        def test_startup(self):
-            pass
-        def test_startup_and_more(self):
-            pass
-
-..
-    This is equivalent to directly applying the decorator to the
-    two test functions.
-
-これは2つのテスト関数に直接デコレーターを適用するのと同じです。
-
-..
-    To remain backward-compatible with Python 2.4 you can also set a
-    ``pytestmark`` attribute on a TestClass like this::
-
-Pythn 2.4 との後方互換性を維持するには、次のように TestClass に ``pytestmark`` 属性も設定できます::
-
-    import pytest
-
-    class TestClass:
-        pytestmark = pytest.mark.webtest
-
-..
-    or if you need to use multiple markers you can use a list::
-
-もしくは、複数のマーカーを使う必要がある場合はリストも使えます::
-
-    import pytest
-
-    class TestClass:
-        pytestmark = [pytest.mark.webtest, pytest.mark.slowtest]
-
-..
-    You can also set a module level marker::
-
-モジュールレベルのマーカーも設定できます::
-
-    import pytest
-    pytestmark = pytest.mark.webtest
-
-..
-    in which case it will be applied to all functions and
-    methods defined in the module.
-
-この場合、そのモジュール内で定義されている全ての関数とメソッドに適用されます。
-
-..
-    Using ``-k TEXT`` to select tests
-    ----------------------------------------------------
-
-``-k TEXT`` を使ったテストの選択
---------------------------------
-
-..
-    You can use the ``-k`` command line option to only run tests with names matching
-    the given argument::
-
-指定した引数に一致する名前のテストを実行するには ``-k`` コマンドラインオプションを使います::
-
-    $ py.test -k send_http  # 前節で定義したサンプルを実行
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 4 items
-    
-    test_server.py .
-    
-    =================== 3 tests deselected by '-ksend_http' ====================
-    ================== 1 passed, 3 deselected in 0.01 seconds ==================
-
-..
-    And you can also run all tests except the ones that match the keyword::
-
-また、そのキーワードに一致するものを除く全てのテストを実行することもできます::
-
-    $ py.test -k-send_http
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 4 items
-    
-    test_mark_classlevel.py ..
-    test_server.py .
-    
-    =================== 1 tests deselected by '-k-send_http' ===================
-    ================== 3 passed, 1 deselected in 0.01 seconds ==================
-
-..
-    Or to only select the class::
-
-もしくは、クラスのみを選択するには次のようにします::
-
-    $ py.test -kTestClass
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 4 items
-    
-    test_mark_classlevel.py ..
-    
-    =================== 2 tests deselected by '-kTestClass' ====================
-    ================== 2 passed, 2 deselected in 0.01 seconds ==================
-
-.. _`adding a custom marker from a plugin`:
-
-カスタムマーカーとコマンドラインオプションによるテストの実行制御
-----------------------------------------------------------------
-
-..
-    Custom marker and command line option to control test runs
-    ----------------------------------------------------------
-
-.. regendoc:wipe
-
-..
-    Plugins can provide custom markers and implement specific behaviour
-    based on it. This is a self-contained example which adds a command
-    line option and a parametrized test function marker to run tests
-    specifies via named environments::
-
-プラグインは、カスタムマーカーを提供して、そのマーカーに基づく特別な振る舞いを実装します。これは、コマンドラインオプションと、名前付きの環境の値に特化したテストを実行するためのパラメーター化されたテスト関数マーカーを追加する自己完結型のサンプルです::
-
-    # conftest.py の内容
-
-    import pytest
-    def pytest_addoption(parser):
-        parser.addoption("-E", dest="env", action="store", metavar="NAME",
-            help="only run tests matching the environment NAME.")
-
-    def pytest_configure(config):
-        # 追加のマーカーを登録
-        config.addinivalue_line("markers",
-            "env(name): mark test to run only on named environment")
-
-    def pytest_runtest_setup(item):
-        if not isinstance(item, item.Function):
-            return
-        if hasattr(item.obj, 'env'):
-            envmarker = getattr(item.obj, 'env')
-            envname = envmarker.args[0]
-            if envname != item.config.option.env:
-                pytest.skip("test requires env %r" % envname)
-
-..
-    A test file using this local plugin::
-
-この local プラグインを使うテストファイルです::
-
-    # test_someenv.py の内容
-
-    import pytest
-    @pytest.mark.env("stage1")
-    def test_basic_db_operation():
-        pass
-
-..
-    and an example invocations specifying a different environment than what
-    the test needs::
-
-そのテストが必要とするものではない別の環境を指定して実行する例です::
-
-    $ py.test -E stage2
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_someenv.py s
-    
-    ======================== 1 skipped in 0.00 seconds =========================
-  
-..
-    and here is one that specifies exactly the environment needed::
-
-今度は正しく必要とする環境を指定して実行します::
-
-    $ py.test -E stage1
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_someenv.py .
-    
-    ========================= 1 passed in 0.00 seconds =========================
-
-..
-    The ``--markers`` option always gives you a list of available markers::
-
-``--markers`` オプションは利用できるマーカーの一覧を表示します::
-
-    $ py.test --markers
-    @pytest.mark.env(name): mark test to run only on named environment
-    
-    @pytest.mark.skipif(*conditions): skip the given test function if evaluation of all conditions has a True value.  Evaluation happens within the module global context. Example: skipif('sys.platform == "win32"') skips the test if we are on the win32 platform. 
-    
-    @pytest.mark.xfail(*conditions, reason=None, run=True): mark the the test function as an expected failure. Optionally specify a reason and run=False if you don't even want to execute the test function. Any positional condition strings will be evaluated (like with skipif) and if one is False the marker will not be applied.
-    
-    @pytest.mark.parametrize(argnames, argvalues): call a test function multiple times passing in multiple different argument value sets. Example: @parametrize('arg1', [1,2]) would lead to two calls of the decorated test function, one with arg1=1 and another with arg1=2.
-    
-    @pytest.mark.tryfirst: mark a hook implementation function such that the plugin machinery will try to call it first/as early as possible.
-    
-    @pytest.mark.trylast: mark a hook implementation function such that the plugin machinery will try to call it last/as late as possible.
-
-
-..
-    Reading markers which were set from multiple places
-    ----------------------------------------------------
-
-複数の場所から設定されたマーカーを読み込む
-------------------------------------------
-
-.. versionadded: 2.2.2
-
-..
-    If you are heavily using markers in your test suite you may encounter the case where a marker is applied several times to a test function.  From plugin
-    code you can read over all such settings.  Example::
-
-テストスイート内でマーカーをたくさん使うと、テスト関数に対して数回マーカーが適用される場合があります。プラグインコードから、そういった全ての設定を読み込めます。サンプルを紹介します::
-
-    # test_mark_three_times.py の内容
-    import pytest
-    pytestmark = pytest.mark.glob("module", x=1)
-
-    @pytest.mark.glob("class", x=2)
-    class TestClass:
-        @pytest.mark.glob("function", x=3)
-        def test_something(self):
-            pass
-
-..
-    Here we have the marker "glob" applied three times to the same
-    test function.  From a conftest file we can read it like this::
-
-ここでは、同じテスト関数に対して3回適用される "glob" マーカーがあります。conftest ファイルから次のようにしてそれを調べます::
-
-    # conftest.py の内容
-
-    def pytest_runtest_setup(item):
-        g = getattr(item.obj, 'glob', None)
-        if g is not None:
-            for info in g:
-                print ("glob args=%s kwargs=%s" %(info.args, info.kwargs))
-
-..
-    Let's run this without capturing output and see what we get::
-
-標準出力を取得せずにこのテストを実行して、何が表示されるかを見てみましょう::
-
-    $ py.test -q -s 
-    collecting ... collected 2 items
-    ..
-    2 passed in 0.01 seconds
-    glob args=('function',) kwargs={'x': 3}
-    glob args=('class',) kwargs={'x': 2}
-    glob args=('module',) kwargs={'x': 1}

doc/ja/example/multipython.py

@@ -1,60 +0,0 @@
-"""
-module containing a parametrized tests testing cross-python
-serialization via the pickle module.
-"""
-import py, pytest
-
-pythonlist = ['python2.4', 'python2.5', 'python2.6', 'python2.7', 'python2.8']
-
-def pytest_generate_tests(metafunc):
-    # we parametrize all "python1" and "python2" arguments to iterate
-    # over the python interpreters of our list above - the actual
-    # setup and lookup of interpreters in the python1/python2 factories
-    # respectively.
-    for arg in metafunc.fixturenames:
-        if arg in ("python1", "python2"):
-            metafunc.parametrize(arg, pythonlist, indirect=True)
-
-@pytest.mark.parametrize("obj", [42, {}, {1:3},])
-def test_basic_objects(python1, python2, obj):
-    python1.dumps(obj)
-    python2.load_and_is_true("obj == %s" % obj)
-
-def pytest_funcarg__python1(request):
-    tmpdir = request.getfuncargvalue("tmpdir")
-    picklefile = tmpdir.join("data.pickle")
-    return Python(request.param, picklefile)
-
-def pytest_funcarg__python2(request):
-    python1 = request.getfuncargvalue("python1")
-    return Python(request.param, python1.picklefile)
-
-class Python:
-    def __init__(self, version, picklefile):
-        self.pythonpath = py.path.local.sysfind(version)
-        if not self.pythonpath:
-            py.test.skip("%r not found" %(version,))
-        self.picklefile = picklefile
-    def dumps(self, obj):
-        dumpfile = self.picklefile.dirpath("dump.py")
-        dumpfile.write(py.code.Source("""
-            import pickle
-            f = open(%r, 'wb')
-            s = pickle.dump(%r, f)
-            f.close()
-        """ % (str(self.picklefile), obj)))
-        py.process.cmdexec("%s %s" %(self.pythonpath, dumpfile))
-
-    def load_and_is_true(self, expression):
-        loadfile = self.picklefile.dirpath("load.py")
-        loadfile.write(py.code.Source("""
-            import pickle
-            f = open(%r, 'rb')
-            obj = pickle.load(f)
-            f.close()
-            res = eval(%r)
-            if not res:
-                raise SystemExit(1)
-        """ % (str(self.picklefile), expression)))
-        print (loadfile)
-        py.process.cmdexec("%s %s" %(self.pythonpath, loadfile))

doc/ja/example/mysetup.txt

@@ -1,185 +0,0 @@
-
-.. highlightlang:: python
-
-.. _mysetup:
-
-Mysetup パターン: アプリケーションに特化したテストフィクスチャ
-==============================================================
-
-..
-    Mysetup pattern: application specific test fixtures
-    ==========================================================
-
-..
-    Here is a basic useful step-by-step example for managing and interacting
-    with application specific test setup.  The goal is to have one place
-    where we have the glue and test support code for bootstrapping and
-    configuring application objects and allow test modules and test
-    functions to stay ignorant of involved details.
-
-アプリケーションに特化したテストのセットアップを管理したり、相互にやり取りする、基本的且つ便利なサンプルを順を追って紹介します。その目的としては、アプリケーションオブジェクトの一連の開始処理や設定のグルーコードやテストコードを1つの場所に集め、実行時にテストモジュールとテスト関数からそういった処理の詳細を見えなくすることです。
-
-..
-    Step 1: Implementing the test/app-specific ``mysetup`` pattern
-    --------------------------------------------------------------
-
-ステップ 1: アプリケーションに特化した ``mysetup`` パターンの実装
------------------------------------------------------------------
-
-..
-    Let's write a simple test function using a ``mysetup`` funcarg::
-
-``mysetup`` という関数の引数を使って、簡単なテスト関数を書いてみましょう::
-
-    # test_sample.py の内容
-    def test_answer(mysetup):
-        app = mysetup.myapp()
-        answer = app.question()
-        assert answer == 42
-
-..
-    To run this test py.test needs to find and call a factory to
-    obtain the required ``mysetup`` function argument.  To make
-    an according factory findable we write down a specifically named factory
-    method in a :ref:`local plugin <localplugin>` ::
-
-このテストを実行するために py.test は、関数の引数に与えられた ``mysetup`` を扱うファクトリー関数を探して呼び出す必要があります。このファクトリー関数を探し出せるように :ref:`local プラグイン <localplugin>` に特別な名前をもつファクトリーメソッドを書きます::
-
-    # conftest.py の内容
-    from myapp import MyApp
-
-    def pytest_funcarg__mysetup(request): # "mysetup" ファクトリー関数
-        return MySetup()
-
-    class MySetup: # このインスタンスはテスト関数から見える
-        def myapp(self):
-            return MyApp()
-
-..
-    To run the example we stub out a simple ``MyApp`` application object::
-
-このサンプルを実行するために ``MyApp`` アプリケーションオブジェクトの簡単なスタブを作ります::
-
-    # myapp.py の内容
-    class MyApp:
-        def question(self):
-            return 6 * 9
-
-..
-    You can now run the test::
-
-テストを実行します::
-
-    $ py.test test_sample.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_sample.py F
-    
-    ================================= FAILURES =================================
-    _______________________________ test_answer ________________________________
-    
-    mysetup = <conftest.MySetup instance at 0x17f21b8>
-    
-        def test_answer(mysetup):
-            app = mysetup.myapp()
-            answer = app.question()
-    >       assert answer == 42
-    E       assert 54 == 42
-    
-    test_sample.py:4: AssertionError
-    ========================= 1 failed in 0.01 seconds =========================
-
-..
-    This means that our ``mysetup`` object was successfully instantiated
-    and ``mysetup.app()`` returned an initialized ``MyApp`` instance.
-    We can ask it about the question and if you are confused as to what
-    the concrete question or answers actually mean, please see here_.
-
-``mysetup`` オブジェクトが正常にインスタンス化されて、 ``mysetup.app()`` が初期化された ``MyApp`` インスタンスを返しました。あなたが具体的に何を聞けば良いのか、もしくは実際に何が起こったかに混乱しているなら、その質問に関して尋ねられます。 `ここ`_ をご覧ください。
-
-.. _here: http://uncyclopedia.wikia.com/wiki/The_Hitchhiker's_Guide_to_the_Galaxy
-.. _ここ: http://uncyclopedia.wikia.com/wiki/The_Hitchhiker's_Guide_to_the_Galaxy
-.. _`tut-cmdlineoption`:
-
-ステップ 2: コマンドラインオプションとテストのスキップを確認
-------------------------------------------------------------
-
-..
-    Step 2: Checking a command line option and skipping tests
-    -----------------------------------------------------------
-
-..
-    To add a command line option we update the ``conftest.py`` of
-    the previous example to add a command line option
-    and to offer a new mysetup method::
-
-コマンドラインオプションを追加するには、前述したサンプルの ``conftest.py`` に、コマンドラインオプションを追加して新たな mysetup メソッドを提供するように変更します::
-
-    # ./conftest.py の内容
-    import pytest
-    from myapp import MyApp
-
-    def pytest_funcarg__mysetup(request): # "mysetup" ファクトリー関数
-        return MySetup(request)
-
-    def pytest_addoption(parser):
-        parser.addoption("--ssh", action="store", default=None,
-            help="specify ssh host to run tests with")
-
-
-    class MySetup:
-        def __init__(self, request):
-            self.config = request.config
-
-        def myapp(self):
-            return MyApp()
-
-        def getsshconnection(self):
-            host = self.config.option.ssh
-            if host is None:
-                pytest.skip("specify ssh host with --ssh")
-            return execnet.SshGateway(host)
-
-
-..
-    Now any test function can use the ``mysetup.getsshconnection()`` method
-    like this::
-
-次のようにテスト関数から ``mysetup.getsshconnection()`` メソッドを使えます::
-
-    # test_ssh.py の内容
-    class TestClass:
-        def test_function(self, mysetup):
-            conn = mysetup.getsshconnection()
-            # conn を使ってテストする
-
-..
-    Running it yields::
-
-実行すると次のようなレポートが表示されます::
-
-    $ py.test test_ssh.py -rs
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 1 items
-    
-    test_ssh.py s
-    ========================= short test summary info ==========================
-    SKIP [1] /tmp/doc-exec-220/conftest.py:22: specify ssh host with --ssh
-    
-    ======================== 1 skipped in 0.01 seconds =========================
-
-..
-    If you specify a command line option like ``py.test --ssh=python.org`` the test will execute as expected.
-
-``py.test --ssh=python.org`` のようにコマンドラインオプションを指定すると、期待した通りにテストが実行されます。
-
-..
-    Note that neither the ``TestClass`` nor the ``test_function`` need to
-    know anything about how to setup the test state.  It is handled separately
-    in your "test setup glue" code in the ``conftest.py`` file.  It is easy
-    to extend the ``mysetup`` object for further needs in the test code - and for use by any other test functions in the files and directories below the ``conftest.py`` file.
-
-``TestClass`` も ``test_function`` のどちらとも、テストの状態をセットアップする方法について何も知る必要がないことに注目してください。 ``conftest.py`` ファイルの "テストをセットアップするグルー" コードは別々に処理されます。テストコード内で必要に応じて ``mysetup`` オブジェクトを拡張するのは簡単です。 ``conftest.py`` ファイルの配下にあるファイルやディレクトリの、任意のテスト関数によって使われます。

doc/ja/example/nonpython.txt

@@ -1,112 +0,0 @@
-
-.. _`non-python tests`:
-
-Python 以外のテストを扱う
-=========================
-
-..
-    Working with non-python tests
-    ====================================================
-
-.. _`yaml plugin`:
-
-Yaml ファイルでテストを指定する基本的なサンプル
------------------------------------------------
-
-..
-    A basic example for specifying tests in Yaml files
-    --------------------------------------------------------------
-
-.. _`pytest-yamlwsgi`: http://bitbucket.org/aafshar/pytest-yamlwsgi/src/tip/pytest_yamlwsgi.py
-.. _`PyYAML`: http://pypi.python.org/pypi/PyYAML/
-
-..
-    Here is an example ``conftest.py`` (extracted from Ali Afshnars special purpose `pytest-yamlwsgi`_ plugin).   This ``conftest.py`` will  collect ``test*.yml`` files and will execute the yaml-formatted content as custom tests:
-
-``conftest.py`` (Ali Afshnars の特殊用途の `pytest-yamlwsgi`_ プラグインから引用) のサンプルを紹介します。この ``conftest.py`` は ``test*.yml`` ファイルを探してきて、yaml フォーマットのコンテンツをカスタムテストとして実行します:
-
-.. include:: nonpython/conftest.py
-    :literal:
-
-..
-    You can create a simple example file:
-
-簡単なサンプルファイルを作成します:
-
-.. include:: nonpython/test_simple.yml
-    :literal:
-
-..
-    and if you installed `PyYAML`_ or a compatible YAML-parser you can
-    now execute the test specification::
-
-`PyYAML`_ か、互換性のある YAML パーサーをインストール済みなら、そのテスト仕様を実行できます::
-
-    nonpython $ py.test test_simple.yml
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    
-    test_simple.yml .F
-    
-    ================================= FAILURES =================================
-    ______________________________ usecase: hello ______________________________
-    usecase execution failed
-       spec failed: 'some': 'other'
-       no further details known at this point.
-    ==================== 1 failed, 1 passed in 0.06 seconds ====================
-
-..
-    You get one dot for the passing ``sub1: sub1`` check and one failure.
-    Obviously in the above ``conftest.py`` you'll want to implement a more
-    interesting interpretation of the yaml-values.  You can easily write
-    your own domain specific testing language this way.
-
-``sub1: sub1`` は成功してドットを1つ表示し、もう1つは失敗します。上述した ``conftest.py`` は言うまでもなく単純なので、もっとおもしろい yaml 値を解釈するサンプルを実装したくなるでしょう。このように独自のドメイン固有テスト言語を簡単に記述できます。
-
-.. note::
-
-    ..
-        ``repr_failure(excinfo)`` is called for representing test failures.
-        If you create custom collection nodes you can return an error
-        representation string of your choice.  It
-        will be reported as a (red) string.
-
-    ``repr_failure(excinfo)`` はテストの失敗を表現するために呼ばれます。カスタムコレクションのノードを作成する場合、好きなエラーを表現する文字列を返せます。それは (赤い) 文字列で表示されます。
-
-..
-    ``reportinfo()`` is used for representing the test location and is also
-    consulted when reporting in ``verbose`` mode::
-
-``reportinfo()`` はテストの位置を表現したり、 ``verbose`` モードではレポート時にも使われます::
-
-    nonpython $ py.test -v
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4 -- /home/hpk/venv/0/bin/python
-    collecting ... collected 2 items
-    
-    test_simple.yml:1: usecase: ok PASSED
-    test_simple.yml:1: usecase: hello FAILED
-    
-    ================================= FAILURES =================================
-    ______________________________ usecase: hello ______________________________
-    usecase execution failed
-       spec failed: 'some': 'other'
-       no further details known at this point.
-    ==================== 1 failed, 1 passed in 0.06 seconds ====================
-
-..
-    While developing your custom test collection and execution it's also
-    interesting to just look at the collection tree::
-
-カスタムテストコレクションや実行処理の開発中、そのコレクションツリーをちょっと見るのもおもしろいです::
-
-    nonpython $ py.test --collect-only
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    <YamlFile 'test_simple.yml'>
-      <YamlItem 'ok'>
-      <YamlItem 'hello'>
-    
-    =============================  in 0.07 seconds =============================

doc/ja/example/nonpython/conftest.py

@@ -1,40 +0,0 @@
-# content of conftest.py
-
-import pytest
-
-def pytest_collect_file(path, parent):
-    if path.ext == ".yml" and path.basename.startswith("test"):
-        return YamlFile(path, parent)
-            
-class YamlFile(pytest.File):
-    def collect(self):
-        import yaml # we need a yaml parser, e.g. PyYAML
-        raw = yaml.load(self.fspath.open())
-        for name, spec in raw.items():
-            yield YamlItem(name, self, spec)
-
-class YamlItem(pytest.Item):
-    def __init__(self, name, parent, spec):
-        super(YamlItem, self).__init__(name, parent)
-        self.spec = spec
-    
-    def runtest(self):
-        for name, value in self.spec.items():
-            # some custom test execution (dumb example follows)
-            if name != value:
-                raise YamlException(self, name, value)
-
-    def repr_failure(self, excinfo):
-        """ called when self.runtest() raises an exception. """
-        if isinstance(excinfo.value, YamlException):
-            return "\n".join([
-                "usecase execution failed",
-                "   spec failed: %r: %r" % excinfo.value.args[1:3],
-                "   no further details known at this point."
-            ])
-
-    def reportinfo(self):
-        return self.fspath, 0, "usecase: %s" % self.name
-
-class YamlException(Exception):
-    """ custom exception for error reporting. """

doc/ja/example/nonpython/test_simple.yml

@@ -1,7 +0,0 @@
-# test_simple.yml
-ok:
-    sub1: sub1
-
-hello:
-    world: world
-    some: other

doc/ja/example/parametrize.txt

@@ -1,425 +0,0 @@
-
-.. _paramexamples:
-
-パラメーターテスト
-==================
-
-..
-    Parametrizing tests
-    =================================================
-
-.. currentmodule:: _pytest.python
-
-py.test は、簡単にパラメーターをテスト関数へ渡せます。パラメーターテストを行うための組み込みの仕組みを使ったサンプルを紹介します。
-
-..
-    py.test allows to easily parametrize test functions.
-    In the following we provide some examples using
-    the builtin mechanisms.
-
-.. _parametrizemark:
-
-シンプルな "デコレーター" によるパラメーターテスト
---------------------------------------------------
-
-..
-    Simple "decorator" parametrization of a test function
-    ----------------------------------------------------------------------------
-
-.. versionadded:: 2.2
-
-..
-    The builtin ``pytest.mark.parametrize`` decorator directly enables
-    parametrization of arguments for a test function.  Here is an example
-    of a test function that wants to compare that processing some input
-    results in expected output::
-
-組み込みの ``pytest.mark.parametrize`` デコレーターは、直接、テスト関数の引数へパラメーターを渡せます。入力値を処理して、その結果として期待される出力値を比較したいテスト関数のサンプルを紹介します::
-
-    # test_expectation.py の内容
-    import pytest
-    @pytest.mark.parametrize(("input", "expected"), [
-        ("3+5", 8),
-        ("2+4", 6),
-        ("6*9", 42),
-    ])
-    def test_eval(input, expected):
-        assert eval(input) == expected
-
-..
-    we parametrize two arguments of the test function so that the test
-    function is called three times.  Let's run it::
-
-テスト関数が3回呼び出され、そのテスト関数へ2つの引数をパラメーターとして渡します。実行してみましょう::
-
-    $ py.test -q 
-    collecting ... collected 3 items
-    ..F
-    ================================= FAILURES =================================
-    ____________________________ test_eval[6*9-42] _____________________________
-    
-    input = '6*9', expected = 42
-    
-        @pytest.mark.parametrize(("input", "expected"), [
-            ("3+5", 8),
-            ("2+4", 6),
-            ("6*9", 42),
-        ])
-        def test_eval(input, expected):
-    >       assert eval(input) == expected
-    E       assert 54 == 42
-    E        +  where 54 = eval('6*9')
-    
-    test_expectation.py:8: AssertionError
-    1 failed, 2 passed in 0.01 seconds
-
-..
-    As expected only one pair of input/output values fails the simple test function.
-
-期待した通り、入力値／出力値の組み合わせの1つだけがこの単純なテスト関数を失敗させます。
-
-..
-    Note that there are various ways how you can mark groups of functions,
-    see :ref:`mark`.
-
-関数のグループをマークする方法は様々なやり方があるのに注意してください。詳細は :ref:`mark` を参照してください。
-
-..
-    Generating parameters combinations, depending on command line
-    ----------------------------------------------------------------------------
-
-コマンドラインからパラメーターの組み合わせを作成
-------------------------------------------------
-
-.. regendoc:wipe
-
-..
-    Let's say we want to execute a test with different computation
-    parameters and the parameter range shall be determined by a command
-    line argument.  Let's first write a simple (do-nothing) computation test::
-
-別のパラメーターでテストを実行したいときに、そのパラメーターの範囲はコマンドライン引数によって決まるものとしましょう。最初の簡単な (何もしない) テストを書いてみます::
-
-    # test_compute.py の内容
-
-    def test_compute(param1):
-        assert param1 < 4
-
-..
-    Now we add a test configuration like this::
-
-次のようなテスト設定を追加します::
-
-    # conftest.py の内容
-
-    def pytest_addoption(parser):
-        parser.addoption("--all", action="store_true",
-            help="run all combinations")
-
-    def pytest_generate_tests(metafunc):
-        if 'param1' in metafunc.fixturenames:
-            if metafunc.config.option.all:
-                end = 5
-            else:
-                end = 2
-            metafunc.parametrize("param1", range(end))
-
-..
-    This means that we only run 2 tests if we do not pass ``--all``::
-
-これは ``--all`` を指定しない場合、2回だけテストを実行します::
-
-    $ py.test -q test_compute.py
-    collecting ... collected 2 items
-    ..
-    2 passed in 0.01 seconds
-
-..
-    We run only two computations, so we see two dots.
-    let's run the full monty::
-
-2回だけテストを実行するので、ドットが2つ表示されます。では、全テストを実行してみましょう::
-
-    $ py.test -q --all
-    collecting ... collected 5 items
-    ....F
-    ================================= FAILURES =================================
-    _____________________________ test_compute[4] ______________________________
-    
-    param1 = 4
-    
-        def test_compute(param1):
-    >       assert param1 < 4
-    E       assert 4 < 4
-    
-    test_compute.py:3: AssertionError
-    1 failed, 4 passed in 0.02 seconds
-
-..
-    As expected when running the full range of ``param1`` values
-    we'll get an error on the last one.
-
-期待した通り ``param1`` の全ての範囲値を実行すると、最後の1つがエラーになります。
-
-..
-    A quick port of "testscenarios"
-    ------------------------------------
-
-"testscenarios" の手早い移行
-----------------------------
-
-.. _`test scenarios`: http://bazaar.launchpad.net/~lifeless/testscenarios/trunk/annotate/head%3A/doc/example.py
-
-..
-    Here is a quick port to run tests configured with `test scenarios`_,
-    an add-on from Robert Collins for the standard unittest framework. We
-    only have to work a bit to construct the correct arguments for pytest's
-    :py:func:`Metafunc.parametrize`::
-
-Robert Collins による標準ライブラリの unittest フレームワークのアドオンである `test scenarios`_ で設定されたテストを実行するために手早い移行方法を紹介します。pytest の :py:func:`Metafunc.parametrize` へ渡す正しい引数を作成するために少しだけコーディングが必要です::
-
-    # test_scenarios.py の内容
-
-    def pytest_generate_tests(metafunc):
-        idlist = []
-        argvalues = []
-        for scenario in metafunc.cls.scenarios:
-            idlist.append(scenario[0])
-            items = scenario[1].items()
-            argnames = [x[0] for x in items]
-            argvalues.append(([x[1] for x in items]))
-        metafunc.parametrize(argnames, argvalues, ids=idlist)
-
-    scenario1 = ('basic', {'attribute': 'value'})
-    scenario2 = ('advanced', {'attribute': 'value2'})
-
-    class TestSampleWithScenarios:
-        scenarios = [scenario1, scenario2]
-
-        def test_demo(self, attribute):
-            assert isinstance(attribute, str)
-
-..
-    this is a fully self-contained example which you can run with::
-
-これはすぐ実行できる完全な自己完結型サンプルです::
-
-    $ py.test test_scenarios.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    
-    test_scenarios.py ..
-    
-    ========================= 2 passed in 0.01 seconds =========================
-
-..
-    If you just collect tests you'll also nicely see 'advanced' and 'basic' as variants for the test function::
-
-ただテストを (実行せずに) 集めるだけなら、テスト関数の変数として 'advanced' と 'basic' もうまく表示されます::
-
-    $ py.test --collect-only test_scenarios.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    <Module 'test_scenarios.py'>
-      <Class 'TestSampleWithScenarios'>
-        <Instance '()'>
-          <Function 'test_demo[basic]'>
-          <Function 'test_demo[advanced]'>
-    
-    =============================  in 0.00 seconds =============================
-
-..
-    Deferring the setup of parametrized resources
-    ---------------------------------------------------
-
-パラメーター化されたリソースの遅延セットアップ
-----------------------------------------------
-
-.. regendoc:wipe
-
-..
-    The parametrization of test functions happens at collection
-    time.  It is a good idea to setup expensive resources like DB
-    connections or subprocess only when the actual test is run.
-    Here is a simple example how you can achieve that, first
-    the actual test requiring a ``db`` object::
-
-テスト関数へのパラメーター渡しはコレクション時に発生します。実際にテストを実行するときのみ、DB コネクションやサブプロセスといった高価なリソースをセットアップするのは良い考えです。そういったテストを行う簡単なサンプルが次になります。最初のテストは ``db`` オブジェクトを要求します::
-
-    # test_backends.py の内容
-
-    import pytest
-    def test_db_initialized(db):
-        # ダミーテスト
-        if db.__class__.__name__ == "DB2":
-            pytest.fail("deliberately failing for demo purposes")
-
-..
-    We can now add a test configuration that generates two invocations of
-    the ``test_db_initialized`` function and also implements a factory that
-    creates a database object for the actual test invocations::
-
-``test_db_initialized`` 関数の2回実行するようにテスト設定を追加します。さらに実際のテスト実行時にデータベースオブジェクトを作成するファクトリー関数も実装します::
-
-    # conftest.py の内容
-
-    def pytest_generate_tests(metafunc):
-        if 'db' in metafunc.fixturenames:
-            metafunc.parametrize("db", ['d1', 'd2'], indirect=True)
-
-    class DB1:
-        "one database object"
-    class DB2:
-        "alternative database object"
-
-    def pytest_funcarg__db(request):
-        if request.param == "d1":
-            return DB1()
-        elif request.param == "d2":
-            return DB2()
-        else:
-            raise ValueError("invalid internal test config")
-
-..
-    Let's first see how it looks like at collection time::
-
-コレクション時に先ほどの設定がどうなるかを最初に見てみましょう::
-
-    $ py.test test_backends.py --collect-only
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    <Module 'test_backends.py'>
-      <Function 'test_db_initialized[d1]'>
-      <Function 'test_db_initialized[d2]'>
-    
-    =============================  in 0.00 seconds =============================
-
-..
-    And then when we run the test::
-
-それからテストを実行します::
-
-    $ py.test -q test_backends.py
-    collecting ... collected 2 items
-    .F
-    ================================= FAILURES =================================
-    _________________________ test_db_initialized[d2] __________________________
-    
-    db = <conftest.DB2 instance at 0x1d4eb00>
-    
-        def test_db_initialized(db):
-            # ダミーテスト
-            if db.__class__.__name__ == "DB2":
-    >           pytest.fail("deliberately failing for demo purposes")
-    E           Failed: deliberately failing for demo purposes
-    
-    test_backends.py:6: Failed
-    1 failed, 1 passed in 0.01 seconds
-
-..
-    The first invocation with ``db == "DB1"`` passed while the second with ``db == "DB2"`` failed.  Our ``pytest_funcarg__db`` factory has instantiated each of the DB values during the setup phase while the ``pytest_generate_tests`` generated two according calls to the ``test_db_initialized`` during the collection phase.
-
-最初の ``db == "DB1"`` による実行が成功したのに対して、2番目の ``db == "DB2"`` は失敗しました。 ``pytest_funcarg__db`` ファクトリーは、セットアップフェーズのときにそれぞれの DB 値をインスタンス化しました。一方 ``pytest_generate_tests`` は、コレクションフェーズのときに2回の ``test_db_initialized`` 呼び出しを生成しました。
-
-.. regendoc:wipe
-
-..
-    Parametrizing test methods through per-class configuration
-    --------------------------------------------------------------
-
-クラス設定毎のテストメソッドのパラメーター渡し
-----------------------------------------------
-
-.. _`unittest parameterizer`: http://code.google.com/p/unittest-ext/source/browse/trunk/params.py
-
-..
-    Here is an example ``pytest_generate_function`` function implementing a
-    parametrization scheme similar to Michael Foord's `unittest
-    parameterizer`_ but in a lot less code::
-
-Michael Foord の `unittest parameterizer`_ とよく似ていますが、それよりもずっと少ないコードでパラメーターを渡す仕組みを実装する ``pytest_generate_function`` 関数のサンプルがあります::
-
-    # ./test_parametrize.py の内容
-    import pytest
-
-    def pytest_generate_tests(metafunc):
-        # それぞれのテスト関数毎に1回呼び出される
-        funcarglist = metafunc.cls.params[metafunc.function.__name__]
-        argnames = list(funcarglist[0])
-        metafunc.parametrize(argnames, [[funcargs[name] for name in argnames]
-                for funcargs in funcarglist])
-
-    class TestClass:
-        # テストメソッドのために複数の引数セットを指定するディクショナリ
-        params = {
-            'test_equals': [dict(a=1, b=2), dict(a=3, b=3), ],
-            'test_zerodivision': [dict(a=1, b=0), ],
-        }
-
-        def test_equals(self, a, b):
-            assert a == b
-
-        def test_zerodivision(self, a, b):
-            pytest.raises(ZeroDivisionError, "a/b")
-
-..
-    Our test generator looks up a class-level definition which specifies which
-    argument sets to use for each test function.  Let's run it::
-
-テストジェネレーターは、それぞれのテストメソッドへどの引数セットを渡すかを特定するクラスレベルの定義を調べます。実行してみましょう::
-
-    $ py.test -q
-    collecting ... collected 3 items
-    F..
-    ================================= FAILURES =================================
-    ________________________ TestClass.test_equals[1-2] ________________________
-    
-    self = <test_parametrize.TestClass instance at 0x10d2e18>, a = 1, b = 2
-    
-        def test_equals(self, a, b):
-    >       assert a == b
-    E       assert 1 == 2
-    
-    test_parametrize.py:18: AssertionError
-    1 failed, 2 passed in 0.01 seconds
-
-..
-    Indirect parametrization with multiple resources
-    --------------------------------------------------------------
-
-複数リソースでの間接的なパラメーター渡し
-----------------------------------------
-
-..
-    Here is a stripped down real-life example of using parametrized
-    testing for testing serialization, invoking different python interpreters.
-    We define a ``test_basic_objects`` function which is to be run
-    with different sets of arguments for its three arguments:
-
-別々の Python インタープリターで実行し、シリアライズ化を検証するのにパラメーターテストを使う、実際の世界でのサンプルを解説します。次の3つの引数を全組み合わせで実行する ``test_basic_objects`` 関数を定義します。
-
-..
-    * ``python1``: first python interpreter, run to pickle-dump an object to a file
-    * ``python2``: second interpreter, run to pickle-load an object from a file
-    * ``obj``: object to be dumped/loaded
-
-* ``python1`` : 1番目の Python インタープリター、オブジェクトをファイルへ pickle-dump するために実行
-* ``python2`` : 2番目の Python インタープリター、ファイルからオブジェクトを pickle-load するために実行
-* ``obj`` : ダンプしたり読み込むためのオブジェクト
-
-.. literalinclude:: multipython.py
-
-..
-    Running it results in some skips if we don't have all the python interpreters installed and otherwise runs all combinations (5 interpreters times 5 interpreters times 3 objects to serialize/deserialize)::
-
-もし全ての Python インタープリターがインストールされていない場合、実行してもスキップされます。インストール済みの場合、全ての組み合わせが実行されます (5つのインタープリター * 5つのインタープリター * 3つのシリアライズ／デシリアライズするオブジェクト)::
-
-   . $ py.test -rs -q multipython.py
-   collecting ... collected 75 items
-   ............sss............sss............sss............ssssssssssssssssss
-   ========================= short test summary info ==========================
-   SKIP [27] /home/hpk/p/pytest/doc/example/multipython.py:36: 'python2.8' not found
-   48 passed, 27 skipped in 1.71 seconds

doc/ja/example/py2py3/conftest.py

@@ -1,16 +0,0 @@
-import sys
-import pytest
-
-py3 = sys.version_info[0] >= 3
-
-class DummyCollector(pytest.collect.File):
-    def collect(self):
-        return []
-
-def pytest_pycollect_makemodule(path, parent):
-    bn = path.basename
-    if "py3" in bn and not py3 or ("py2" in bn and py3):
-        return DummyCollector(path, parent=parent)
-
-
-

doc/ja/example/py2py3/test_py2.py

@@ -1,7 +0,0 @@
-
-def test_exception_syntax():
-    try:
-        0/0
-    except ZeroDivisionError, e:
-        assert 0, e
-

doc/ja/example/py2py3/test_py3.py

@@ -1,7 +0,0 @@
-
-def test_exception_syntax():
-    try:
-        0/0
-    except ZeroDivisionError as e:
-        assert 0, e
-

doc/ja/example/pythoncollection.py

@@ -1,11 +0,0 @@
-
-# run this with $ py.test --collect-only test_collectonly.py
-#
-def test_function():
-    pass
-
-class TestClass:
-    def test_method(self):
-        pass
-    def test_anothermethod(self):
-        pass

doc/ja/example/pythoncollection.txt

@@ -1,141 +0,0 @@
-標準的な (Python) テスト探索の変更
-==================================
-
-..
-    Changing standard (Python) test discovery
-    ===============================================
-
-..
-    Changing directory recursion
-    -----------------------------------------------------
-
-ディレクトリの再帰探索の変更
-----------------------------
-
-..
-    You can set the :confval:`norecursedirs` option in an ini-file, for example your ``setup.cfg`` in the project root directory::
-
-ini ファイルで :confval:`norecursedirs` オプションを設定できます。例えば、プロジェクトのルートディレクトリにある ``setup.cfg`` に設定します::
-
-    # setup.cfg の内容
-    [pytest]
-    norecursedirs = .svn _build tmp*
-
-..
-    This would tell py.test to not recurse into typical subversion or sphinx-build directories or into any ``tmp`` prefixed directory.
-
-これは典型的な subversion と sphinx の build ディレクトリと ``tmp`` という接頭辞をもつディレクトリを再帰探索しない設定です。
-
-.. _`change naming conventions`:
-
-命名規則の変更
---------------
-
-..
-    Changing naming conventions
-    -----------------------------------------------------
-
-..
-    You can configure different naming conventions by setting
-    the :confval:`python_files`, :confval:`python_classes` and
-    :confval:`python_functions` configuration options.  Example::
-
-:confval:`python_files`, :confval:`python_classes`, :confval:`python_functions` オプションを設定することで別の命名規則を使うこともできます。サンプルを紹介します::
-
-    # setup.cfg の内容
-    # tox.ini または pytest.init ファイルでも定義できる
-    [pytest]
-    python_files=check_*.py
-    python_classes=Check
-    python_functions=check
-
-..
-    This would make py.test look for ``check_`` prefixes in
-    Python filenames, ``Check`` prefixes in classes and ``check`` prefixes
-    in functions and classes.  For example, if we have::
-
-この設定は Python ファイル名に ``check_`` 、 クラス名に ``Check`` 、関数名に ``check`` という接頭辞を py.test が探すようにします。例えば、次のようなファイルです::
-
-    # check_myapp.py の内容
-    class CheckMyApp:
-        def check_simple(self):
-            pass
-        def check_complex(self):
-            pass
-
-..
-    then the test collection looks like this::
-
-テストコレクションは次のようになります::
-
-    $ py.test --collect-only
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 2 items
-    <Module 'check_myapp.py'>
-      <Class 'CheckMyApp'>
-        <Instance '()'>
-          <Function 'check_simple'>
-          <Function 'check_complex'>
-    
-    =============================  in 0.00 seconds =============================
-
-..
-    Interpreting cmdline arguments as Python packages
-    -----------------------------------------------------
-
-Python パッケージとしてコマンドライン引数を解釈
------------------------------------------------
-
-..
-    You can use the ``--pyargs`` option to make py.test try
-    interpreting arguments as python package names, deriving
-    their file system path and then running the test. For
-    example if you have unittest2 installed you can type::
-
-py.test がファイルシステムのパスから Python パッケージ名として引数を解釈するように ``--pyargs`` オプションを使えます。例えば、unittest2 をインストール済みなら、次のように指定できます::
-
-    py.test --pyargs unittest2.test.test_skipping -q
-
-..
-    which would run the respective test module.  Like with
-    other options, through an ini-file and the :confval:`addopts` option you
-    can make this change more permanently::
-
-それぞれのテストモジュールを実行します。その他のオプションと同様に ini ファイルと :confval:`addopts` オプションにより、この変更を永続化できます::
-
-    # pytest.ini の内容
-    [pytest]
-    addopts = --pyargs
-
-..
-    Now a simple invocation of ``py.test NAME`` will check
-    if NAME exists as an importable package/module and otherwise
-    treat it as a filesystem path.
-
-単純に ``py.test NAME`` を実行すると、NAME がインポート可能なパッケージ／モジュールとして存在しているかどうかをチェックします。存在しない場合、ファイルシステム上のパスとして NAME を扱います。
-
-..
-    Finding out what is collected
-    -----------------------------------------------
-
-コレクションの探索
-------------------
-
-..
-    You can always peek at the collection tree without running tests like this::
-
-次のようにテストを実行せずにコレクションツリーをピークできます::
-
-    . $ py.test --collect-only pythoncollection.py
-    =========================== test session starts ============================
-    platform linux2 -- Python 2.7.1 -- pytest-2.2.4
-    collecting ... collected 3 items
-    <Module 'pythoncollection.py'>
-      <Function 'test_function'>
-      <Class 'TestClass'>
-        <Instance '()'>
-          <Function 'test_method'>
-          <Function 'test_anothermethod'>
-    
-    =============================  in 0.00 seconds =============================