![[Picture of the textbook]](python2.gif)
Your grade will be determined by how well you do on the homework (60%) and your final project (40%). Remember that you have to follow the exact interface when output is asked for. Ill formatted output is untestable and will be graded accordingly.
apt-get install python-nox and make sure that when you type "python" in your shell that it actually executes /sw/bin/python Then the readline module exists, and you can do all that .pythonrc.py stuff.Stuff I want to cover, possibly in the order I will cover it:
If you have any feedback about what is going well and what is going poorly for you, I would love to hear it! Please come and talk to me, send me an email, or if it is something that you are not comfortable signing your name to, you can tell me about it anonymously.
If I haven't started grading the assignments yet, late work is accepted with no penalty. After that it is 10% for every day late. After the assignment has been handed back to everyone, you can't turn it in. All of this can be changed if you get sick or have some kind of emergency. But let me know before you fail to turn in the assignment. If you are wondering whether or not you can still turn it in, you should check this page. Your current assignment looks like this, things with a past-due date that look like this can still be turned in as late work, while things that look like this have already been handed back, so you can't turn them in. If you cannot see what I am talking about, enable CSS in your browser.
This course is in large part a practicum, which
is a fancy Latin way of saying that you will be doing a lot of practice.
Thus, if your code doesn't compile (i.e. python refuses
to make a .pyc), then the assignment is ungradeable and you get a 0.
After that initial hurdle, life gets a little more fair. The gist of the grade is 2/3 correct code and 1/3 good style. These are not hard numbers, but instead are guidelines for the grader (which is me). Misspellings in your comments and bad grammar in your documentation will drag down your grade, as will hardcoded "magic numbers" and the like. You should understand your algorithm and its implementation, and your code should reflect that understanding, with comments provided to hold the reader's hand through the tricky bits. As a programming language, Python code tends to be very clear, so try not to get in the way of that.
You've made it this far. By now you either have enough character not to cheat, or you'll do it anyway. But just in case, let me say it right here: DON'T CHEAT. It is completely unacceptable academically and, on a more personal level, totally pisses me off. Anyone cheating will end up getting prosecuted as much as possible. You'll certainly fail the assignment and get a letter on your record, you'll probably also be assigned a failing grade and being forbidden from dropping the class. Please don't make me do this. Everyone involved hates it. I could spell out a bunch of rules, but they would come down to: do your own work, and be ethical and honest. If you need any refinements on this, please come and see me, I will be happy to talk to you about the specifics of a particular situation. Err on the side of full disclosure - if you talked with someone about how to solve the problem, a little comment noting that fact is the right thing to do. Despite this warning, I have caught people cheating in every class I have ever taught except last year's python class. There's not that many of you, and I'm going to read all of your code. Please don't cheat.
All the code you give to me should be freshly written for this class. Please don't recycle old code, instead write new stuff.
You should be having it. Python is a fun language to program in!
Questions? Answers!