Hi
I've asked a few of the committers about this but thought I'd ping this to the list. We've integrated landscape.io to do automated code checks and as of right now it's flagging 8 Errors, 416 Smells and 784 Style alerts. I've had a look at some of these and thought I might pick off some of the lower hanging fruit in this area, but I'd just like to understand if improving the static code scores is seen to be of value right now... I'd like to see the scores improve, but like the testing and the changes to model.py, it's a big job which touches a significant number of lines of code. Of course, it's also fine if we choose to keep the codebase as-is but if that's the case we should adjust .landscape.yml to a profile that is tailored to alert on only the things we care about. (For example, I would be in favour of allowing _(\w+) in the pylint dummy variable syntax to allow context to be maintained for dummy variables)) cheers Paul
