Hmm. What I meant for you guys to turn in for your “assignment #4’s” was:
- A git repo, with these contents:
- Your customer_service.py program that allows the user to interactively purchase tickets
- Your SQLite database file that has all the stuff from galactic in it (and optionally, other rows left over from your assignment #3)
- Optionally, Python code in some other file (perhaps “bulk_import.py” or some such) that does your assignment #4 bulk-import loading, although I don’t actually need that for grading.
Instead, I’m getting lots of people whose “customer_service.py” file isn’t actually their customer service program at all, but appears instead to be their assignment #4 bulk-import code. I’m also getting people seem to have expected me to run their bulk-import code to populate their database with galactic stuff, instead of including an SQLite database that already has the galactic stuff included.
All this is taking me longer than I want to mess around with. And it has proven to be too onerous to try to dig up old assignment #3 submission emails, which may not even be compatible with any schema changes you had to make to accommodate galactic in assignment #4, etc.
**So, since I’m old and tired and want to make the process of grading 52 of these as streamlined as possible, I’m going to have everyone resubmit your assignment #3/#4 according to the above specifications. The subject line for the email should be “CPSC/DATA 350 Assignment #3/#4 resubmission”.
To be crystal clear: when I open your email, it should contain a git bundle as an attachment. When I clone that git bundle, I should then have (1) a customer_service.py file which does the whole assignment #3 thing, and which works on (2) your assignment #4 database file that contains all the galactic data. Also note: I will not be running any code to actually perform the bulk import; the results of that importing process should already be reflected in the database.
Submissions will be graded in the order they are received.
