orSolocate
orSolocate
@vinsdragonis sounds like a nice idea. And if you follow the same way of thinking maybe you could add a `number of followers` badge.
@DanielNoord I agree that this is a chicken-egg case, I think variable assignments like this should be ignored by the checker like you guys suggest. Maybe it should just take...
I will work on it you can assign me and I will open a PR when implemented
@DanielNoord - I extended `comparison-of-constants` to add this feature. I tried to keep functionality of `comparison-of-constants` as it was. But maybe we want to disallow singletons there too like I...
Edit: actually I don't think casting should be the suggestion here. It would still be `False` after casting...
I can implement it if there is value in that for Pylint. @Pierre-Sassoulas or anyone else like the idea?
could you explain why you think there will be false positives with an example? The implementation can be restricted only to `if` visits. it can be reduced to work only...
@DanielNoord well the value of catching such error is great because if you detect it inside an `if` comparison you detect unreachable code. I also have some doubt about (1)...
I will try to check it when I have the time (keep this issue opened)
@DanielNoord just to make sure I understand your suggestion: You suggest to add a new optional entry called `files` or `files_default` in `setup.cfg` under `[options]` and set the `.` there?...