Code with Style - PyOhio

Code With StyleClayton ParkerPyOhio 2010nowhere to go butopen sourcesixfeetup.com/deploy2010Who am I?• claytron on IRC• Python dev since 2003sixfeetup.com/deploy2010What wil we learn?• Zen• PEP8• Toolssixfeetup.com/deploy2010Don’t dissapointhttp://www.flickr.com/photos/docsearls/199700939/sixfeetup.com/deploy2010The Zen of Python>>> import thisThe Zen of Python, by Tim PetersBeautiful is better than ugly.Explicit is better than implicit.Simple is better than complex.Complex is better than complicated.Flat is better than nested.Sparse is better than dense.Readability counts.Special cases aren't special enough to break the rules.Although practicality beats purity.Errors should never pass silently.Unless explicitly silenced.In the face of ambiguity, refuse the temptation to guess.There should be one-- and preferably only one --obvious way to do it.Although that way may not be obvious at first unless you're Dutch.Now is better than never.Although never is often better than *right* now.If the implementation is hard to explain, it's a bad idea.If the implementation is easy to explain, it may be a good idea.Namespaces are one honking great idea -- let's do more of those!sixfeetup.com/deploy2010Important Zen• Beautiful is better than ugly.• Readability counts.• Now is better than never.• Although never is often better than right now.sixfeetup.com/deploy2010What is PEP8?• A style guide for Python• Common sensesixfeetup.com/deploy2010The importance of PEP8• Code is read more than it is written• Consistencysixfeetup.com/deploy2010When to break the rules• Less readable• Be aware of your surroundingssixfeetup.com/deploy2010Code layout• 4 space indents• Never mix tabs and spaces!• Maximum line length 79 characters• Use blank lines sparinglysixfeetup.com/deploy2010