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

Impose upper bound on pylint version #103

Merged
merged 1 commit into from Apr 27, 2020
Merged

Impose upper bound on pylint version #103

merged 1 commit into from Apr 27, 2020

Conversation

bmorcos
Copy link
Contributor

@bmorcos bmorcos commented Apr 27, 2020

Motivation and context:

The new release of pylint (2.5) needs to have the package installed,
whether intentional or not, this has been failing our FPGA repos.

How long should this take to review?

  • Quick (less than 40 lines changed or changes are straightforward)

Types of changes:

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have read the CONTRIBUTING.rst document.
  • N/A I have updated the documentation accordingly.
  • I have included a changelog entry.
  • N/A I have added tests to cover my changes.
  • I have run the test suite locally and all tests passed.

Copy link
Member

@drasmuss drasmuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Added a minor fixup to the wording in the changelog. It's generally most useful to describe the effect of the change (restricting the pylint version) and the motivation (what was failing), rather than just the mechanical change (adding an upper bound). And then modified the commit message to describe the change (same reasoning) and to avoid referring to FPGAs in particular (since this isn't specific to the FPGA repos).

Pylint 2.5 errors if the package being checked is not
installed. It is not clear whether this is an intentional
change or not, so we are temporarily avoiding this
version.
@drasmuss
Copy link
Member

Oh one other thing, could you open an issue with pylint as well so that we have something to follow to see if there is any upstream resolution to this?

@bmorcos
Copy link
Contributor Author

bmorcos commented Apr 27, 2020

Looks like pylint-dev/pylint#3524 covers this.

@drasmuss drasmuss merged commit a398b33 into master Apr 27, 2020
@drasmuss drasmuss deleted the pylint branch April 27, 2020 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants