Remove setup.py test now that it's broken #3552
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @asottile! |
|
Oh just realized we would need a |
|
on it! I always forget 😕 |
|
as far as external api is concerned, taking away setup.py test is a breaking change, even if it was broken by accient ^^ |
nicoddemus
added a commit
that referenced
this pull request
Jun 9, 2018
Add changelog entry for #3552
|
@RonnyPfannschmidt I agree in general, but in this case it was broken for a few major releases now without people noticing, so I think it is OK to just remove it. |
|
The SRC move made things apparent, that was recent |
|
Indeed |
guykisel
referenced
this pull request
in guykisel/inline-plz
Jul 6, 2018
This PR updates [pytest](https://pypi.org/project/pytest) from **3.5.1** to **3.6.3**. <details> <summary>Changelog</summary> ### 3.6.2 ``` ========================= Bug Fixes --------- - Fix regression in ``Node.add_marker`` by extracting the mark object of a ``MarkDecorator``. (`3555 <https://github.com/pytest-dev/pytest/issues/3555>`_) - Warnings without ``location`` were reported as ``None``. This is corrected to now report ``<undetermined location>``. (`3563 <https://github.com/pytest-dev/pytest/issues/3563>`_) - Continue to call finalizers in the stack when a finalizer in a former scope raises an exception. (`3569 <https://github.com/pytest-dev/pytest/issues/3569>`_) - Fix encoding error with `print` statements in doctests (`3583 <https://github.com/pytest-dev/pytest/issues/3583>`_) Improved Documentation ---------------------- - Add documentation for the ``--strict`` flag. (`3549 <https://github.com/pytest-dev/pytest/issues/3549>`_) Trivial/Internal Changes ------------------------ - Update old quotation style to parens in fixture.rst documentation. (`3525 <https://github.com/pytest-dev/pytest/issues/3525>`_) - Improve display of hint about ``--fulltrace`` with ``KeyboardInterrupt``. (`3545 <https://github.com/pytest-dev/pytest/issues/3545>`_) - pytest's testsuite is no longer runnable through ``python setup.py test`` -- instead invoke ``pytest`` or ``tox`` directly. (`3552 <https://github.com/pytest-dev/pytest/issues/3552>`_) - Fix typo in documentation (`3567 <https://github.com/pytest-dev/pytest/issues/3567>`_) ``` ### 3.6.1 ``` ========================= Bug Fixes --------- - Fixed a bug where stdout and stderr were logged twice by junitxml when a test was marked xfail. (`3491 <https://github.com/pytest-dev/pytest/issues/3491>`_) - Fix ``usefixtures`` mark applyed to unittest tests by correctly instantiating ``FixtureInfo``. (`3498 <https://github.com/pytest-dev/pytest/issues/3498>`_) - Fix assertion rewriter compatibility with libraries that monkey patch ``file`` objects. (`3503 <https://github.com/pytest-dev/pytest/issues/3503>`_) Improved Documentation ---------------------- - Added a section on how to use fixtures as factories to the fixture documentation. (`3461 <https://github.com/pytest-dev/pytest/issues/3461>`_) Trivial/Internal Changes ------------------------ - Enable caching for pip/pre-commit in order to reduce build time on travis/appveyor. (`3502 <https://github.com/pytest-dev/pytest/issues/3502>`_) - Switch pytest to the src/ layout as we already suggested it for good practice - now we implement it as well. (`3513 <https://github.com/pytest-dev/pytest/issues/3513>`_) - Fix if in tests to support 3.7.0b5, where a docstring handling in AST got reverted. (`3530 <https://github.com/pytest-dev/pytest/issues/3530>`_) - Remove some python2.5 compatibility code. (`3529 <https://github.com/pytest-dev/pytest/issues/3529>`_) ``` ### 3.6.0 ``` ========================= Features -------- - Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to read the `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.htmlmarker-revamp-and-iteration>`_, or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.htmlupdating-code>`_. (`3317 <https://github.com/pytest-dev/pytest/issues/3317>`_) - Now when ``pytest.fixture`` is applied more than once to the same function a ``ValueError`` is raised. This buggy behavior would cause surprising problems and if was working for a test suite it was mostly by accident. (`2334 <https://github.com/pytest-dev/pytest/issues/2334>`_) - Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the builtin breakpoint function <https://docs.pytest.org/en/latest/usage.htmlbreakpoint-builtin>`_ for details. (`3180 <https://github.com/pytest-dev/pytest/issues/3180>`_) - ``monkeypatch`` now supports a ``context()`` function which acts as a context manager which undoes all patching done within the ``with`` block. (`3290 <https://github.com/pytest-dev/pytest/issues/3290>`_) - The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, instead of stopping the test session. On python 2.7, hitting CTRL+C again exits the debugger. On python 3.2 and higher, use CTRL+D. (`3299 <https://github.com/pytest-dev/pytest/issues/3299>`_) - pytest not longer changes the log level of the root logger when the ``log-level`` parameter has greater numeric value than that of the level of the root logger, which makes it play better with custom logging configuration in user code. (`3307 <https://github.com/pytest-dev/pytest/issues/3307>`_) Bug Fixes --------- - A rare race-condition which might result in corrupted ``.pyc`` files on Windows has been hopefully solved. (`3008 <https://github.com/pytest-dev/pytest/issues/3008>`_) - Also use iter_marker for discovering the marks applying for marker expressions from the cli to avoid the bad data from the legacy mark storage. (`3441 <https://github.com/pytest-dev/pytest/issues/3441>`_) - When showing diffs of failed assertions where the contents contain only whitespace, escape them using ``repr()`` first to make it easy to spot the differences. (`3443 <https://github.com/pytest-dev/pytest/issues/3443>`_) Improved Documentation ---------------------- - Change documentation copyright year to a range which auto-updates itself each time it is published. (`3303 <https://github.com/pytest-dev/pytest/issues/3303>`_) Trivial/Internal Changes ------------------------ - ``pytest`` now depends on the `python-atomicwrites <https://github.com/untitaker/python-atomicwrites>`_ library. (`3008 <https://github.com/pytest-dev/pytest/issues/3008>`_) - Update all pypi.python.org URLs to pypi.org. (`3431 <https://github.com/pytest-dev/pytest/issues/3431>`_) - Detect `pytest_` prefixed hooks using the internal plugin manager since ``pluggy`` is deprecating the ``implprefix`` argument to ``PluginManager``. (`3487 <https://github.com/pytest-dev/pytest/issues/3487>`_) - Import ``Mapping`` and ``Sequence`` from ``_pytest.compat`` instead of directly from ``collections`` in ``python_api.py::approx``. Add ``Mapping`` to ``_pytest.compat``, import it from ``collections`` on python 2, but from ``collections.abc`` on Python 3 to avoid a ``DeprecationWarning`` on Python 3.7 or newer. (`3497 <https://github.com/pytest-dev/pytest/issues/3497>`_) ``` </details> <details> <summary>Links</summary> - PyPI: https://pypi.org/project/pytest - Changelog: https://pyup.io/changelogs/pytest/ - Repo: https://github.com/pytest-dev/pytest/issues - Homepage: http://pytest.org </details>
tony
added a commit
to cihai/unihan-etl
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to cihai/unihan-etl
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to cihai/unihan-etl
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to cihai/unihan-db
that referenced
this pull request
Dec 24, 2019
Similar commit in unihan-etl: - cihai/unihan-etl@051bd6d - cihai/unihan-etl#196 More into on setup.py test being removed: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to cihai/cihai
that referenced
this pull request
Dec 24, 2019
In other cihai projects: - cihai/unihan-db@54a6a98 - cihai/unihan-etl@051bd6d setup.py test support being removed in pytest: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to cihai/cihai
that referenced
this pull request
Dec 24, 2019
Similar commits on other cihai projects: - cihai/unihan-db@54a6a98 - cihai/unihan-etl@051bd6d and others Other cihai PRs: - cihai/unihan-etl#196 - cihai/unihan-db#225 More into on setup.py test being removed: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to cihai/cihai-cli
that referenced
this pull request
Dec 24, 2019
In other cihai projects: - cihai/cihai@5bf47d2 - cihai/unihan-db@54a6a98 - cihai/unihan-etl@051bd6d Info on setup.py test being phased out in pytest: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to cihai/cihai-cli
that referenced
this pull request
Dec 24, 2019
In other cihai projects: - cihai/cihai@5bf47d2 - cihai/unihan-db@54a6a98 - cihai/unihan-etl@051bd6d Info on setup.py test being phased out in pytest: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to vcs-python/libvcs
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to cihai/cihai-cli
that referenced
this pull request
Dec 24, 2019
Similar commits in other cihai projects: - cihai/cihai@5bf47d2 - cihai/unihan-db@54a6a98 - cihai/unihan-etl@051bd6d Similar PRs in other cihai projects: - cihai/cihai#244 - cihai/unihan-db#225 - cihai/unihan-etl#196 Pytest references: - http://doc.pytest.org/en/5.3.2/changelog.html#pytest-3-6-2-2018-06-20 - pytest-dev/pytest#3552
tony
added a commit
to vcs-python/vcspull
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to tony/django-docutils
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to tony/django-slugify-processor
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to tmux-python/tmuxp
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to tmux-python/libtmux
that referenced
this pull request
Dec 24, 2019
tony
added a commit
to cihai/unihan-etl
that referenced
this pull request
Sep 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #3543