Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-enable pylint in info-only mode for all packages #3519

Merged
merged 2 commits into from
Jun 23, 2017

Conversation

theacodes
Copy link
Contributor

No description provided.

@theacodes theacodes requested a review from dhermes June 22, 2017 20:47
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jun 22, 2017
@dhermes
Copy link
Contributor

dhermes commented Jun 22, 2017

A cursory scan looks fine, though ISTM we should have a single pylint.config.py at the project root and then every package points at that?

@theacodes
Copy link
Contributor Author

I'd do that but @lukesneeringer is planning on splitting packages into their own repos.

@dhermes
Copy link
Contributor

dhermes commented Jun 22, 2017

Yeah in that context it totally makes sense.

@tseaver
Copy link
Contributor

tseaver commented Jun 23, 2017

@jonparrott I'm missing what makes running pylint this way "advisory only": can you elaborate?

@theacodes
Copy link
Contributor Author

@tseaver nox is ignoring its return value, so pylint can fail but the lint session will still pass.

@theacodes
Copy link
Contributor Author

@dhermes @lukesneeringer y'all got any more of them LGTMs?

@dhermes
Copy link
Contributor

dhermes commented Jun 23, 2017

LGTM

landrito pushed a commit to landrito/google-cloud-python that referenced this pull request Aug 22, 2017
landrito pushed a commit to landrito/google-cloud-python that referenced this pull request Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants