- Reading Journal Debrief
- Complete Reflection and Teaming Survey 2
- Teaming and pair programming discussion and practice
- MP3 kickoff
For Next time
- Gallery show postponed - submit your art!
- Complete first Project Toolbox
- There are supplemental readings due Thursday but no Reading Journal exercises
Reading Journal Debrief
In this Reading Journal we looked at a very common error that can be very frustrating to debug:
class Kangaroo: def __init__(self, name, contents=): # Warning: mutable default argument bug! self.pouch_contents = contents
The core “gotcha” here is that default argument values are evaluated once when the function is defined, not every time it is called.
In this case, it means that the new list is created one time, and each new
Kangaroo instance (that did not provide contents to override the default) has a reference to the same list.
This would be true of any mutable object as a default argument, not just
dict, your custom classes). Here is another implementation, showing a Python idiom commonly used to avoid this bug:
class Kangaroo: def __init__(self, name, contents=None): if contents == None: contents =  self.pouch_contents = contents
Here we’ve used
None (immutable) as a stand-in for the case when no contents have been passed and we should create an empty list. The new list is created inside the body of the
__init__ method when it is called, so each
Kangaroo instance gets its own empty list vs a shared reference.
General advice: avoid using mutable objects as default values of function arguments.
Agenda: sorting objects
For this Reading Journal, you had to implement a
print_agenda method that displays
Event objects in chronological order.
The key challenge here was sorting the
Events: Python provides many
techniques for sorting,
but they don’t know how to sensibly sort your custom objects without some help from you.
Let’s imagine that you have a list of
The first design choice to make is whether you should maintain the list in sorted order at all times, or sort it only when required (e.g. whenever
print_agenda is called). There are pros and cons to each style, depending on application:
In this case the burden falls on your
add_event method to ensure that you insert new
Events in chronological order (perhaps using your
is_after method). It takes a little more time to add an
Event, but you afterwards you can rely on the list being sorted at no extra cost.
Sort on demand
With this approach you have a simpler insertion process, but you must sort the list every time you need it to be in order. This may be more expensive depending on whether adding new
Events or printing the
Agenda is more common.
Python knows how to sort built-in types (e.g. integers), but not your custom classes. Let’s say you have a
class Time: def __init__(self, hour=0, minute=0, second=0): self.hour = hour self.minute = minute self.second = second def to_int(self): return 60*(60*self.hour + self.minute) + self.second
Sorting key function
list.sort method and
sorted function both take an optional
key parameter, which expects a function that takes the object to be sorted and returns a key used to sort it. We could write such a function for
def event_start(event): """Given Event object containing a start Time, return time as sortable key""" return event.start.to_int()
and then use it to sort a list of Events:
for event in sorted(some_events, key=event_start): ... do something
Anonymous lambda functions
If you just want to sort
Events, it can be a bit clunky to write the
event_start function solely to pass as a
You’ll often see people use an anonymous
lambda function (a function defined on the fly that is not bound to a name) for this purpose. Equivalently:
for event in sorted(some_events, key=lambda e: e.start.to_int()) ... do something
Implement comparison operator(s)
If you implement the less-than __lt__ method for your classes (so that
time1 < time2 works), then Python now knows how to sort your custom objects.
# inside class Time: def __lt__(self, other): return self.to_int() < other.to_int()
Agenda: __str__ vs __repr__
We started discussing
__repr__ methods for Classes last time.
Here is another example showing the behavior when trying to print your Time class using the
>>> times = [Time(6,20), Time(2,45), Time(4)] >>> print(times) 06:20:00 >>> print(times) [<__main__.Time object at 0x105b1d0b8>, <__main__.Time object at 0x105b1d0f0>, <__main__.Time object at 0x105b1d128>]
When printing collections like lists, the
__repr__ method is used for the contained objects. As an example of why, let’s imagine our
TicTacToe class has a pretty
__str__ method that gives:
X| |O ----- |X|O ----- O|X|
If we used that for the
__repr__, and printed a list of two
TicTacToe objects, it would be a mess!:
[X| |O ----- |X|O ----- O|X| , X| |O ----- |X|O ----- O|X| ]
[<__main__.TicTacToe object at 0x105b1d160>, <__main__.TicTacToe object at 0x105b1d168>]
__repr__ methods, a great goal is for the result to be a valid Python expression that could recreate the object (e.g.
If a class does not define a
__str__ method, the
__repr__ method is used instead (if it exists).
Pair programming is a software practice where two developers sit together at the same computer to write software. Only one developer, the “driver”, has their hands on the keyboard and is responsible for actually typing in the code. The other person, the “navigator”, participates just as actively but focuses on planning at a higher level. Partners switch roles frequently.
Pair programming may seem inefficient at first, but we find that the benefits in learning, creative problem solving, and reduction of errors often more than outweigh the time spent together working on the “same task”.
Pair programming is a skill that requires practice. Just like in other teamwork situations, try to be generous with your partner and provide direct feedback to help you both improve.
With your partner, take on one of the Going Beyond challenges (or invent one of your own) for the Agenda in the last reading journal. You’ll need to download your reading journal as a Python script so you can develop the code together.
We’re also available for conversation about issues that arose using classes in the last reading journals,
geometry.py, and our “social network app” from last time.