Work with your assigned partner(s).
Use only the Python expressions, statements and commands we have been using in class at the time of the official announcement of this assignment. (That now includes Python’s built-in slicing and most of its standard string methods. If you are not sure whether you can use a particular command or construct, be sure to check with your instructor first.)
When ready to submit your work, one (and only one) member of your
team should upload one zip file of a folder called
hw5 that contains all required files via MySLC
The required files are:
.py file that you have created from
scratchreadme.txt file (see below)If your project requires additional files (notably
simple_graphics) then you should include that file in the
zipped folder that you submit.
The readme.txt file should clearly (but concisely!)
describe your project. It should be well written and proofread. When
using the first person it should always use the plural (“we”; not “I”).
It should explain any discrepancies between your goals and what you were
able to accomplish.
All the files that you write should have all your names in the file, at the top of the file.
Whoever uploads the assignment should then email me (reply to the email officially announcing the assignment) and CC your partners indicating that the assignment has been submitted.
Test your work as you go!
Be creative!
Experience the challenge of and synergy afforded of collaborative coding outside the confines of the laboratory
Gain further experience working with top-down design and writing Read Evaluate Print Loops (REPLs)
Have fun!
Your readme document should make it clear how to run
your program.
Your program must be a REPL; it may make use of other REPLs within its execution (as we did in lab5).
Your program should consist of at least 6 distinct functions that you have written yourselves.
Every function you write should include a brief comment as to its purpose.
You should make use of at least:
while loopsinputprint using f-stringsWhere possible, separate functions that are pure (that
take explicit arguments and return values) from those that are
side-effecting and rely on input and output (whether
print or simple_graphics).
To the extent that you can keep each function short (aim for
fewer than 10 lines of code; for example, in my solution to lab5), every function except
quizzer was fewer than 10 lines; quizzer was
about 20.
Where appropriate, you use None and
break.
You can use functions that we have written together in class or that have been provided as examples or solutions to past labs and homework; in that case be sure to use a comment at the top of those functions indicating that.
You cannot use code that you find anywhere else.
simple game that uses simple_graphics
high-low guessing game where the game alternate between having the computer think of a number and having the player try to guess it and vice versa (the computer tries to guess the number the player is thinking of)
simple word guessing game like Wordle or hangman
fancy calculator