Jun-06-2017, 04:09 PM
(Jun-06-2017, 03:53 PM)micseydel Wrote: Rather than adding that comment, why not do the typicalI got the impression that this is recommended form for files without interpreter line - see PEP-263. And, I've already implied
# -*- coding: <encoding name> -*-?
- This line looks too artificial to be user comments (well, my level of English is much higher than that of my colleagues)
- This was the only change made to the file in the commit
- and this line was there for a long time
(Jun-06-2017, 03:53 PM)micseydel Wrote: Also, annotations are more than just cosmetic. They allow static analysis tools to notify you of mistakes in a way similar to a statically typed language. In theory....
I can tell you a joke about the difference between
in theory
and in practice
- but I will be banned for foul language 
Making changes to files after running tests is bad practice altogether - in my humble. Breaking builds

Test everything in a Python shell (iPython, Azure Notebook, etc.)
- Someone gave you an advice you liked? Test it - maybe the advice was actually bad.
- Someone gave you an advice you think is bad? Test it before arguing - maybe it was good.
- You posted a claim that something you did not test works? Be prepared to eat your hat.