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

Plugins incompatible with pytest 4, leads to ContextualVersionConflict #110

Closed
jaraco opened this issue Jan 17, 2019 · 5 comments
Closed

Comments

@jaraco
Copy link
Contributor

jaraco commented Jan 17, 2019

As can be seen in this commit, none of the plugins are compatible with pytest. This causes test suites that depend on them to fail. Consider:

setuptools master $ pip-run -q pytest pytest-virtualenv -- -c "import pkg_resources; pkg_resources.require('pytest-virtualenv')"                                                         
pytest-shutil 1.4.0 has requirement pytest<4.0.0, but you'll have pytest 4.1.1 which is incompatible.
pytest-fixture-config 1.4.0 has requirement pytest<4.0.0, but you'll have pytest 4.1.1 which is incompatible.
pytest-virtualenv 1.4.0 has requirement pytest<4.0.0, but you'll have pytest 4.1.1 which is incompatible.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/jaraco/code/main/setuptools/pkg_resources/__init__.py", line 898, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/Users/jaraco/code/main/setuptools/pkg_resources/__init__.py", line 789, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (pytest 4.1.1 (/private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-svi02ctd), Requirement.parse('pytest<4.0.0'), {'pytest-shutil', 'pytest-fixture-config', 'pytest-virtualenv'})
@jonathansp
Copy link
Contributor

@javefang @eeaston any specific reason this plugin is not compatible with v4.x.x?

jaraco added a commit to pytest-dev/pytest-runner that referenced this issue Feb 14, 2019
jaraco added a commit to pytest-dev/pytest-runner that referenced this issue Feb 14, 2019
clrpackages pushed a commit to clearlinux-pkgs/pytest-runner that referenced this issue Feb 16, 2019
…ersion is detected. Ref #43.

Jason R. Coombs (5):
      Pin to old versions of pytest as workaround for man-group/pytest-plugins#110.
      Add workaround for man-group/pytest-plugins/issues/122
      Suppress E117 as workaround for PyCQA/pycodestyle#836
      Update changelog. Ref #43.
      Emit a warning when a future-unsupported setuptools version is detected. Ref #43.

4.4
===

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

4.3.1
=====
@eeaston
Copy link
Collaborator

eeaston commented Mar 20, 2019

Hi all, we just merged #134 to address this, thanks

jvesely added a commit to PrincetonUniversity/PsyNeuLink that referenced this issue Mar 21, 2019
@jvesely
Copy link

jvesely commented Mar 24, 2019

Hi all, we just merged #134 to address this, thanks

Hi, do you plan a release that includes this change in the near future?

jvesely added a commit to PrincetonUniversity/PsyNeuLink that referenced this issue May 9, 2019
clrpackages pushed a commit to clearlinux-pkgs/pytest-runner that referenced this issue May 24, 2019
…support setuptools older than 30.4. Fixes #49.

Jason R. Coombs (57):
      Bump minimum pytest version
      Add pyproject.toml declaring build dependencies.
      When ignoring linter warnings, document the reason.
      Disable the (broken) IPv6 in Travis. Ref travis-ci/travis-ci#8361.
      Don't match issues if preceeded by some other indicator.
      skip_upload_docs is default
      Drop the dot; http://blog.pytest.org/2016/whats-new-in-pytest-30/
      Rely on declarative config to create long_description.
      Remove workaround for pyyaml 126.
      Revert "Remove workaround for pyyaml 126."
      We're getting close, but Python 3.7 still requires a workaround
      Use xenial to include support for Python 3.7.
      Remove release, no longer needed. Use twine instead.
      Also ignore W504 in flake8, following the indication in OCA/maintainer-quality-tools that neither W503 nor W504 are worthwhile in general.
      Release of pyyaml 3.13 seems to have fixed install issues on Python 3.7.
      Block pytest 3.7.3 due to pytest-dev/pytest#3888.
      Move most package config to declarative config
      Ignore pycodestyle warning. Seems it's not going to be fixed anytime soon.
      Also ignore flake8 error
      Require setuptools 34.4 to support python_requires in declarative config.
      Add workaround for Teemu/pytest-sugar#159.
      Add black config, pre-commit including black, check code with black.
      Remove workaround for pytest-sugar 159, now fixed.
      Remove pytest-sugar plugin from standard pipelines as recommended in Teemu/pytest-sugar#159.
      Prefer pytest-checkdocs to collective.checkdocs
      Suppress deprecation warning in docutils
      Remove use of setup_requires. Builders now require pip 10 or later to build/install from sdist. Older installers will still install the packages from wheels. Ref tox-dev/tox#809.
      Revert "Remove use of setup_requires. Builders now require pip 10 or later to build/install from sdist. Older installers will still install the packages from wheels. Ref tox-dev/tox#809."
      Indicate build backend of setuptools
      Add support for cutting releases without DPL and using pep517.
      Rely on pep517 0.5
      Add documentation on the skeleton. Fixes #5.
      Add workaround for DeprecationWarning in flake8
      Use consistent encoding quoting in pyproject.toml
      Clarify purpose of local/upstream extras
      Suppress E117 as workaround for PyCQA/pycodestyle#836
      Amend skeleton documentation to expand on the value of the approach.
      Pin to old versions of pytest as workaround for man-group/pytest-plugins#110.
      Add workaround for man-group/pytest-plugins/issues/122
      Update changelog. Ref #42.
      pytest-runner has a single module, not a package. Fixes #44.
      Remove sudo declaration in Travis config.
      Enable tox-pip-extensions ext_venv_update if available. Fixes jaraco/skeleton#6
      Rely on tox 3.2 and pip 10 or later for all builds
      It adds no value to add a pip requirement for the tox install
      Pin to pip 19.0 for now for pypa/pip#6434.
      Revert "Pin to pip 19.0 for now for pypa/pip#6434."
      Only install and invoke pytest-black on Python 3
      Use pytest-black-multipy to enable simple support for pytest-black where available. Ref pytest-dev/pytest#5272.
      Update skeleton documentation to reflect black adoption.
      Fade to black
      Update changelog.
      Update changelog from master.
      Update changelog.
      Update changelog for 5.0
      Clarify changelog. Ref #49.
      Duplicately supply a minimal metadata in setup.py to support setuptools older than 30.4. Fixes #49.

Sebastian Kriems (1):
      spaces, style and formatters (#4)
@jcfr
Copy link
Contributor

jcfr commented May 28, 2019

@eeaston I think this issue can be closed.

@eeaston
Copy link
Collaborator

eeaston commented May 28, 2019

Released in 1.7.0 - many apologies all for the delay in releasing to pypi.

@eeaston eeaston closed this as completed May 28, 2019
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue May 28, 2019
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue May 28, 2019
The issue with pytest-plugins should be fixed now:
man-group/pytest-plugins#110

Signed-off-by: Jan Vesely <[email protected]>
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue May 28, 2019
The issue with pytest-plugins should be fixed now:
man-group/pytest-plugins#110

Signed-off-by: Jan Vesely <[email protected]>
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue May 28, 2019
The issue with pytest-plugins should be fixed now:
man-group/pytest-plugins#110

Signed-off-by: Jan Vesely <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants