Learning Pyret
1 Setup
2 Assignment
3 Handin Instructions

Learning Pyret

1 Setup

As a way to learn the basics of Pyret, we are asking you to implement and test certain functions. We strongly suggest that before you begin you start reading the course text and look at the language tour, using the documentation for Pyret as needed. You will be writing your code online. We are not supporting any other usage modes.

To begin, please go to code.pyret.org and follow the instructions to connect your Brown Google drive.

Once connected, visit this link.

Save a copy to your Google Drive with an appropriate title.

2 Assignment

We are asking you to implement and test the functions outlined in the file. Fill in the code and test blocks with your own implementations and test cases. As you fill out test cases, click the “Run” button to compile and execute your code. Pyret will report on the functionality of your code and tests. When you are done with this assignment, all of your test cases should pass.

3 Handin Instructions

You can hand in your code by sharing a copy of your work on code.pyret.org, and then submitting the link to your shared copy using the handin script. With your code open, click the share button at the top of the page, and click on “Share a New Copy” to generate a snapshot of your code at the current moment. Choose the shared copy you would like to submit and copy the url of the shared copy. In your terminal, run the command:

cs019-cpo-handin learning-pyret <shared copy url>

This first assignment will not be assigned a numerical grade. Instead, after submitting your work via the handin script, you will need to get checked off by a TA to receive credit for your work. This weekend, your TAs will be holding additional office hours—check your email for details as to when and where these extra hours will be held. To get checked off for this assignment, go to one of these special “lab” hours and go through your code with one of the TAs. The TAs will be reading your code carefully to determine how exhaustive your test cases are, and how well your implementations work. Once the TA is satisfied with your code and test cases, you will be checked off.