-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Enforce pylint violation when using old event tracker. #6080
Conversation
Idea is this will raise our pylint violations slightly today but if anyone decides to re-use the library, diff-quality will fail. it doesn't appear to catch all cases at this point, though, because of pylint failures to import. i'll see how the jenkins builds handle it. CC @mulby |
@sarina in order to prevent folks from using a deprecated event-tracking module, I'm introducing this rule change. My end goal is to prevent additional drift or re-use of this module. Thoughts? FYI this adds 8 pylint violations. |
@benpatterson I think that definitely makes sense. Where are the 8 pylint violations coming from? I think it's not going to be possible for us to ever have 0 pylint violations. I think a reasonable number is somewhere around 500. so on that front I'm ok. but if it's possible to explicitly ignore some of the introduced violations (because we know we're ok with them) maybe we could do that here. |
@sarina I think we should not comment these out though. The library is deprecated, so the violations are technically valid. |
OK, makes sense. Is there a backlog ticket to migrate these files away from using a deprecated library? Why are they using deprecated libraries? |
OK, makes sense. Would be good, but not strictly necessary, to capture that somewhere - but I agree, best to have the pylint warnings so if someone goes in to those files to clean up perhaps they'll fix. 👍 |
Found the ticket |
Solid. Thanks guys. |
Enforce pylint violation when using old event tracker.
This is a deprecated use and we need to be sure others don't adopt it.