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

PyFlakes bear dependency conflict in latest coala bears #1228

Closed
Mixih opened this issue Dec 30, 2016 · 2 comments
Closed

PyFlakes bear dependency conflict in latest coala bears #1228

Mixih opened this issue Dec 30, 2016 · 2 comments
Assignees

Comments

@Mixih
Copy link
Member

Mixih commented Dec 30, 2016

[ERROR][17:33:55] There is a conflict in the version of a dependency you have installed and the requirements of coala. This may be resolved by creating a separate virtual environment for coala or running pip install "pyflakes!=1.2.0,!=1.2.1,!=1.2.2,<1.4.0,>=0.8.1". Be aware that the latter solution might break other python packages that depend on the currently installed version.

@Mixih Mixih self-assigned this Dec 30, 2016
@Mixih Mixih changed the title PyFalkes bear dependency conflict in latest coala bears PyFlakes bear dependency conflict in latest coala bears Dec 30, 2016
jayvdb added a commit to jayvdb/coala-bears that referenced this issue Jan 2, 2017
radon 1.4.2 added a dependency on flake8-polyfill, which depends
on flake8 without any version specification, and flake8 versions
have various version dependencies on pyflakes and pycodestyle.
As a result, it is not possible to know what versions of pyflakes
and pycodestyle that will be required to be compatible with
whatever flake8 version happens to be installed.

Fixes coala#1228
jayvdb added a commit to jayvdb/coala-bears that referenced this issue Jan 2, 2017
radon 1.4.2 added a dependency on flake8-polyfill, which depends
on flake8 without any version specification, and flake8 versions
have various version dependencies on pyflakes and pycodestyle.
As a result, it is not possible to know what versions of pyflakes
and pycodestyle that will be required to be compatible with
whatever flake8 version happens to be installed.

Fixes coala#1228
jayvdb added a commit to jayvdb/coala-bears that referenced this issue Jan 2, 2017
radon 1.4.2 added a dependency on flake8-polyfill, which depends
on flake8 without any version specification, and flake8 versions
have various version dependencies on pyflakes and pycodestyle.
As a result, it is not possible to know what versions of pyflakes
and pycodestyle that will be required to be compatible with
whatever flake8 version happens to be installed.

Fixes coala#1228
jayvdb added a commit to jayvdb/coala-bears that referenced this issue Jan 2, 2017
radon 1.4.2 added a dependency on flake8-polyfill, which depends
on flake8 without any version specification, and flake8 versions
have various version dependencies on pyflakes and pycodestyle.
As a result, it is not possible to know what versions of pyflakes
and pycodestyle that will be required to be compatible with
whatever flake8 version happens to be installed.

Fixes coala#1228
@jayvdb
Copy link
Member

jayvdb commented Jan 3, 2017

Copying #1245 (comment) here:

The uncontrollable part of the pyflakes problem was between autoflake(pyflakes) and radon(flake8).
autoflake pinned their pyflakes to 1.3, and we followed suite, which only temporarily solved our problem. The real problem was radon, which depended on flake8 without any version spec, and different versions of flake8 have different pinned versions of pyflakes.

@jayvdb
Copy link
Member

jayvdb commented Jan 5, 2017

Note that using pyflakes 1.4 is quite important, specifically for an AST change in Python 3.6 ( PyCQA/pyflakes#80 )

gosom pushed a commit to gosom/coala-bears that referenced this issue Jul 15, 2017
If we don't specify the minor verison, `~=` matches any point update,
including major ones.

Fixes coala#1228
gosom pushed a commit to gosom/coala-bears that referenced this issue Jul 15, 2017
radon 1.4.2 added a dependency on flake8-polyfill, which depends
on flake8 without any version specification, and flake8 versions
have various version dependencies on pyflakes and pycodestyle.
As a result, it is not possible to know what versions of pyflakes
and pycodestyle that will be required to be compatible with
whatever flake8 version happens to be installed.

Fixes coala#1228
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants