This file is indexed.

/usr/lib/python3/dist-packages/pytest_runner-2.7.1.egg-info/PKG-INFO is in python3-pytest-runner 2.7.1-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
Metadata-Version: 1.1
Name: pytest-runner
Version: 2.7.1
Summary: Invoke py.test as distutils command with dependency resolution
Home-page: https://github.com/pytest-dev/pytest-runner
Author: Jason R. Coombs
Author-email: jaraco@jaraco.com
License: UNKNOWN
Description: pytest-runner
        =============
        
        Setup scripts can use pytest-runner to add setup.py test support for pytest
        runner.
        
        Usage
        -----
        
        - Add 'pytest-runner' to your 'setup_requires'. Pin to '>=2.0,<3dev' (or
          similar) to avoid pulling in incompatible versions.
        - Include 'pytest' and any other testing requirements to 'tests_require'.
        - Invoke tests with ``setup.py pytest``.
        - Pass ``--index-url`` to have test requirements downloaded from an alternate
          index URL.
        - Pass additional py.test command-line options using ``--addopts``.
        - Set permanent options for the pytest distutils command in the ``[pytest]``
          section of setup.cfg.
        - Set permanent options for the pytest run itself in the ``[pytest]``
          section of pytest.ini or tox.ini. See `pytest 567
          <https://bitbucket.org/pytest-dev/pytest/issues/567/>`_ for details on
          why setup.cfg is inadequate.
        - Optionally, set ``test=pytest`` in the ``[aliases]`` section of setup.cfg
          to cause ``setup.py test`` to invoke pytest.
        
        Example
        -------
        
        The most simple usage looks like this in setup.py::
        
            setup(
                setup_requires=[
                    'pytest-runner',
                ],
                tests_require=[
                    'pytest',
                ],
            )
        
        Additional dependencies require to run the tests (e.g. mock or pytest
        plugins) may be added to tests_require and will be downloaded and
        required by the session before invoking pytest.
        
        See the `jaraco.collections
        <https://github.com/jaraco/jaraco.collections>`_ project
        for real-world usage.
        
        Standalone Example
        ------------------
        
        Although ``pytest-runner`` is typically used to add pytest test
        runner support to maintained packages, ``pytest-runner`` may
        also be used to create standalone tests. Consider `this example
        failure <https://gist.github.com/jaraco/d979a558bc0bf2194c23>`_,
        reported in `jsonpickle #117
        <https://github.com/jsonpickle/jsonpickle/issues/117>`_
        or `this MongoDB test
        <https://gist.github.com/jaraco/0b9e482f5c0a1300dc9a>`_
        demonstrating a technique that works even when dependencies
        are required in the test.
        
        Either example file may be cloned or downloaded and simply run on
        any system with Python and Setuptools. It will download the
        specified dependencies and run the tests. Afterward, the the
        cloned directory can be removed and with it all trace of
        invoking the test. No other dependencies are needed and no
        system configuration is altered.
        
        Then, anyone trying to replicate the failure can do so easily
        and with all the power of pytest (rewritten assertions,
        rich comparisons, interactive debugging, extensibility through
        plugins, etc).
        
        As a result, the communication barrier for describing and
        replicating failures is made almost trivially low.
        
        Considerations
        --------------
        
        Conditional Requirement
        ~~~~~~~~~~~~~~~~~~~~~~~
        
        Because it uses Setuptools setup_requires, pytest-runner will install itself
        on every invocation of setup.py. In some cases, this causes delays for
        invocations of setup.py that will never invoke pytest-runner. To help avoid
        this contingency, consider requiring pytest-runner only when pytest
        is invoked::
        
            needs_pytest = {'pytest', 'test', 'ptr'}.intersection(sys.argv)
            pytest_runner = ['pytest-runner'] if needs_pytest else []
        
            # ...
        
            setup(
                #...
                setup_requires=[
                    #... (other setup requirements)
                ] + pytest_runner,
            )
        
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3