* Dan Stromberg [2016-01-20 07:08:14 -0800]:
> I like this too, though I find that sometimes there's no disable= for a
> message.
Do you have an example of this? Every message should have a name and
you should be able to disable it using that name. I've never seen a
message where this wasn't the
Hey,
* Philip Jay [2016-01-20 23:25:42 +1100]:
> Instead of accepting a threshold like 8/10 or whatever...
> Set your continuous integration pipeline to fail a build if you don't get
> 10/10.(yes! you read it correctly!)
It's already pylint's default behaviour to exit nonzero if there are
an
I like this too, though I find that sometimes there's no disable= for a
message.
For that reason, I wrote a pylint wrapper that knows how to ignore some
messages. I prefer to use disable= where possible though.
EG:
./this-pylint \
--ignore-message "^.*Unable to import 'hashlib'" \
Hi all,
Last year I was taught a really good method of using pylint.
Instead of accepting a threshold like 8/10 or whatever...
Set your continuous integration pipeline to fail a build if you don't get
10/10.(yes! you read it correctly!)
Then, where you need to deviate from 'perfect style' -
thank you, it's always nice to get such cheerful feedback. And congrat ! :)
On 16 janvier 13:58, David Aguilar wrote:
> I just got git-cola[1] to 100%
>
> Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)
> Wow ! Now this deserves our uttermost respect.
> Please sen
