PEP 8

>>60955327
>tfw used to using the following function naming convention: thisIsAFunction()
>but PIP 8 autism enforcer on my IDE highlights it as an error

Should I change my function title naming just to satisfy Pip 8?

>>60956034
Yes you should.
Naming convention and code guidelines can vary between project.
I suggest you to be not fanatic to any of them and be fluid on your work.

>>60956034
You can disable the warnings on PyCharm, but camel case in python looks pretty reatarded.

>>60956064
This. It's pretty evident what you should be using if you're working with standard library functions.

My biggest annoyance with PEP-8 is actually the 80 character line limit. I know the philosophy is to write short lines and it's fine in most cases but it can all go out the window when using and/or logic or using list comprehensions, force you to obscure the names of your variables or break an expression over two lines.

>>60956034
Yes, using snake case is an actual standard among a huge part of python devs, not just pep8.
Wrappers around C/C++ libraries are usually exempt as those use their language's equivalent (like opencv)

>>60955327

PEP 8 is a good base, but you need to apply common sense. If you are in deep indentation either split into functions if possible, or just go over the limit.

>>60955327
>>60956139
>Thinking about code formatting in 2017
Just get YAPF or some similar tool and you won't have to think about where to put newlines ever again.