
Hey all, I was working with Joe Gordon (who's subscribed to this list) and we realized there's a very real desire for the ability to register a check but not have it turned on by default. Thanks to some free time today, I've been able to throw together an example of what that would look like in flake8: https://gitlab.com/pycqa/flake8/merge_requests/14 I'm mainly looking for community and user based feedback. Are there objections to a feature like this? Are there pitfalls? The approach is a bit hack-ish, granted, but I doubt this is something pep8 has any need to absorb. Cheers, Ian

On Thu, Dec 18, 2014 at 1:15 PM, Ian Cordasco <graffatcolmingov@gmail.com> wrote:
Hey all,
I was working with Joe Gordon (who's subscribed to this list) and we realized there's a very real desire for the ability to register a check but not have it turned on by default. Thanks to some free time today, I've been able to throw together an example of what that would look like in flake8: https://gitlab.com/pycqa/flake8/merge_requests/14
I just tried this patch out on hacking, OpenStacks style guide flake8 plugin and it works well: http://paste.openstack.org/show/154033
I'm mainly looking for community and user based feedback. Are there objections to a feature like this? Are there pitfalls? The approach is a bit hack-ish, granted, but I doubt this is something pep8 has any need to absorb.
I like this feature, because it is an easy way to allow repos to opt-in to new rules without feeling like they are forced to use them. We currently work around this issue by having local rules in each repo but this has resulted in a lot of duplicate code.
Cheers, Ian _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
participants (2)
-
Ian Cordasco
-
Joe Gordon