fix line endings

bench/manyparam.py

@@ -9,4 +9,3 @@ def test_it(foo):
     pass
 def test_it2(foo):
     pass
-

doc/en/_templates/links.html

@@ -6,4 +6,3 @@
   <li><a href="https://github.com/pytest-dev/pytest/issues">Issue Tracker</a></li>
   <li><a href="https://media.readthedocs.org/pdf/pytest/latest/pytest.pdf">PDF Documentation</a>
 </ul>
-

doc/en/announce/release-2.0.3.rst

@@ -37,4 +37,3 @@ Changes between 2.0.2 and 2.0.3
   internally)
 
 - fix issue37: avoid invalid characters in junitxml's output
-

doc/en/announce/release-2.1.1.rst

@@ -34,4 +34,3 @@ Changes between 2.1.0 and 2.1.1
 - 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/en/announce/release-2.1.2.rst

@@ -30,4 +30,3 @@ Changes between 2.1.1 and 2.1.2
 - 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/en/announce/release-2.2.4.rst

@@ -36,4 +36,3 @@ Changes between 2.2.3 and 2.2.4
   configure/sessionstart where called
 - fix issue #144: better mangle test ids to junitxml classnames
 - upgrade distribute_setup.py to 0.6.27
-

doc/en/announce/release-2.3.0.rst

@@ -131,4 +131,3 @@ Changes between 2.2.4 and 2.3.0
   - don't show deselected reason line if there is none
 
   - py.test -vv will show all of assert comparisons instead of truncating
-

doc/en/announce/release-2.3.3.rst

@@ -59,4 +59,3 @@ Changes between 2.3.2 and 2.3.3
 
 - fix issue127 - improve documentation for pytest_addoption() and
   add a ``config.getoption(name)`` helper function for consistency.
-

doc/en/announce/release-2.3.5.rst

@@ -94,4 +94,3 @@ Changes between 2.3.4 and 2.3.5
 - fix issue134 - print the collect errors that prevent running specified test items
 
 - fix issue266 - accept unicode in MarkEvaluator expressions
-

doc/en/announce/release-2.4.0.rst

@@ -222,4 +222,3 @@ Bug fixes:
 - pytest_terminal_summary(terminalreporter) hooks can now use
   ".section(title)" and ".line(msg)" methods to print extra 
   information at the end of a test run.
-

doc/en/announce/release-2.5.0.rst

@@ -172,4 +172,3 @@ holger krekel
   does not duplicate the unittest-API into the "plain" namespace.
 
 - fix verbose reporting for @mock'd test functions
-

doc/en/announce/release-2.5.1.rst

@@ -44,4 +44,3 @@ holger krekel
 
 - fix issue407: fix addoption docstring to point to argparse instead of
   optparse. Thanks Daniel D. Wright.
-

doc/en/announce/release-2.5.2.rst

@@ -61,4 +61,3 @@ holger krekel
   expressions now work better.  Thanks Floris Bruynooghe.
 
 - make capfd/capsys.capture private, its unused and shouldn't be exposed
-

doc/en/announce/release-2.6.1.rst

@@ -56,4 +56,3 @@ Changes 2.6.1
 
 - don't use py.std import helper, rather import things directly.
   Thanks Bruno Oliveira.
-

doc/en/announce/release-2.6.2.rst

@@ -49,4 +49,3 @@ holger krekel
 - Do not mark as universal wheel because Python 2.6 is different from
   other builds due to the extra argparse dependency.  Fixes issue566.
   Thanks sontek.
-

doc/en/announce/release-2.6.3.rst

@@ -49,4 +49,3 @@ Changes 2.6.3
 
 - check xfail/skip also with non-python function test items. Thanks
   Floris Bruynooghe.
-

doc/en/announce/release-2.7.0.rst

@@ -98,4 +98,3 @@ holger krekel
 - On failure, the ``sys.last_value``, ``sys.last_type`` and
   ``sys.last_traceback`` are set, so that a user can inspect the error
   via postmortem debugging (almarklein).
-

doc/en/announce/release-2.7.2.rst

@@ -55,4 +55,3 @@ The py.test Development Team
 
 - fix issue756, fix issue752 (and similar issues): depend on py-1.4.29
   which has a refined algorithm for traceback generation.
-

doc/en/announce/release-2.8.3.rst

@@ -56,4 +56,3 @@ The py.test Development Team
 - extend documentation on the --ignore cli option 
 - use pytest-runner for setuptools integration 
 - minor fixes for interaction with OS X El Capitan system integrity protection (thanks Florian)
-

doc/en/announce/release-2.8.7.rst

@@ -28,4 +28,4 @@ The py.test Development Team
 2.8.7 (compared to 2.8.6)
 -------------------------
 
-- fix #1338: use predictable object resolution for monkeypatch
+- fix #1338: use predictable object resolution for monkeypatch

doc/en/announce/release-2.9.0.rst

@@ -156,4 +156,4 @@ The py.test Development Team
 .. _@tomviner: https://github.com/tomviner
 .. _@RonnyPfannschmidt: https://github.com/RonnyPfannschmidt
 .. _@rabbbit: https://github.com/rabbbit
-.. _@hackebrot: https://github.com/hackebrot
+.. _@hackebrot: https://github.com/hackebrot

doc/en/bash-completion.rst

