It's time to learn a new language! Python!
Python is a popular, easy-to-use programming language that has significant traction in the field.
Remember the goal is learning to learn, so keep track of what works for you and what doesn't as you go through the process of exploring Python.
-
Try to relate things you already know in another language (e.g. what an array is) to the corresponding things in Python (e.g. a list) and how to use them.
-
Write a bunch of "toy programs" that demonstrate different key features of the language
-
Explore the standard library that's available for the language. Skim it briefly for now--the idea isn't to memorize everything but to file away generally what functionality is available.
-
Write a more substantial toy program that uses a variety of the features.
Again, keep track of what works for you. Try different things to see what works best for learning new languages.
- Installing Python and pipenv
- JavaScript<->Python cheatsheet
- How to read Specs and Code
- Python 3 standard library
-
Make sure you have Python 3 and pipenv installed.
-
Go to the directory with the
Pipfileand runpipenv install -
After the install completes, run
pipenv shellThis will get you into the virtual environment. At this point, you should be able to run Python 3 by just running
python:$ python --version Python 3.6.5You can exit the virtual environment by typing
exit.
Learn the basics of Python with a pile of toy programs.
Take a look in the src/ directory.
NOTE: adv/ is for Day 2, so ignore it for today.
Suggested order for implementing the toy programs:
hello-- Hello worldbignum-- Print some big numbersdatatypes-- Experiment with type conversionmodules-- Learn to import from modulesprintf-- Formatted print outputlists-- Python's version of arraysslice-- Accessing parts of listscomp-- List comprehensionsdicts-- Dictionariesfunc-- Functionsfileio-- Read and write from filescal-- Experiment with module importsobj-- Classes and objects
Put it together into a bigger toy program: a simple text adventure!
This is in src/adv/. Check it out!
-
Put the Room class in room.py based on what you see in
adv.py. -
Put the Player class in
player.py. -
Follow the instructions
adv.py. -
Figure out what all those
.pycfiles are that appear after you successfully run the program.
-
Add an
Itemclass in a fileitem.py.-
This will be the base class for specialized item types to be declared later.
-
The item should have
nameanddescriptionattributes.- Hint: the name should be one word for ease in parsing later.
-
-
Add capability to add items to rooms.
-
The
Roomclass should be extended with alistthat holds theItems that are currently in that room. -
Add functionality to the main loop that prints out all the items that are visible to the player when they are in that room.
-
-
Add capability to add
Items to the player's inventory. The inventory can also be alistof items "in" the player, similar to howItems can be in aRoom. -
Add a new type of sentence the parser can understand: two words.
-
Until now, the parser could just understand one sentence form:
verbsuch as "n" or "q".
-
But now we want to add the form:
verbobjectsuch as "take coins" or "drop sword".
-
Split the entered command and see if it has 1 or 2 words in it to determine if it's the first or second form.
-
-
Implement support for the verb
getfollowed by anItemname. This will be used to pick upItems.-
If the user enters
getortakefollowed by anItemname, look at the contents of the currentRoomto see if the item is there.-
If it is there, remove it from the
Roomcontents, and add it to thePlayercontents. -
If it's not there, print an error message telling the user so.
-
-
-
Implement support for the verb
dropfollowed by anItemname. This is the opposite ofget/take. -
Add the
iandinventorycommands that both show a list of items currently carried by the player.
-
Add a
scoreto yourPlayerclass. Set it to 0. -
Add a single word command,
score, that the user can type in to see their current score. -
Add a subclass to
ItemcalledTreasure.- The
Treasureconstructor should accept a name, description, and value.
- The
-
During world creation, add three
Treasures to convenientRooms. -
Add an
on_takemethod toItem.-
Call this method when the
Itemis picked up by the player. -
The
Itemcan use this to run additional code when it is picked up.
-
-
Override
on_takeinTreasureso that the player gets the value of theTreasureadded to theirscoreattribute but only the first time the treasure is picked up.- If the treasure is dropped and picked up again later, the player should not have the value added to their score again.
-
Add an
on_dropmethod toItem. Implement it similar toon_take. -
Add a subclass to
ItemcalledLightSource. -
During world creation, add a
lampLightSourceto a convenientRoom. -
Override
on_dropinLightSourcethat tells the player "It's not wise to drop your source of light!" if the player drops it. (But still lets them drop it.) -
Add an attribute to
Roomcalledis_lightthat isTrueif theRoomis naturally illuminated, orFalseif aLightSourceis required to see what is in the room. -
Modify the main loop to test if there is light in the
Room(i.e. ifis_lightisTrueor there is aLightSourceitem in theRoom's contents or if there is aLightSourceitem in thePlayer's contents).-
If there is light in the room, display name, description, and contents as normal.
-
If there isn't, print out "It's pitch black!" instead.
-
Hint:
isinstancemight help you figure out if there's aLightSourceamong all the nearbyItems.
-
-
Modify the
get/takecode to print "Good luck finding that in the dark!" if the user tries to pick up anItemin the dark.
-
Add more rooms.
-
Add more items to the game.
-
Add a way to win.
-
Modify the code that calls
on_taketo check the return value. Ifon_takereturnsFalse, then don't continue picking up the object. (I.e. prevent the user from picking it up.)- This enables you to add logic to
on_taketo code things like "don't allow the user to pick up the dirt unless they're holding the shovel.
- This enables you to add logic to
-
Add monsters.
-
Add the
attackverb that allows you to specify a monster to attack. -
Add an
on_attackmethod to the monster class. -
Similar to the
on_takereturn value modification, above, haveon_attackprevent the attack from succeeding unless the user possesses asworditem. -
Come up with more stretch goals! Scoring? Monsters?