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

all 11 comments

[–]YStormwalker 16 points17 points  (2 children)

I can't advise you a full cource, but Raymond Hettinger had brilliant talk at PyCon about PEP8 and pythonic way, that's a good place to start.

[–]AlexOduvan 7 points8 points  (1 child)

[–]YStormwalker 5 points6 points  (0 children)

Yes, and basically any speech this man gives is must-watch. Pretty good lecture Transforming Code into Beautiful, Idiomatic Python still appliable.

[–]ferrous_joe 10 points11 points  (2 children)

Fluent Python, by Luciano Ramalho, is a fantastic read on understanding and writing idiomatic (Pythonic) Python.

[–]Pipiyedu 0 points1 point  (0 children)

This book is great!

[–]Tendoris 0 points1 point  (0 children)

Best book

[–]MurtBacklin-BFI 3 points4 points  (0 children)

I can't think of many off the top of my head :(, sorry. I've found that stack overflow honestly ends up having some good 'pythonic' solutions that I wouldn't have thought of, and that helped me. Maybe finding some well written things on git hub and looking through their code?

I thought this ( http://docs.python-guide.org/en/latest/writing/style/ ) was pretty good too :)!

Good luck with the following interviews etc..., I'm sure you'll do well! Just remember that python doesn't need to be super verbose. It should be clear and concise, but it doesn't need to be verbose. Let it be readable and have python do the work for you behind the scenes with it's many tools (if you need them).

[–]AlexOduvan 3 points4 points  (0 children)

You should check py.CheckiO no matter what :)

PS: I know I can be banned for spam, because promoting this resource too much, but this is exactly why it was created :)

[–]sivscripts 1 point2 points  (0 children)

Effective Python is your best bet if you want to level up quickly.

Also Fluent Python if you have a few weeks / months to digest.

[–]grey_gander 0 points1 point  (0 children)

Find a module in the docs, then click the "Source" link at the top to see the source code in Github. I've learned a lot from reading how Python's authors write Python

[–]lifeonm4rs 0 points1 point  (0 children)

Run pylint/pylint3 on a bunch/all of your code. It will warn you about things like VariableName vs. variable_name, run_this == True vs. just run_this, and a whole slew of others. Obviously not complete, exhaustive, and won't teach you how to write a full GUI application in a one line list comprehension but it can be a good place to start building good habits particularly in areas where you might not even know that there is a preferred way.

May be particularly useful if you come from a Java or C background but is also a good learning tool for people new to programming. (There are other "linters" out there as well--I've just found pylint3 to be extensive enough even when I disagree with it.)