telephone
Part of Computer Programming is sending input data to a process and getting output data back
input_object -> process -> output_object
I send things (input data) to a program to test it, and check if what I think will happen (my expectation) is the same as the results I get (reality). This helps me answer two questions:
what is the same?
what is different?
The difference helps me know what to change to get what I want. I use assertions to test if reality is the same as my expectation.
assert reality == my_expectation
where
reality is what happens when I do something with code
my expectation is what I think will happen when I do something with code
The exercises in this chapter show how I can pass objects to a function and use it to make a string (anything in quotes).
preview
I have these tests by the end of the chapter
1def assert_equal(a, b):
2 assert a == b
3
4
5def text(the_input):
6 return f'I got: {the_input}'
7
8
9def test_passing_none():
10 assert_equal(text(None), 'I got: None')
13def test_passing_booleans():
14 assert_equal(text(False), 'I got: False')
15 assert_equal(text(True), 'I got: True')
16
17
18def test_passing_an_integer():
19 an_integer = 1234
20 assert_equal(text(an_integer), f'I got: {an_integer}')
21
22
23def test_passing_a_float():
24 a_float = 5.678
25 assert_equal(text(a_float), f'I got: {a_float}')
28def test_passing_a_string():
29 a_string = 'hello'
30 assert_equal(text(a_string), f'I got: {a_string}')
31
32
33def test_passing_a_tuple():
34 a_tuple = (0, 1, 2, 'n')
35 assert_equal(text(a_tuple), f"I got: {a_tuple}")
36
37
38def test_passing_a_list():
39 a_list = [0, 1, 2, 'n']
40 assert_equal(text(a_list), f'I got: {a_list}')
43def test_passing_a_set():
44 a_set = {0, 1, 2, 'n'}
45 assert_equal(text(a_set), f'I got: {a_set}')
46
47
48def test_passing_a_dictionary():
49 a_dictionary = {
50 'key0': 'value0',
51 'keyN': [0, 1, 2, 'n'],
52 }
53 reality = text(a_dictionary)
54 my_expectation = f'I got: {a_dictionary}'
55 assert_equal(reality, my_expectation)
58def test_passing_an_object():
59 assert_equal(
60 text(object), "I got: <class 'object'>"
61 )
62 assert_equal(text(bool), "I got: <class 'bool'>")
63 assert_equal(text(int), "I got: <class 'int'>")
64 assert_equal(text(float), "I got: <class 'float'>")
65 assert_equal(text(str), "I got: <class 'str'>")
66 assert_equal(text(tuple), "I got: <class 'tuple'>")
67 assert_equal(text(list), "I got: <class 'list'>")
68 assert_equal(text(set), "I got: <class 'set'>")
69 assert_equal(text(dict), "I got: <class 'dict'>")
70
71
72# Exceptions seen
73# AssertionError
74# NameError
75# TypeError
start the project
I name this project
telephoneI open a terminal
I use uv to make a directory for the project and initialize it
the terminal shows
Initialized project `telephone` at `.../pumping_python/telephone`then goes back to the command line.
I change directory to the project
the terminal shows I am in the
telephonefolder.../pumping_python/telephoneI make a directory for the tests
the terminal goes back to the command line.
I make the
testsdirectory a Python packageDanger
use 2 underscores (__) before and after
initfor__init__.pynot_init_.pytouch tests/__init__.pyNew-Item tests/__init__.pythe terminal goes back to the command line.
I make an empty file for the tests in the
testsfoldertouch tests/test_telephone.pyNew-Item tests/test_telephone.pythe terminal goes back to the command line.
I open
test_telephone.pyfrom thetestsfolderI add the first failing test to
test_telephone.py1def test_failure(): 2 assert False is TrueI go back to the terminal
I use echo to add pytest to
requirements.txtecho "pytest" > requirements.txtI add pytest-watcher to the requirements file
echo "pytest-watcher" >> requirements.txtthe terminal goes back to the command line.
I use Out-File to add pytest to
requirements.txt"pytest" | Out-File requirements.txt -Encoding UTF8I add pytest-watcher to the requirements file
"pytest-watcher" >> requirements.txt
I use uv to install pytest-watcher with the requirements file
the terminal shows that it installed pytest-watcher and its dependencies.
I add the new files and folders to git for tracking
the terminal goes back to the command line.
I add a git commit message
the terminal shows a summary of the changes then goes back to the command line.
I use pytest-watcher to run the tests automatically
the terminal is my friend, and shows AssertionError
======================== FAILURES ======================== ______________________ test_failure ______________________ def test_failure(): > assert False is True E assert False is True test_telephone.py:2: AssertionError ================ short test summary info ================= FAILED test_telephone.py::test_failure - assert False is True =================== 1 failed in X.YZs ====================if the terminal does not show the same error, then check if
your
tests/__init__.pyhas two underscores (__) before and afterinitfor__init__.pynot_init_.pyyou ran
echo "pytest-watcher" >> requirements.txt, to addpytest-watcherto the requirements file
and try
uv run pytest-watcher . --now --patterns "**/*.py"againI add AssertionError to the list of Exceptions seen, to
test_telephone.py1def test_failure(): 2 assert False is True 3 4 5# Exceptions seen 6# AssertionErrorI change True to False in the assertion
1def test_failure(): 2 # assert False is True 3 assert False is False 4 5 6# Exceptions seen 7# AssertionErrorthe test passes.
test_passing_none
Can I pass None (the simplest object) as input to a function?
RED: make it fail
I change
test_failureto test_passing_none with an assertion for a function call with None (the simplest Python data structure) as input, totest_telephone.py1def test_passing_none(): 2 assert text(None) == 'I got: None' 3 4 5# Exceptions seen 6# AssertionErrorthe terminal is my friend, and shows NameError
NameError: name 'text' is not definedbecause I have not defined the function yet.
I add NameError to the list of Exceptions seen
GREEN: make it pass
I add the function
1def test_passing_none(): 2 def text(): 3 return None 4 5 assert text(None) == 'I got: None' 6 7 8# Exceptions seenthe terminal is my friend, and shows TypeError
TypeError: test_passing_none.<locals>.text() takes 0 positional arguments but 1 was givenbecause the assertion called the
textfunction which belongs to test_passing_none with input (None) and the function definition does not allow any inputs, the parentheses are empty.I add TypeError to the list of Exceptions seen
I add a name to the function definition
1def test_passing_none(): 2 # def text(): 3 def text(the_input): 4 return None 5 6 assert text(None) == 'I got: None' 7 8 9# Exceptions seenthe_inputis the name I used for the input, I can use any name I want.the terminal is my friend, and shows AssertionError
E assert None == 'I got: None'
because the assertion expects
'I got: None'and thetextfunction returns None.I copy the string from the terminal and paste it in the return statement to replace None
1def test_passing_none(): 2 # def text(): 3 def text(the_input): 4 # return None 5 return 'I got: None' 6 7 assert text(None) == 'I got: None' 8 9 10# Exceptions seenthe test passes.
text(None) -> 'I got: None' └── def text(the_input): └── return 'I got: None'
REFACTOR: make it better
I remove the commented lines from test_passing_none
1def test_passing_none(): 2 def text(the_input): 3 return 'I got: None' 4 5 assert text(None) == 'I got: None' 6 7 8# Exceptions seenI open a new terminal then change directories to
telephonethe terminal shows I am in the
telephonefolder.../pumping_python/telephoneI add a git commit message in the new terminal
the terminal shows a summary of the changes then goes back to the command line.
I can pass None as input to a function.
The problem with this solution is that the text function does not care about what it gets, it always returns 'I got: None' when it is called. I want it to return the object it gets as part of the string.
test_passing_booleans
Can I pass booleans from a test to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for booleans (there are only two), first with an assertion for False, to
test_telephone.py1def test_passing_none(): 2 def text(the_input): 3 return 'I got: None' 4 5 assert text(None) == 'I got: None' 6 7 8def test_passing_booleans(): 9 assert text(False) == 'I got: False' 10 11 12# Exceptions seenthe terminal is my friend, and shows NameError
NameError: name 'text' is not definedbecause the
textfunction belongs to the test_passing_none function and I cannot reach it from outside.
GREEN: make it pass
I move the
textfunction out of test_passing_none so that it can be called from anywhere in the file1def text(the_input): 2 return 'I got: None' 3 4 5def test_passing_none(): 6 assert text(None) == 'I got: None' 7 8 9def test_passing_booleans():the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: None' == 'I got: False'because the
textfunction always returns'I got: None'and this assertion expects'I got: False'.I change the return statement to give the test what it wants
1def text(the_input): 2 # return 'I got: None' 3 return 'I got: False' 4 5 6def test_passing_none():the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: False' == 'I got: None'because the
textfunction now always returns'I got: False'and the assertion in test_passing_none expects'I got: None'. My change broke the assertion that was passing before.The return statement has to use the input it gets as part of the output.
what is string interpolation?
String Interpolation is how to place objects in strings. It allows me to make one string that can have values that change.
I can use an f-string (short for formatted string literal) for string interpolation.
A string is anything inside quotes, for example
'single quotes''''triple single quotes'''"double quotes""""triple double quotes"""
how to write an f-string
f'characters {object} more characters'
I add
the_inputto the string in the return statement of thetextfunction1def text(the_input): 2 # return 'I got: None' 3 # return 'I got: False' 4 return 'I got: {the_input}'the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: {the_input}' == 'I got: False'I change the return statement to an f-string
1def text(the_input): 2 # return 'I got: None' 3 # return 'I got: False' 4 # return 'I got: {the_input}' 5 return f'I got: {the_input}' 6 7 8def test_passing_none():the test passes because Python uses the string representation of the object in the curly braces
{ }text(None) -> 'I got: None' └── def text(the_input): ├── the_input = None └── return f'I got: {the_input}' return 'I got: None 'text(False) -> 'I got: False' └── def text(the_input): ├── the_input = False └── return f'I got: {the_input}' return 'I got: False '
REFACTOR: make it better
I remove the commented lines from the
textfunction1def text(the_input): 2 return f'I got: {the_input}' 3 4 5def test_passing_none():I add an assertion for True (the other boolean) to test_passing_booleans
the terminal is my friend, and shows AssertionError
E assert 'I got: True' == 'I got: "True"I remove the quotes around True in my expectation
the test passes because Python uses the string representation of the object in the curly braces
{ }text(True) -> 'I got: True' └── def text(the_input): ├── the_input = True └── return f'I got: {the_input}' return 'I got: True 'I add the assert_equal function
1def assert_equal(a, b): 2 assert a == b 3 4 5def text(the_input):I use the assert_equal function in test_passing_none
the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: None' == 'I got: BOOM!!!'I change the expectation of the assertion to match reality
the test passes.
I remove the commented lines from test_passing_none
I use the assert_equal function in test_passing_booleans
the test is still green.
I remove the commented lines from test_passing_booleans
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_an_integer
Can I pass an integer (a whole number without decimals) as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for an integer to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert 'I got: 1234' == 'I got: "1234"'
GREEN: make it pass
I remove the quotes around the integer in my expectation
18def test_passing_an_integer():
19 # assert_equal(text(1234), 'I got: "1234"')
20 assert_equal(text(1234), 'I got: 1234')
21
22
23# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text(1234) -> 'I got: 1234'
└── def text(the_input):
├── the_input = 1234
└── return f'I got: {the_input}'
return 'I got: 1234 '
REFACTOR: make it better
I add a variable for
1234I use the variable to remove repetition of
1234the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: 1234' == 'I got: an_integer'I change my expectation to an f-string
the test passes
I remove the commented lines from test_passing_an_integer
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_float
Can I pass a float (binary floating point decimal number) as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a float (binary floating point decimal numbers) to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert 'I got: 5.678' == 'I got: "5.678"'
GREEN: make it pass
I remove the quotes around the float in my expectation
23def test_passing_a_float():
24 # assert_equal(text(5.678), 'I got: "5.678"')
25 assert_equal(text(5.678), 'I got: 5.678')
26
27
28# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text(5.678) -> 'I got: 5.678'
└── def text(the_input):
├── the_input = 5.678
└── return f'I got: {the_input}'
return 'I got: 5.678 '
REFACTOR: make it better
I add a variable for
5.678I use the variable to remove repetition of
5.678the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: 5.678' == 'I got: a_float'I change my expectation to an f-string
the test passes.
I remove the commented lines from test_passing_a_float
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_string
Can I pass a string as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a string (anything in quotes) to
test_telephone.pythe terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: hello' == 'I got: hi'
GREEN: make it pass
I change my expectation to match reality
28def test_passing_a_string():
29 # assert_equal(text('hello'), 'I got: hi')
30 assert_equal(text('hello'), 'I got: hello')
31
32
33# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text('hello') -> 'I got: hello'
└── def text(the_input):
├── the_input = 'hello'
└── return f'I got: {the_input}'
return 'I got: hello '
REFACTOR: make it better
I add a variable for
'hello'I use the variable to remove repetition of
'hello'the terminal is my friend, and shows AssertionError
AssertionError: assert 'I got: hello' == 'I got: a_string'I change my expectation to an f-string
the test passes.
I remove the commented lines from test_passing_a_string
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_tuple
Can I pass a tuple (anything in parentheses ( ) separated by a comma) as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a tuple to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert "I got: (0, 1, 2, 'n')" == 'I got: (0, 1, 2, n)'
GREEN: make it pass
I change the tuple in my expectation to match reality
33def test_passing_a_tuple():
34 assert_equal(
35 text((0, 1, 2, 'n')),
36 # "I got: (0, 1, 2, n)"
37 "I got: (0, 1, 2, 'n')"
38 )
39
40
41# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text((0, 1, 2, 'n')) -> "I got: (0, 1, 2, 'n')"
└── def text(the_input):
├── the_input = (0, 1, 2, 'n')
└── return f'I got: { the_input }'
return "I got: (0, 1, 2, 'n')"
REFACTOR: make it better
I add a variable for
(0, 1, 2, 'n')I use the variable to remove repetition of
(0, 1, 2, 'n')the terminal is my friend, and shows AssertionError
assert "I got: (0, 1, 2, 'n')" == 'I got: a_tuple'I change my expectation to an f-string
the test passes.
I remove the commented lines from test_passing_a_tuple
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_list
Can I pass a list (anything in square brackets [ ]) from a test to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a list to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert "I got: [0, 1, 2, 'n']" == 'I got: [0, 1, 2, "n"]'
GREEN: make it pass
I change the list in my expectation to match reality
38def test_passing_a_list():
39 assert_equal(
40 text([0, 1, 2, 'n']),
41 # 'I got: [0, 1, 2, "n"]'
42 "I got: [0, 1, 2, 'n']"
43 )
44
45
46# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text([0, 1, 2, 'n']) -> "I got: [0, 1, 2, 'n']"
└── def text(the_input):
├── the_input = [0, 1, 2, 'n']
└── return f'I got: { the_input }'
return "I got: [0, 1, 2, 'n']"
Python changed the double quotes (") in the list to a single quote (').
REFACTOR: make it better
I add a variable for
[0, 1, 2, 'n']I use the variable to remove repetition of
[0, 1, 2, 'n']the terminal is my friend, and shows AssertionError
E assert "I got: [0, 1, 2, 'n']" == 'I got: a_list'I change my expectation to an f-string
the test is still green.
I remove the commented lines from test_passing_a_list
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_set
Can I pass a set (anything in curly braces { }, not key-value pairs) from a test to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a set to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert "I got: {0, 1, 2, 'n'}" == 'I got: {0, 1, 2, "n"}'
GREEN: make it pass
I change the set in my expectation to match reality
I use ctrl/command+s (Windows & Linux/MacOS) to run the test a few times
if the result of
text({0, 1, 2, 'n'})is equal to"I got: {0, 1, 2, 'n'}"the test passes because Python uses the string representation of the object in the curly braces{ }text({0, 1, 2, 'n'}) -> "I got: {0, 1, 2, 'n'}" └── def text(the_input): ├── the_input = {0, 1, 2, 'n'} └── return f'I got: { the_input }' return 'I got: {0, 1, 2, 'n'}'if the result of
text({0, 1, 2, 'n'})is NOT equal to"I got: {0, 1, 2, 'n'}", the terminal shows AssertionError, for exampleE assert "I got: {0, 'n', 2, 1}" == "I got: {0, 1, 2, 'n'}"
Python cannot guarantee the order of the things in the set and the order matters for the assertion that is comparing the strings because
these two are the same set
{0, 'n', 2, 1} == {0, 1, 2, 'n'}these two are not the same string
"{0, 'n', 2, 1}" != "{0, 1, 2, 'n'}"
I add a variable for
{0, 1, 2, 'n'}I use the variable to remove repetition of
{0, 1, 2, 'n'}the terminal is my friend, and shows AssertionError
E assert "I got: {0, 1, 2, 'n'}" == 'I got: a_set'I change my expectation to an f-string
I use ctrl/command+s (Windows & Linux/MacOS) to run the test a few times and the test stays green with no random failures because Python uses the string representation of the object in the curly braces
{ }.It can guarantee the order when I use a variable and the f-string to refer to the same exact set.
REFACTOR: make it better
I remove the commented lines from test_passing_a_set
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_a_dictionary
Can I pass a dictionary (any key-value pairs in curly braces { } separated by commas) as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a test for a dictionary to
test_telephone.pythe terminal is my friend, and shows AssertionError
E assert "I got: {'key..., 1, 2, 'n']}" == 'I got: {key0...[0, 1, 2, n]}'
GREEN: make it pass
I change my_expectation to match reality
48def test_passing_a_dictionary():
49 reality = text({
50 'key0': 'value0',
51 'keyN': [0, 1, 2, 'n'],
52 })
53 my_expectation = (
54 "I got: "
55 # "{key0: value0, keyN: [0, 1, 2, n]}"
56 "{'key0': 'value0', 'keyN': [0, 1, 2, 'n']}"
57 )
58 assert_equal(reality, my_expectation)
59
60
61# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text({
'key0': 'value0', 'keyN': [0, 1, 2, 'n'],}
) -> ("I got: {'key0': 'value0',"
│ 'keyN': [0, 1, 2, 'n']}")
└── def text(the_input):
├── the_input = {
│ 'key0': 'value0', 'keyN': [0, 1, 2, 'n']
│ }
└── return f'I got: { the_input }'
return ("I got: {'key0': 'value0',"
'keyN': [0, 1, 2, 'n']}")
REFACTOR: make it better
I add a variable for
{'key0': 'value0', 'keyN': [0, 1, 2, 'n'],}I use the variable to remove repetition of
{'key0': 'value0', 'keyN': [0, 1, 2, 'n'],}the terminal is my friend, and shows AssertionError
E assert "I got: {'key..., 1, 2, 'n']}" == 'I got: {a_dictionary}'I change
my_expectationto an f-stringthe test passes.
I remove the commented lines from test_passing_a_dictionary
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
test_passing_an_object
Can I pass any object as input to a function?
RED: make it fail
I go back to the terminal where the tests are running
I add a failing test to see what happens when I pass a class from a test to the
textfunction, totest_telephone.pythe terminal is my friend, and shows AssertionError
E assert "I got: <class 'object'>" == 'I got: object'object is the mother class that all Python objects come from because everything in Python is an object.
GREEN: make it pass
I change my expectation to match reality
58def test_passing_an_object():
59 # assert_equal(text(object), 'I got: object')
60 assert_equal(
61 text(object), "I got: <class 'object'>"
62 )
63
64
65# Exceptions seen
the test passes because Python uses the string representation of the object in the curly braces { }
text(object) -> "I got: <class 'object'>"
└── def text(the_input):
├── the_input = object
└── return f'I got: { the_input }'
return "I got: <class 'object'>"
REFACTOR: make it better
I add an assertion for bool (the class for booleans)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'bool'>" == 'I got: bool'I change my expectation to match reality for bool
the test passes.
I add an assertion for int (the object for whole numbers without decimals)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'int'>" == 'I got: int'I change my expectation to match reality for int
the test passes.
I add an assertion for float (the object for binary floating point decimal numbers)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'float'>" == 'I got: float'I change my expectation to match reality for float
the test passes.
I add an assertion for str (the object for anything in quotes)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'str'>" == 'I got: str'I change my expectation to match reality for str
the test passes.
I add an assertion for tuple (the object for anything in parentheses
( )separated by a comma)the terminal is my friend, and shows AssertionError
E assert "I got: <class 'tuple'>" == 'I got: tuple'I change my expectation to match reality for tuple
the test passes.
I add an assertion for list (the object for anything in square brackets ‘[ ]’)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'list'>" == 'I got: list'I change my expectation to match reality for list
the test passes.
I add an assertion for set (the object for anything in curly braces
{ }, not key-value pairs)the terminal is my friend, and shows AssertionError
E assert "I got: <class 'set'>" == 'I got: set'I change my expectation to match reality for set
the test passes.
I add an assertion for dict (the object for key-value pairs in curly braces ‘{ }’ separated by commas)
the terminal is my friend, and shows AssertionError
E assert "I got: <class 'dict'>" == 'I got: dict'I change my expectation to match reality for dict
all the tests are passing because Python uses the string representation of the object in the curly braces
{ }text(any object) -> "I got: <class 'any object'>" └── def text(the_input): ├── the_input = dict └── return f'I got: { the_input }' return "I got: <class 'any object'> "I remove the commented lines from test_passing_an_object
I add a git commit message in the other terminal
the terminal shows a summary of the changes then goes back to the command line.
close the project
I close
test_telephone.pyI click in the terminal where the tests are running
I use q on the keyboard to leave the tests. The terminal goes back to the command line.
I change directory to the parent of
telephonethe terminal shows
.../pumping_pythonI am back in the
pumping_pythondirectory.
review
I ran tests to see what happens when I pass objects from a test to a program and place them in an f-string which is one way to do string interpolation.
I still have the problem where I wrote the assert_equal function in this project, even though I wrote it in previous projects. There has to be a better way where I can write the function once, then use it any time or anywhere I want.
code from the chapter
what is next?
would you like to test separating the tests from the solutions?
rate pumping python
If this has been a 7 star experience for you, please CLICK HERE to leave a 5 star review of pumping python. It helps other people get into the book too.