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

[REF] requirements: upgrade pylint version #320

Merged
merged 2 commits into from
Jan 23, 2021

Conversation

fernandahf
Copy link
Contributor

Description of the issue/feature this PR addresses:

The following line of code:

is pinning the pylint version because it could raise red with newer versions but we need keep upgrading this version each period of time

There is a new release pylint-2.6.0 on Aug 21, 2020

Current behavior before PR:
pylint-odoo works correctly.

Desired behavior after PR is merged:
pylint-odoo works correctly with new pylint version.

Fix #319

-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

@fernandahf fernandahf force-pushed the master-upgrade-pylint-version-fer branch from 81d8251 to 2388d94 Compare January 20, 2021 18:02
@fernandahf
Copy link
Contributor Author

@moylop260

Could you review this, please?

Regards.

requirements.txt Outdated Show resolved Hide resolved
@fernandahf fernandahf force-pushed the master-upgrade-pylint-version-fer branch from 5e64921 to d42666c Compare January 22, 2021 23:28
isort>5 is only compatible with py36 and above, therefore we use a ISortDriver to support both versions and that it's not necessary to pin only one version.
@fernandahf fernandahf force-pushed the master-upgrade-pylint-version-fer branch from d42666c to dd470b3 Compare January 22, 2021 23:40
@moylop260 moylop260 merged commit c55f7f5 into OCA:master Jan 23, 2021
@moylop260 moylop260 deleted the master-upgrade-pylint-version-fer branch January 23, 2021 01:37
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.

Upgrade pylint==2.5.3 to pylint==2.6.0 for py>=3
2 participants