- PDF Free Download

Size: px

Start display at page:

Download ""

Octavia French
6 years ago
Views:

1 CS 11 Project #6 Due THURSDAY, December 7 th, 11:59pm. Classes and Exceptions Background: Classes allow us to define new types for Python. We can first think of a class as defining a new container instead of a list, tuple, set, or dictionary, we can have our own collection of values, each with a chosen name rather than an index/key. We can then read out a value or update a value, much like reading or replacing the values in a list or dictionary. But we can also put methods in a class definition, giving us a way to specify the exact ways we should interact with values of this new type. Once we have created a class definition, we can create as many objects of the new type as we want and use them in our programs. We can create entirely new types during the design phase of writing a program. This enables us to think in terms of types (and instances of types) that better model what we see in the real world, instead of endlessly relying on lists or dictionaries (and having to remember exactly how we intended to use those things as proxies for the values we actually had in mind). Exceptions allow us to recover from unusual events some unavoidable (user types in bad file name or bad input in general), some unexpected (such as IndexErrors when stepping through a list). Without exceptions, we tend to program in an "ask permission, then attempt" style of calculation. But using exceptions, we can instead program in a "try it first, beg for forgiveness" approach by writing code that specifies how to recover from exceptions that we allowed to occur. Project Basics document: Project Six tester file: Grading Rubric There are 105 test cases, each worth one point. There's no specific function identified as the extra credit. if you don't comment your code or submit it correctly, we might deduct up to 10 points. if you use globals, we might deduct up to 10 points. if you import unauthorized things, you might lose all points for related test cases. What's Allowed? As long as you don't import anything, you can use anything built-in or that you create. Now that we're really writing our own datatypes, the built-ins aren't really designed to solve our quite-specific problems! Just as we used to say "add your own helper functions and call them", you can also add your own helper methods and use them. Task We will implement some basic classes and method to manage invitations and responses for planning a party. An Event can add/discard Invitations, and can receive Responses. By calling the methods, someone could managd their attendees list for their party. 1

2 Notes / Assumptions / Requirements Don't import anything, and you can use all built-ins/methods that are otherwise available. J adding definitions: You may add additional methods and functions in support of your solution. displaying things: str and repr are used by many other places in Python to get a string representation of the object. Specifically, str() calls str, and repr() calls repr, on any objects they receive as arguments. str often generates a human-centric representation, appropriate for a human reading what is present. repr often generates a Python-centric representation. The goal of repr is actually to have a string that could be evaluated to re-generate an identical object. In general, we would quite prefer it to look like a valid constructor call, if possible. Ultimately, we can have the same representation in str and repr if we'd like; in fact, when we didn't explicitly describe two different string representations for str and repr to return, we can define one in terms of the other, like this: def repr (self): return str(self). Just remember the original intent of str vs repr. It's good practice to define init, str, and repr immediately before writing any extra methods in a Python class at a minimum, and perhaps also eq as well. what to return? Many methods don't specify a return value, and thus they return None after modifying the object. handling exceptions: notice where we create exception types, and where we catch those exceptions. Be sure you don't catch the exception too early, or when not requested! When testing smaller parts of your code, it may be possible and even expected/required that specific inputs to a function/method will cause an exception to propagate (crash), rather than returning normally with a return value. We could extend this project to a full program with user interactions; this top-level layer of code would be a great place to catch more exceptions and ask for decisions and responses whenever we catch certain exception types. Since we're not writing the larger program that was described, there's no menu and user interaction present to do this particular style of interaction. testing individual methods: you can also narrow down the focus of our tester by feeding it the name of a class (which only runs the init/str/repr/eq/lt kinds of tests), or the method name of things that are needed in a particular class; this is the Event class. We had to manually create this listing, and it's how the test cases were named. Here is the full list of test batches you can select: o classes: Invitation, Response, InviteNotFoundError, TooManyError, Event o methods: find_invite, pop_invite, add_invite, find_response, pop_response, read_response, count_attendees, count_rejections, max_attendance, count_pending, rescind_invitation o for example: demo$ python3 tester6p.py Event Response find_invite pop_invite

