Python and Python Scripting


This post is being created as an example of an area of concern while I am teaching myself… Am I learning the right stuff?

I am beginning to look for a new position, and some employers are looking for “Python Scripting”. It was not a phrase I was familiar with and looked it up, but apparently I’ve already been doing it.

“Python Scripting” is not something that is not clearly defined online. The best description I have been able to find is at RealPython.com, as it is describing Scripts vs Modules. It’s a short explanation, so please give it a quick read. Based on this description and my coding experience, for my additional clarification I am adding scripts can run independently, but may rely on modules…

Taking the above into account, I see 2 types of scripting. The first type is the kind I have been doing primarily in tutorials and small programs. A very simple example is getting the current date,

import time
time.ctime()

This code can “run on its own” to deliver an output, as opposed to a module (in this case, “time”), which does not deliver anything when run itself (which happens at import). But this script is dependent on the time module to work.

Recently, I viewed Python Scripting for Beginners, and it introduced what I am calling the second type of scripting, automating tasks. At approximately min 32, scripting for AWS is introduced. This example, with the proper modules installed and configuration, you can set up and tear down instances from within the script/program. Stringing together a series of these types of commands can create a whole other environment from a few lines of (scripted) code.