@@ -23,6 +23,3 @@ For permanent (but not global) ``pytest`` activation, use::
 For one-time activation of argcomplete for ``pytest`` only, use::
 
         eval "$(register-python-argcomplete pytest)"
-
-
-

doc/en/builtin.rst

@@ -120,4 +120,3 @@ You can also interactively ask for help, e.g. by typing on the Python interactiv
 
     import pytest
     help(pytest)
-

doc/en/cache.rst

@@ -260,5 +260,3 @@ by adding the ``--cache-clear`` option like this::
 This is recommended for invocations from Continuous Integration
 servers where isolation and correctness is more important
 than speed.
-
-

doc/en/check_sphinx.py

@@ -13,5 +13,3 @@ def test_linkcheck(tmpdir):
     subprocess.check_call(
         ["sphinx-build", "-blinkcheck",
           "-d", str(doctrees), ".", str(htmldir)])
-
-

doc/en/contact.rst

@@ -47,4 +47,3 @@ Contact channels
 .. _`development mailing list`:
 .. _`pytest-dev at python.org (mailing list)`: http://mail.python.org/mailman/listinfo/pytest-dev
 .. _`pytest-commit at python.org (mailing list)`: http://mail.python.org/mailman/listinfo/pytest-commit
-

doc/en/contents.rst

@@ -62,4 +62,3 @@ Full pytest documentation
       :maxdepth: 1
 
       changelog
-

doc/en/doctest.rst

@@ -168,5 +168,3 @@ by using one of standard doctest modules format in options
     pytest --doctest-modules --doctest-report cdiff
     pytest --doctest-modules --doctest-report ndiff
     pytest --doctest-modules --doctest-report only_first_failure
-
-

doc/en/example/assertion/test_setup_flow_example.py

@@ -39,4 +39,3 @@ Note that ``setup_class(TestStateFullThing)`` is called and not
 to insert ``setup_class = classmethod(setup_class)`` to make
 your setup function callable.
 """
-

doc/en/example/costlysetup/sub_b/test_two.py

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

doc/en/example/py2py3/conftest.py

@@ -11,6 +11,3 @@ 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/en/example/py2py3/test_py2.py

@@ -4,4 +4,3 @@ def test_exception_syntax():
         0/0
     except ZeroDivisionError, e:
         pass
-

doc/en/example/py2py3/test_py3.py

@@ -4,4 +4,3 @@ def test_exception_syntax():
         0/0
     except ZeroDivisionError as e:
         pass
-

doc/en/example/simple.rst

@@ -854,4 +854,3 @@ This allows you to execute tests using the frozen
 application with standard ``pytest`` command-line options::
 
     ./app_main --pytest --verbose --tb=long --junitxml=results.xml test-suite/
-

doc/en/funcarg_compare.rst

@@ -214,5 +214,3 @@ fixtures:
   and simplify your fixture function code to use the :ref:`@pytest.fixture`
   decorator instead.  This will also allow to take advantage of 
   the automatic per-resource grouping of tests.
-
-

doc/en/funcargs.rst

@@ -11,4 +11,3 @@ and you can read on here:
 - :ref:`fixtures`
 - :ref:`parametrize`
 - :ref:`funcargcompare`
-

doc/en/mark.rst

@@ -136,4 +136,3 @@ More details can be found in the `original PR <https://github.com/pytest-dev/pyt
 
 	in a future major relase of pytest we will introduce class based markers,
 	at which points markers will no longer be limited to instances of :py:class:`Mark`
-

doc/en/nose.rst

@@ -70,6 +70,3 @@ Unsupported idioms / known issues
   There are no plans to fix this currently because ``yield``-tests
   are deprecated in pytest 3.0, with ``pytest.mark.parametrize``
   being the recommended alternative.
-
-
-

doc/en/talks.rst

@@ -98,8 +98,3 @@ Plugin specific examples:
 .. _`parametrizing tests, generalized`: http://tetamap.wordpress.com/2009/05/13/parametrizing-python-tests-generalized/
 .. _`generating parametrized tests with fixtures`: parametrize.html#test-generators
 .. _`test generators and cached setup`: http://bruynooghe.blogspot.com/2010/06/pytest-test-generators-and-cached-setup.html
-
-
-
-
-

doc/en/test/index.rst

@@ -31,5 +31,3 @@ changelog_: history of changes covering last releases
 .. _features: features.html
 .. _funcargs: funcargs.html
 .. _customize: customize.html
-
-

doc/en/test/plugin/django.rst

@@ -4,4 +4,3 @@ pytest_django plugin (EXTERNAL)
 pytest_django is a plugin for ``pytest`` that provides a set of useful tools for testing Django applications, checkout Ben Firshman's `pytest_django github page`_.
 
 .. _`pytest_django github page`: http://github.com/bfirsh/pytest_django/tree/master
-

doc/en/writing_plugins.rst

@@ -592,8 +592,3 @@ declaring the hook functions directly in your plugin module, for example::
 
 This has the added benefit of allowing you to conditionally install hooks
 depending on which plugins are installed.
-
-
-
-
-

extra/get_issues.py

@@ -80,4 +80,3 @@ if __name__ == "__main__":
                         help="cache file")
     args = parser.parse_args()
     main(args)
-

testing/freeze/.gitignore

@@ -1,3 +1,3 @@
 build/
 dist/
-*.spec
+*.spec