3 Required Classes Working through the classes in the given order is the simplest path to completion. Be sure to complete the init/str/repr/eq/lt definitions before moving on to other classes that use them. class Invitation: def init (self, name, num_invited): create/initialize instance variables for name and num_invited. Assume num_invited is a positive int. def str (self): create/return a string as in this example: "Invitation('Alice', )" def repr (self): create/return a string identical to the str output. def eq (self, other): determine if this object (self) is equivalent to other. Two Invitations are considered equal if they have the same name and same number of invited people. def lt (self, other): this is the "less than" method. Return the boolean answer of if self<other. First compare names, then num_invited if needed, to determine if self<other. Examples in the test cases. o By providing this method,.sort()/sorted() can sort lists of Invitations. class Response: def init (self, name, ans, num_attending): create/initialize instance variables for all three non- self parameters. Assume ans is a bool and num_attending is a non-negative int. def str (self): create/return a string as in this example: "Response('Alice',, )" def repr (self): create/return a string identical to the str output. def eq (self, other): determine if this object (self) is equivalent to other. Two Responses are considered equal if they have the same values for all instance variables. def lt (self, other): this is the "less than" method. Return the boolean answer of if self<other. First compare names, then ans if needed, then num_attending if needed, to determine if self<other. Examples in the test cases. class InviteNotFoundError(LookupError): Be sure to include the (LookupError) portion above in your class declaration, so that this is an extension of the LookupError class (with all the exception properties that implies). def init (self, name): create/initialize instance variable for name. def str (self): create/return a string as in this example: "no invite for 'Alice' found." def repr (self): create/return a string as inthis example: "InviteNotFoundError('Alice')" def eq (self, other): determine if this object (self) is equivalent to other (both have same name). class TooManyError(ValueError): Be sure to include the (ValueError) portion above in your class declaration, so that this is an extension of the ValueError class (with all the exception properties that implies). def init (self, num_requested, num_allowed): create/initialize instance variables for both numbers. Assume that num_requested > num_allowed. Assume both are non-negative ints. def str (self): create/return a string as in this example: "too many: requested, 3 allowed." def repr (self): create/return a string as in this example: "TooManyError(5, 3)" def eq (self, other): determine if this object (self) is equivalent to other (both have same instance variable values). 3

4 class Event: def init (self, title, invites=none, responses=none): create/initialize instance variables for title, invites, and responses. When invites or responses is None, use an empty list as the value. The incoming lists of invites and responses might not have been sorted, but must be sorted as part of this constructor. def str (self): create/return a string similar to: """Event('party', [], [])""" Hint: when obtaining strings for the lists of invites/responses, how can you rely upon other str definitions to make this a short/trivial method to write? def repr (self): create/return a string identical to the str output. def eq (self, other): determine if this object (self) is equivalent to other (both have same instance variable values). find_invite(self, name): retrieve the Invitation by that name, and return a reference to that Invitation object. When no such invitation is found, this method will raise an InviteNotFoundError. pop_invite(self, name): retrieve and remove the invitation by the given name from the list of invites, and return it. Any Responses of the same name should be discarded. When no such invitation is found, this method will raise an InviteNotFoundError. add_invite(self, inv): add this invitation to the event's list of invites; the list must be sorted before returning. If there is already an invitation by that name, discard the previous one. Hint: use sort(). find_response(self, name): retrieve the Response by that name, and return a reference to that Response object. When no such response is found, this method will raise a LookupError such as the following: "no Response found with name='alice'." pop_response(self, name): retrieve and remove the response by the given name from the list of responses, and return it. When no such response is found, it will raise a LookupError as follows: "no Response found with name='alice'." read_response(self, response): check the response, and possibly add it to the list of responses, count_attendees(self): return how many people are currently attending, according to the responses list. count_pending(self): return how many inviteds' invitations have no corresponding response. max_attendance(self): return the highest number of attendees, if all remaining unanswered invitations according to the following rules: o If the name wasn't on the invitation list, raise an InviteNotFoundError out of the method. o When the response indicates more attending than invited, raise a TooManyError out of the method. o When the previous two errors are avoided, add response to the list (removing any old ones by that name) o The responses list must be sorted before returning. o When the response indicates not attending, replace its num_attending with 0. responded 'yes' with the full number of invited. count_rejections(self): Count how many responses indicated not coming (how many invited people are not coming, not just how many rejection responses were received some are "no" responses, others are bringing less than invited). All responses should have been validated when added, so if a response has no associated invitation, behavior is undefined (you don't have to consider the situation, and whatever your program does in these situations is acceptable; this is the normal idea of "undefined behavior", look for it in specs in the future!). rescind_invitation(self, name): we've decided a person is no longer invited to our party; find and remove the invitation by that name from this event, as well as any response they may have sent. This method raises no errors when invitations or responses weren't found. Hint: use exception handling to make this a simple function.

