Errata

"Now let’s look at that request module again"
change "request" to "requests" (plural)

on page xxxiv, "Do not download version 2.7.", but figures of pp 26 -27are made by version 2.7.9.

"The highest precedence in this expression is exponentiation. 3 is 9^2."

It should be:

"The highest precedence in this expression is exponentiation. 3^2 is 9."

"We'll also need to save this somewhere so we can use it in step 4."

Since the dog's age is used in step 3, it should be:
"We'll also need to save this somewhere so we can use it in step 3."

The code written is:

print(winner, 'won. The computer chose', computer_choice + '.'

But the second parentheses is missing. So it should be:

print(winner, 'won. The computer chose', computer_choice + '.')

You’ve create some logic that never lets the loop end,

Should be:
You’ve created some logic that never lets the loop end,

There is no clue for the word 23 across.

The answer is "Ferrari" not "Ferarri".

With the right solution in item 1 down, we cannot fit the 4th word across "comparison".

Description says, "Pretend you're the Python Interpreter…".
Maybe the "BE the Interpreter" template should be used here.

Original: "Each time we iterate, we print “Smoothie#", the index, and the smoothie at that index."

Missing space before "#".

Missing a space before 18. It should be:

Solutions with highest score: [11, 18]

Original: "Scores and costs are parallel lists"
Since it's a variable name, "scores" should be lowercase.

Change 'cost list' to 'costs list'. (cost holds a single value)

Original: "And we use each best_solutions item as an index into the cost list."

Should be: "And we use each best_solutions item as an index into the costs list."

The code written is:

print('Solution', most_effective, 'is the most effctive with a cost of', costs[most_effective])

But the second effective is missing an "e". So it should be:

print('Solution', most_effective, 'is the most effective with a cost of', costs[most_effective])

replace "previous page" with "page 153" (PDF) to establish a correct back-reference

Intro text says "You’ll find all the code up until now listed below." while annotation says "We're just showing you the new code."

Annotation is correct. Suggestion to change intro text to "You'll find our solution below."

“WOOF WOOF" and "woof woof” should probably be formatted as literal text or surrounded by quotes.

Original: "And if we supply an argument for message, then our greet function will gladly accept that as the message argument."

Suggestion: "…will gladly accept that as a value for the message parameter."

Original: "Just make sure your calls provide any required arguments before the keywords arguments."

"keywords" should IMHO be singular.

Original: "...except, when we swap two values of the score list […]"
Change to: "...except, when we swap two values of the scores list […]"

Original: "You’ve got a brain twister ahead, and the bullet points and the crossword..."

There is no crossword in chapter 4b.

Original: "Take the list below and bubble sort it, showing your work just like we did on the previous two pages."

Change "the previous two" to "pages 228 and 229." for correct context.

Original: "After you’ve done the exercises, look at the end of the chapter to see if you got it right."

Update: "Here are our solutions."

Original: "[…] to your analyze file."
Missing formatting and file extension:

"[…] to your <literal>analyze.py</literal> file."

Original: "Or, likewise, if you omit the ending index, then slice assumes you mean to stop the end of the list:"

1. format "slice" as literal/code
2. replace "list" with "string". Usage of slice for lists is being introduced at bottom of page, but not yet.

shape() was introduced as a method on page 316/317, ist now (on page 324) an attribute. Is being used as a method only throughout the rest of the chapter.

Suggestion: Only use it as a method to avoid confusion. This would also correspond with page 319 where access to attributes via getter/setter methods is being explained.

sentence = "To do that we simply use a for/in statement over our global turtles lists."

sentence.replace("lists", "list")

Original: "Notice we can pass any turtle into make_square, not just slow_poke."

Change "slow_poke" to "slowpoke".

Original: "Remember in Python a dictionary key can be any value, including integers."

IMHO this is misleading/confusing for two reasons:

1. a key and a value are different things, esp. in the context of dictionaries.

2. *any* value (or type)
Not absolutely sure here. Can a list be used as a dictionary key? I don't think so (hashing issues, AFAIK). See e.g. https://wiki.python.org/moin/DictionaryKeys

Page 363 (PDF) says: "For keys you can use numbers, strings, or Booleans. For dictionary values you can use any valid Python value."

Suggestion: Rephrase to: "Remember in Python many data types can be used as dictionary keys, including integers."

"Let’s use the read method to get the entire contents of the lib file..."
-> "[…] lib.txt file...

Example shows text with \n sequences, but placeholders are highlighted in bold. Suggestion to highlight \n instead.

"exploring exception" should probably be plural:
"exploring exceptions"

Original: "how to handle expectations".
Should probably be: "how to handle exceptions"

But then… that's just what I'd expect to see… maybe throw an unexpected exception

Original: "Let's store the crazy lib filename in a variable to…"

"Crazy Lib" refers to the game and thus should be uppercase:
""Let's store the Crazy Lib filename in a variable to…""

function and method names are formatted bold instead of fixed-width (for code).

Inconsistent headings: Heading on page 426 (Coding Cross) is used throughout the book. On page 433 (solution) the heading "File i/o cross Solution" is used.

Throughout the book the chapter title is being used as a "running head" for odd pages. In ch10 'web services' is used instead of "using web apis".

This should probably be changed to "using web apis".

All these refer to the same thing, so I summarized them.
Occurences of "service" should be replaced by "API".

Here we go:

436 "brain power" 3rd sentence:
"How would you write the app without such a service?"
-> change "such a service" to "such an API"

438 left code annotation between last paragraph and url:
"Here’s another URL to a web service for weather data."
-> change "URL to a web service" to "URL to a web API"

442 screenshot annotation:
"Open Notify supplies three different services."
-> change "three different services" to "three different APIs"

446 Q&A, 1st answer, 3rd sentence:
"But with JSON [...] to another program or service."
-> change "program or service" to "program or API"

449 top left annotation:
"Let’s set a variable url to the URL address of the ISS web service."
-> change "ISS web service" to "ISS web API"

449 "Watch it!", 1st sentence:
"At the time of writing, the ISS location service is a working, healthy service. Of course there are no guarantees in the future; so if for some reason the ISS location service is not operating"
-> change "ISS location service" to "ISS location API"

450 "Watch it!", 3rd sentence:
"Paste the URL into your browser to make sure you have connectivity and the service is up and running"
-> "Paste the URL into your browser to make sure you have connectivity and the API is up and running"

450 "Watch it!", last sentence:
"If it appears as if something is wrong with the Open Notify service, then revisit the Watch it! on the previous page."
-> change "Open Notify service" to "Open Notify API"

450 1st paragraph under "How to use JSON in Python", 1st sentence:
"So we’ve got our response from the ISS location service, [...]"
-> change "ISS location service" to "ISS location API"

457 2nd sentence:
"We’ve got everything in place and we’ve got a location back from the Open Notify service, so all we need to do is put it all together."
-> change "Open Notify service" to "Open Notify API"

462 bullet points, 5th bullet
"Web services respond to requests, sending data, often using the JSON notation."
-> change "Web services" to "Web APIs"

463 xword, 1 down:
"He wrote the ISS location service."
-> change "ISS location service" to "ISS location API"

Disclaimer: Please don't shoot the messenger. ;)

" I typedthe Spotify URL into my browser and I got a “no token” error."

Maybe include a hint on page 439 that the reader might not get the expected result and things will be explained on the following page.

If this is intentional, please ignore my erratum about p439

Original: "the terminal app"

"Terminal" should be written with a capital T since it refers to an actual app with that name.

"Another great way to find Python
packages is to search for them with Google using
search terms like “python3 request module” or […]"

Change “python3 request module” to “python3 requests module” (plural)

"Now let’s look at that request module again"
Change "request" to "requests" (plural)

"The text property holds the real data of the response, typically in JSON format."

Change "property" to "attribute" for consistency?

Text: "Let's move to the right coordinate."

To avoid confusion I suggest to rephrase this to "Let's move to the right coordinates."

Otherwise "right" could be seen as a direction.

"A Web API typically provides a documented Application Programming Interface (API) that describes the data it can provide and services it has available."

That would mean, that the API provides an API. I guess what is meant is that the API provides (or comes with) some sort of documentation that describes the data and services.

The book reads
Using the requests library we issued a request using the get method

but shouldn't it be "issue" instead of "issued"? All other sentences are using the present tense except this one.

"17. Documented functions of a Web API."
Answer: API

Letters "PI" are not visible. Crossword graphic is probably a tiny bit too wide.

This seems odd. Maybe change the question to something like:
"Users should read this before using a Web API."
Answer: Documentation

(almost 11pm, I might be biased)

"left button" (i.e. mouse button) is using the same cognitive "namespace" as "start button", "clear button" (i.e. interface buttons).

Suggestion: use "left mouse button" for better comprehension and to avoid confusion.

"Now we need to write the code to load a pattern into the grid mode."

"grid mode" -> "grid model"

"Note that only ServiceDogs will have this attribute because only ServiceDogs will execute this _init__ method."

Missing left underscore for dunder-init.
Should be: __init__

"arbitary" should, perhaps, be "arbitrary"

"Create a frisbeeDog and a Frisbee."

should be

"Create a FrisbeeDog and a Frisbee."
(uppercase "F" for "FrisbeeDog")

"[…] you could improve the implementation with the iterable pattern that we mentioned much earlier in the book."

The pattern is introduced in chapter 9 as "iterator (design) pattern".

Suggested changes:
* use same wording: "iterator pattern"
* explicitely mention chapter 9 for ease of reference

"[…] you could improve the implementation with the 'Iterator' design pattern that we mentioned in chapter 9 of this book."

" The class we’re subclassing is often called the superclass or supertype."

First and only mention of "supertype" in the book.

"Override the str method to return the string you’d like displayed when your object is printed by print."

Missing underscores around "str",
should be "__str__".

"The isinstance method returns True […]"

According to Python documentation, isinstance is a built-in function, not a method.

The lyrics list erroneously has the word "saw" and also transposes the order of "you" and "on". The initial letter "s" and the reversed order of "y" and "o" show up in the last two shell output examples. The existing syntax:

lyric = ['I', 'saw', 'heard', 'on', 'you', 'the', 'wireless', 'back', 'in', '52']

Should be:

lyric = ['I', 'heard', 'you', 'on', 'the', 'wireless', 'back', 'in', '52']

The second shell output example is presently:

['I', 's', 'h', 'o', 'y', 't', 'w', 'b', 'i', '5']

But should be:

['I', 'h', 'y', 'o', 't', 'w', 'b', 'i', '5']

The last shell output example is presently:

['s', 'o', 'y', 't', 'w']

But should be:

['y', 'o', 't', 'w']

redundant entries for "macOS" and "MacOS". Official name is "macOS"

"module view controller pattern. See MVC (module view controller) pattern"

should be

"model view controller pattern. See MVC (model view controller) pattern"

Index entries:

requests (Web APIs) about 437
[...]
request module process 447

and

responses (Web APIs) about 437
[…]
request module process 447–448

In both cases, the sub-entry should read "requests module…" (plural)