Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

```$ ./pants pylint src/python/fsluigi/filesystem::
ERROR] Invalid scope [pylint] in pants-internal.ini```

```$ ./pants pylint --help

pylint options:

--pylint-disable=&lt;str&gt; (--pylint-disable=&lt;str&gt;) ..., --pylint-disable="[&lt;str&gt;, &lt;str&gt;, ...]", --pylint-disable="+[&lt;str&gt;, &lt;str&gt;, ...]" (default: [])
    The disabled warnings and errors.
--pylint-pylintrc="{'key1':val1,'key2':val2,...}" (default: None)
    A dictionary that will be transformed into a pylintrc.```

<@U053HNE90>: try `./pants options | grep pylint`

(i have no idea what the answer to your question is)

`./pants options` is apparently broken in our repo

```Exception message: Invalid registration kwarg action. [option --target-types in scope filter-targets].```

```pylint.disable = ['too-many-lines', 'multiple-statements', 'line-too-long', 'super-on-old-class', 'attribute-defined-outside-init', 'unused-argument', 'no-init', 'too-few-public-methods', 'too-many-arguments', 'wrong-spelling-in-docstring', 'too-many-locals', 'too-many-public-methods'] (from CONFIG)
pylint.pylintrc = {u'REPORTS': {u'files-output': u'no'}, u'FORMAT': {u'indent-string': u"'  '", u'max-line-length': u'120'}} (from CONFIG in pants-internal.ini)```

This was triggered by a _completely unrelated_ and unmentioned task

```except TypeError:
  # Let's assume this wasn't a problem!
  ...```

fyi: the docs for "the new engine" are now a bit more specific to what we hope to move out of the `exp` package in the next few months: <https://github.com/pantsbuild/pants/blob/master/src/python/pants/engine/exp/README.md>

everyone, please welcome <@U0XUTHRPZ> who joined Twitter recently, and will be working from NYC

I think I am gonna greet you with a question that has bothered me for a while...

it is about unittest. I have a BaseClass, which has a setUp() method and a few test_… function. and I have a DerivedClass(unittest.TestCase, BaseClass). When I run the tests, it seems setUp() in BaseClass is skipped (I have set a pdb breakpoint in setUp and it didn’t break) and execution goes directly to test_…. Does anyone know why this happens?

(i tried to answer this one and failed... my understanding of multiple inheritance was that this should work fine.)

did you call `super(BaseClass, self).setUp()`?

does unittest.TestCase itself have a setUp method?

if so, super will go to unittest.TestCase’s setUp