5 Example Session i = Invitation("Alice", ) i. str () "Invitation('Alice', )" i. repr () "Invitation('Alice', )" i. eq (Invitation("Alice", )) i. lt (Invitation("Bob", 1)) i. lt (Invitation("Alice", 3)) i. lt (Invitation("Alex", 3)) r = Response("Alice",,) str(r) "Response('Alice',, )" repr(r) "Response('Alice',, )" r == Response("Alice",,) r == Response("Bob",,) r < Response("Bob",,) r < Response("Alice",,) r < Response("Alice",,) = Event("party",[Invitation("Alice", ), Invitation("Bob", ), Invitation("Alex", 3)], [Response("Alice",,0), Response("Alex",,)]) Invitation('Alice', ), Invitation('Bob', )], [Response('Alex',, ), Response('Alice',, 0)]).find_invite("Alice") Invitation('Alice', ).pop_invite("alice") Invitation('Alice', ) Invitation('Bob', )], [Response('Alex',, )]).add_invite(invitation("allen", 3)) [Response('Alex',, )]).find_response("alex") Response('Alex',, ).pop_response("alex") Response('Alex',, ) []).read_response(response("allen",,)) [Response('Allen',, )]).read_response(response("alex",,1)) [Response('Alex',, 0), Response('Allen',, )]).count_attendees().count_pending().max_attendance().count_rejections().rescind_invitation("allen") Invitation('Bob', )], [Response('Alex',, 0)]) # exception related ie = InviteNotFoundError("Alice") str(ie) "no invite for 'Alice' found." ie == InviteNotFoundError("Bob") raise ie main.invitenotfounderror: no invite for 'Alice' found. te = TooManyError(,3) str(te) 'too many: requested, 3 allowed.' te == TooManyError(,3) raise te main.toomanyerror: too many: requested, 3 allowed..find_invite("patrick") main.invitenotfounderror: no invite for 'Patrick' found..pop_invite("patrick") main.invitenotfounderror: no invite for 'Patrick' found..find_response("patrick") LookupError: no Response found with name='patrick'..pop_response("patrick") LookupError: no Response found with name='patrick'..read_response(response("patrick",,3)) main.invitenotfounderror: no invite for 'Patrick' found..read_response(response("bob",,100)) main.toomanyerror: too many: 100 requested, allowed..rescind_invitation("patrick") Invitation('Bob', )], [Response('Alex',, 0)])

CS 1110 Final, December 8th, Question Points Score Total: 100

CS 1110 Final, December 8th, Question Points Score Total: 100 CS 1110 Final, December 8th, 2016 This 150-minute exam has 8 questions worth a total of 100 points. Scan the whole test before starting. Budget your time wisely. Use the back of the pages if you need more