-
Notifications
You must be signed in to change notification settings - Fork 171
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
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
5ea0e95
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi
Pinning
astroid==2.2.5
produces an issue when installing latest stableprospector==1.1.7
using latest stable Pipenv (version 2018.11.26).There is a sub-dependency of Prospector requiring
astroid>=2.3.0
but I do not reach identifying it… 🤔I had to uninstall Prospector. 😿
5ea0e95
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reached to generate the
pipenv graph
.I have removed unnecessary lines to reduce noise:
prospector==1.1.7
requirespylint-celery==0.3
that does not pin a particular Pylint version and Pipenv installs the latest one (Pylint 2.4.2) that requiresastroid>=2.3.0
.If pin
pylint==2.3.1
it works:5ea0e95
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While we'll have to work on updating pylint soon as we expect pylint-dev/pylint#3016 to be merged, it's pretty odd that Pipenv is enforcing the latest pylint version as from the graph the highest version in there would be
pylint [required: ==2.3.1, installed: 2.3.1]
as prospector pins. I'll take a look a it to see if there's anything else to be done here as astroid pinning is necessary to avoid breaking builds on unexpected/untested dependencies updates.5ea0e95
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is weird from Pipenv 🙄
(maybe fixed, but no Pipenv release from a while…)
Of course, the issue is also obtained using Pip 🤗