Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pytest-runner to 5.3.1 #1201

Closed
wants to merge 1 commit into from

Conversation

pyup-bot
Copy link
Collaborator

This PR updates pytest-runner from 3.0 to 5.3.1.

Changelog

5.3.1

======

* Refreshed package metadata.

5.3.0

======

* Require Python 3.6 or later.
* Refreshed package metadata.

5.2

===

* 50: This project is deprecated.

5.1

===

* 49: Surgically restore support for older setuptools versions.

5.0

===

* 42: Prefer pyproject.toml
* Refresh package metadata.
* This release now intentionally introduces the changes
unintionally brought about in 4.5 and 4.3, where the
adoption of declarative config adds a new requirement
on setuptools 30.4 or later. On systems running older
setuptools, installation of pytest-runner via
``easy_install`` (or ``setup_requires``), will result
in a ``DistributionNotFound`` exception.

All projects should pin to ``pytest-runner < 5``
or upgrade the environment to ``setuptools >= 30.4``
(prior to invoking setup.py).

4.5.1

=====

* 48: Revert changes from 4.5 - restoring project to the
state at 4.4.

4.5

===

(Pulled from PyPI due to 43 and 48)

* Packaging (skeleton) refresh, including adoption of
`black <https://pypi.org/project/black>`_ for style.

4.4

===

* 43: Detect condition where declarative config will cause
errors and emit a UserWarning with guidance on necessary
actions.

4.3.1

=====

* 43: Re-release of 4.2 to supersede the 4.3 release which
proved to be backward-incompatible in that it requires
setuptools 30.4 or possibly later (to install). In the future, a
backward-incompatible release will re-release these changes.
For projects including pytest-runner, particularly as
``setup_requires``, if support for older setuptools is required,
please pin to ``pytest-runner < 5``.

4.3

===

(Pulled from PyPI due to 43)

* 42: Update project metadata, including pyproject.toml declaration.

4.2

===

* 40: Remove declared dependency and instead assert it at
run time.

4.1

===

* 40: Declare dependency on Setuptools in package metadata.

4.0

===

* Drop support for Setuptools before Setuptools 27.3.0.

3.0.1

=====

* 38: Fixed AttributeError when running with ``--dry-run``.
``PyTest.run()`` no longer stores nor returns the result code.
Based on the commit message for `840ff4c <
https://github.com/pytest-dev/pytest-runner/commit/840ff4c2bf6c752d9770f0dd8d64a841060cf9bc>`_,
nothing has ever relied on that value.
Links

@codecov-commenter
Copy link

Codecov Report

Merging #1201 (68d5ce8) into master (7ab5b29) will increase coverage by 1.62%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1201      +/-   ##
==========================================
+ Coverage   35.38%   37.00%   +1.62%     
==========================================
  Files          30       31       +1     
  Lines        3103     3259     +156     
==========================================
+ Hits         1098     1206     +108     
- Misses       2005     2053      +48     
Impacted Files Coverage Δ
stackformation/__init__.py 69.23% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ab5b29...68d5ce8. Read the comment docs.

@pyup-bot
Copy link
Collaborator Author

Closing this in favor of #1457

@pyup-bot pyup-bot closed this Feb 25, 2022
@ibejohn818 ibejohn818 deleted the pyup-update-pytest-runner-3.0-to-5.3.1 branch February 25, 2022 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants