a pull request out of the blue, since the
actual change is trivial. Is there some better way to accomplish what I
am trying to do?
Thanks for your consideration,
tjs
--
Tim Stumbaugh
Operations
Hudson River Trading
___
code-quality mailing list
ile?
Of course, if you'd prefer not to support this workflow, I completely
understand, and our workaround is workable (even if it's a bit brittle).
tjs
On 2016-06-02 17:44, Claudiu Popa wrote:
On Thu, May 26, 2016 at 8:57 PM, Tim Stumbaugh wrote:
Hello,
We are in the early pha
ges in --errors-only that they haven't asked for.
Is there an opinion on what patch might be acceptable for the project?
Would it work to add an extra flag or put extra state in the PyLinter
object so that it knows which messages have been explicitly disabled?
Thanks,
tjs
--
Tim Stumbaugh
O
Jul 20, 2016 at 8:20 PM, Tim Stumbaugh
> wrote:
> > Hi,
> >
> > Since command line flags are processed after config file directives,
> error
> > messages that are disabled in a config file (or in a command line flag
> that
> > appears before --errors-o
I would assume would be out of
> scope, but aren't.
>
> I may move this loop into a separate function, and remove the need for
> the del statements.
>
> Comments?
> ___
> code-quality mailing list -- [email protected]
