We run pylint two ways:
* Interactively, in the same location as the .pylintrc file. We don't
explicitly pass it to pylint, and the normal routines for finding a
.pylintrc file work well here. There won't be an environment
variable set here (since it's just running within a user's shell
On Thu, Jun 2, 2016 at 11:09 PM, Tim Stumbaugh wrote:
> We run pylint two ways:
>
> Interactively, in the same location as the .pylintrc file. We don't
> explicitly pass it to pylint, and the normal routines for finding a
> .pylintrc file work well here. There won't be an environment variable set
On Thu, May 26, 2016 at 8:57 PM, Tim Stumbaugh wrote:
> Hello,
>
> We are in the early phases of rolling out pylint to our Python application.
> We have a particularly strange setup where we use __path__ in a number of
> "virtual packages" in order to set the correct location of the real package.
Hello,
We are in the early phases of rolling out pylint to our Python
application. We have a particularly strange setup where we use __path__
in a number of "virtual packages" in order to set the correct location
of the real package. Activating astroid's behavior which scans sys.path
(the fro
