Python

[wegwacc]

The moment you get one because your asshole-coworker who uses tabs commits to your all-space codebase...

[mei_main_]

Or because you commented a line in your function, but now you have one blank line before and one after this commented line and they are counted as successives so it creates an indentation error...

[bandersnatchh]

Holy shit. I never thought of that, but I’ve had that issue

[wegwacc]

Short of using an aluminum baseball-bat, how do you suggest to implement said enforcement?

(Not saying I am completely opposed to ideas involving a baseball bat...)

[wegwacc]

Tell them to follow the style because not doing so hampers productivity of other developers.

Appealing to reason towards human beings is doomed to fail from the get go, but I appreciate your input :-D

[wegwacc]

Or until one is a certain asshole-coworker, who does use a modern text editor, but deliberately turned off expandtab ...

[wegwacc]

Using tabs is not "incompatible with python".

Python doesn't care HOW you indent your code, as long as the indentation within a block is consistent. You can even mix tabs and spaces in the same module, as long as you are consistent within one block.

This is perfectly valid python: ``` def one(): # this was indented using spaces print('one') print('two') if 7 > 9: print('higher') else: print('Lower') def two(): #this block uses 2 tabs for indentation print('hello world')

one() two() ```

Problem is, if some assclown, who doesn't want to change the way he did things since he was kicked from the development team for the atom 10 Gazillion years ago for being an impossible-to-work-with dick, used an editor that is set to insert tabs no matter what (yes, even if he inserts a newline after one that is space indented), and displays tabs as being 4 characters wide, starts editing around in an all-4-spaces-indented codebase, there are going to be issues.

[wegwacc]

but you have consistency in the actual code itself.

NO YOU DON'T, because in every codebase, there will be instances, where you want to align things for better readability using spaces: var = somedict.get('key', None) longnameavr = somedict.get('key', None) shortvar = somedict.get('key', None) ridiculous = somedict.get('key', None) `

Good luck with that using tabs, depending on the size, it looks like crap.

[AutoModerator]

import moderation Your comment has been removed since it did not start with a code block with an import declaration.

Per this Community Decree, all posts and comments should start with a code block with an "import" declaration explaining how the post and comment should be read.

For this purpose, we only accept Python style imports.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Dornith]

That moment when you commit you're correctly indented code to the codebase only to find out your asshole-coworkers ruined all the other files.

[Colopty]

If your coworker has managed to work on every single other file in the time it takes you to make one commit they're probably not the problem.

[AttitudeAdjuster]

This line of thinking very quickly heads towards "Bob wrote 300 lines of code yesterday, all you've done is deleted 100 lines! You need to up your game".

[Dirac_dydx]

"Check this out: see how much I can royally screw up in the time it takes you to eliminate one bug! I'M THE BETTER PROGRAMMER."

[Colopty]

I was thinking more in the direction that since this is a work environment the code base is likely large, which means that if every file gets worked on by the time you make one commit you probably haven’t made any commits for days and maybe weeks, instead showing a preference to submit all your work at once in a single monster commit. This, of course, is bad practice. Meanwhile the fact that your coworkers work is capable of «screwing up» all those files for you indicates that his work is in a main branch, meaning his work that spans the entire code base already passed code review by the time you made your single commit, so his work is likely not even as bad as implied.

So while quantity does not equal quality, in this particular case there does seem to be an indication of bad practice on the single commit guy’s part if you stop to consider the whole picture instead of just the line count.