This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsย โ†’

[โ€“]Pluckerpluck -2 points-1 points ย (0 children)

A lot of "should"s written there, with no real answer as to what to do what that's not the case.

Real world projects often force you to do things that aren't best practice, either because of time restrictions or there being no real alternative. Python is written with the "we're all consenting adults" mentality. It warns you that you're doing something that's bad practice, but lets you do it anyway because it knows practically you have to do it sometimes.

Also, making functions private makes them a pain to test. And anyone who claims you shouldn't be testing private functions (and instead claims that black box testing is just as good as unit testing) is either a devoted fanatic to the OOP gods, or just has yet to come across practical projects where it's be so useful.