I am with you on that. I hate Python, and I always wonder why there isn´t any other popular language that has the idiotic policy of considering spaces part of the language syntax... there might be a reason for that.

It's barely a hurdle, if you can't manage to configure your setup to meet your teams setup then it probably means you are not qualified.

Thank you for your charitable interpretation of my qualifications.

But, you know, stuff happens. Somebody's machine loses the hard drive; in the process of building the new hard drive, they miss restoring the configuration for their editor. Somebody else installs a new editor, and forgets that configuration matters. A new employee gets hired, and doesn't know either how or why to configure properly. And behold, bugs get introduced invisibly.

That won't happen often. It will happen more than zero, though. And when it does, it's a headache I don't need.

Sorry, I don't mean to even suppose about your qualifications. Most scans will detect mixed tabs/spaces and they don't even make it into the repo. And if it is a continual problem with a particular team member then that has been in my experience a sign that this person doesn't know what the hell they are doing. Again I make no suppositions about your particular qualifications, I apologize.

No big deal. It just rubbed me the wrong way - perhaps more than it should have.

But yes, if you have a team member that repeatedly does this, then there's clearly a problem. If you run a scan that won't let people do this, that's clearly a solution.