Pylint, FTW

This weekend was a wash. With the Memorial Day weekend behind me, on Monday I jumped right back into my programming quest. It sux that I broke my commit streak, but that’s fine. It’s a personal challenge- not a bet. However, to the folks who are paying attention, I’ll be sure not to let you guys down.

Yesterday, I spent time going through a couple of the chapter exercises on Udemy. I’d been through them before, but I’d not coded up the examples by hand. Even though the material in the earlier sections of the Ultimate Python course aren’t new for me, I went back and coded them up by hand anyway. I also imported the exercises that I’d completed thus far in the ‘Learn Python the Hard Way’ tutorial series. I’ll probably spend some time going back through those examples as well, just to make sure that I’ve not missed something.

Enter Pylint. One thing that I’ve discovered as an operations guy is that I come across code of various dialects. Bash, Python, Java, Puppet, etc, etc. It’s hard sometimes for me to keep track of what’s legal syntax for a given programming language. That’s when I discovered the power of Pylint . It’s not earth shattering- it’s just a syntax checker that ensures you’re writing good PEP-8 compliant python code. What’s PEP-8? It’s the coding standard or style guide that you ‘should’ follow when writing Python. I’ve also noticed that a lot of python coders don’t follow it for whatever reason, but I figured that if I’m going to learn, I might as well learn the right way to do it right from the start.

Look for my Day 2 post shortly…

Jason T Clark

Jason T Clark

Father. Musician. Gamer. Coder.

comments powered by Disqus
rss facebook twitter github youtube mail spotify instagram linkedin