Re: [PATCH v7 17/31] python: add pylint to pipenv

2021-05-27 Thread Cleber Rosa
On Tue, May 25, 2021 at 08:24:40PM -0400, John Snow wrote: > We are specifying >= pylint 2.8.x for several reasons: > > 1. For setup.cfg support, added in pylint 2.5.x > 2. To specify a version that has incompatibly dropped >bad-whitespace checks (2.6.x) > 3. 2.7.x fixes "unsubscriptable" warn

Re: [PATCH v7 17/31] python: add pylint to pipenv

2021-05-26 Thread John Snow
On 5/26/21 5:14 AM, Vladimir Sementsov-Ogievskiy wrote: 26.05.2021 03:24, John Snow wrote: We are specifying >= pylint 2.8.x for several reasons: 1. For setup.cfg support, added in pylint 2.5.x 2. To specify a version that has incompatibly dropped     bad-whitespace checks (2.6.x) 3. 2.7.x fixe

Re: [PATCH v7 17/31] python: add pylint to pipenv

2021-05-26 Thread Vladimir Sementsov-Ogievskiy
26.05.2021 03:24, John Snow wrote: We are specifying >= pylint 2.8.x for several reasons: 1. For setup.cfg support, added in pylint 2.5.x 2. To specify a version that has incompatibly dropped bad-whitespace checks (2.6.x) 3. 2.7.x fixes "unsubscriptable" warnings in Python 3.9 4. 2.8.x adds

[PATCH v7 17/31] python: add pylint to pipenv

2021-05-25 Thread John Snow
We are specifying >= pylint 2.8.x for several reasons: 1. For setup.cfg support, added in pylint 2.5.x 2. To specify a version that has incompatibly dropped bad-whitespace checks (2.6.x) 3. 2.7.x fixes "unsubscriptable" warnings in Python 3.9 4. 2.8.x adds a new, incompatible 'consider-using-wi