Get Started with Python
Encourage learners to run small Scratch commands to remind them of the result, alternatively, have video clips of Marty carrying out Scratch commands. Have step-by-step instructions printed out for starting and using the IDLE interface.
Challenge groups to combine their work or find a way to write code that seems as if their Marty's interact with each other. Challenge learners to create pseudocode to represent possible Python code to explore in future lessons.
18 of 18 linked standards shown.
| Curriculum area | Linked standards |
|---|---|
| Digital Technologies, Design & technologies: Digital Technologies |
Select a code to read the full standard.
| Curriculum area | Linked standards |
|---|---|
| General standards |
Select a code to read the full standard.
| Curriculum area | Linked standards |
|---|---|
| Health and Wellbeing: Mental, Emotional, Social and Physical Wellbeing | |
| Literacy & English: Listening and Talking | |
| Literacy & English: Reading | |
| Literacy & English: Writing | |
| Technologies: Computing Science |
Select a code to read the full standard.
| Curriculum area | Linked standards |
|---|---|
| Computing, Design and Technology: Computing |
Select a code to read the full standard.
| Curriculum area | Linked standards |
|---|---|
| International Society for Technology in Education (ISTE) |
Select a code to read the full standard.
Students will begin interacting with the Python shell so that they can play around with running different commands to control Marty before creating code using a game-based activity for creating code in Python.
In this lesson, we will be focusing on using the IDLE program to access the Python shell before creating some small scripts. This needs to be installed in each device.
Scratch commands, for comparison with Python
-
Have a goal for Marty to accomplish and a sample program written in pseudocode, that is supposed to achieve the goal, for the learners to discuss. Have learners work as a team to create an efficient version of the program in scratch. Perhaps learners could include a loop, change a variable, add a conditional, etc.
Share with learners Python statements that could be used to achieve the goal of the pseudocode, without defining any of the statements. Have teams talk with other teams to share and compare: did different teams use the exact same code in exactly the same order? If it isn't exactly the same: does it still accomplish the goal; is one more efficient than another; is one easier to modify if the goal of the program changes?
After learners have decided that their code is good, have learners click the windows button or open their Mac terminal. In both instances, they should type 'idle'. Then, instruct them to code along as you type the command to connect Marty and model how to enter text into IDLE and run it.
Explain that IDLE has a 'shell' which is a window allowing a programmer to enter commands that are run in Python. When the window is closed, and you don't first save, all the work is lost: saving is crucial!
Have learners enter separate Python commands into IDLE and observe the results through Marty's actions.
Demonstrate or code along creating an IDLE script and running the file.
Have learners combine Python commands, in a file, and run the file. Challenge learners to try creating either similar code in different ways or more efficient code than what was created earlier.
Create the paper dice for the game-based way of practising the code on each of the faces. Have learners show you each time they pass a challenge.
Ask if there are any groups wanting to display anything that they think is interesting. Ask learners for the challenges they faced with Python. Ask them if the same challenges were faced with Scratch. Ask if they can think of any other reasons a person might use Python over Scratch, for work, a hobby, research, study, etc.
