Errata

First sentence following "Hooking into the "with" Statement":
"At stated at the end..." should be "As stated at the end"

Note from the Author or Editor:

Note: this is an errata for the 2nd edition, not the first.

text printed in handwriting should be "These two lines look OK." instead of "Thes two lines look OK."

Note from the Author or Editor:
Yes, change "Thes" to "These".

typo: change "messgage" to "message"

Note from the Author or Editor:
Well spotted. Thanks, and noted.

--Paul.

"the club?s Android?s phones."

excessive possessive; should be "the club?s Android phones."

Note from the Author or Editor:
"Android's" should be "Android".

wrong kind of single quotes on entries: '59:59?, '56:29?

Note from the Author or Editor:
Replace typographical quote after 59:59.

the comprehensions results,"

incorrect possessive, should be "the comprehension's results,"

Note from the Author or Editor:
Change "comprehensions" to "comprehension's" in bottom paragraph.

"associated columns headings"

Should be "associated column headings" or "associated columns' headings".

Note from the Author or Editor:
Change "columns" to "column's" in middle of page.

"might help here?"

The sentence should end in a period instead of a question mark.

Note from the Author or Editor:
Remove "?" after "might help here".

Because the[y] have no affect on the timing data,

Change "the" to "they".

Note from the Author or Editor:
Change "the" to "they".

PyQT is actually written PyQt (with a lowercase 't').

Note from the Author or Editor:
Change "PyQT" to "PyQt".

Jeff Friedl?s regular expression ?bible?, which is well worth a look if you want to learn more.

Awkward sentence. Perhaps remove the word "which".

Note from the Author or Editor:
Remove ", which" from the first comment.

add it to your modules documentation strings

missing possessive apostrophe: should be modules'

Note from the Author or Editor:
Replace "modules" with "module's".

course,there

missing space after comma

Note from the Author or Editor:
Add a space after "And, of course,".

comes in various licencing flavor

should be "flavors"

Note from the Author or Editor:
"flavour" should read "flavours".

Ask your user *to* enter the recorded time.

Add the word "to".

Note from the Author or Editor:
Third comment on RHS: insert "to" before "enter".

Space missing between sentences: code.You

Note from the Author or Editor:
Add a space as indicated.

Change "brwoser" to "browser".

Note from the Author or Editor:
Change "brwoser" to "browser" in first paragraph.

Phrase "you?ll need to revert one of the options" should be "you?ll need to revert to one of the options."

Note from the Author or Editor:
Add the word "to" after the word "revert" in the hand-written note.

No space between third and fourth sentences: "too.Your" (There is an errata report for this typo on page 371 but not one for page 372.)

Note from the Author or Editor:
Add space as indicated. Also on page 371, same location, same problem.

Change "an new" to "a new."

Note from the Author or Editor:
Replace "an new" with "a new".

The phrase "the column type associated piece of data stored in a row" should be "the column type associated with a piece of data stored in a row."

Note from the Author or Editor:
Add the words "with a" before "piece" in second paragraph.

Change "browse and select your web app?s folder" to "browse to and select your webapp?s folder."

Note from the Author or Editor:
Add the word "to" after "browse".

The phrase "your evey expanding Python toolbox" should be "your ever-expanding Python toolbox." (Two changes: y changed to r and the addition of a hyphen.)

Note from the Author or Editor:
Change "evey " to "ever-" at top of page.

The phrase "it's database API" should be "its database API."

Note from the Author or Editor:
Change "it's database" to "its database".

The timing message would be more grammatically correct if it included the preposition "for", i.e., 'Provide a new timing value for '.

Note from the Author or Editor:
In the pool, add the word "for" to the end of "Provide a new timing value".

The phrase "the same folder your index.html file" should be "the same folder as your index.html file". Add the word "as".

Note from the Author or Editor:
Add the word "as" after "folder" in first paragraph.

There is an extra period in the text. "This is coming along. nicely." should be "This is coming along nicely."

Note from the Author or Editor:
Remove the full-stop (period) after the word "along" at bottom of page.

The phrase "bring ups" should be "brings up".

Note from the Author or Editor:
Change "bring up" to read "brings up".

"This function is a more involved than" should be "This function is more involved than".

Note from the Author or Editor:
Remove the word "a" from the sentence.

The phrase "we might have been designed" should be "we might have designed."

Note from the Author or Editor:
Remove the word "been" from this sentence.

In the last bullet point the phrase "input streams" should be "input/output streams".

Note from the Author or Editor:
Remove the word "input" from before "streams",

The athlete_title string shown on page 280:
athlete_title = which_athlete + ' top 3 times:'
does not match that shown on page 282:
athlete_title = athlete['Name'] + ' (' + athlete['DOB'] + '), top 3 times:'

Note from the Author or Editor:
Yes.. there's an inconsistency here. To be fixed in 2nd edition.

The string for quit_msg contains a typographical single quote.

Note from the Author or Editor:
Change the typographical quotes to be code quotes.

The phrase "You need an data interchange format" should be "You need a data interchange format".

Note from the Author or Editor:
Change Jill's line to read "You need a " not "You need an".

The phrase "your need to generate a new HTML page" should be "you need to generate a new HTML page".

Note from the Author or Editor:
Change "your" to read "you".

The code for testing the u_list function is missing ">>> " and is printed in blue (in the PDF) when it should be black, i.e.,
>>> u_list(['Life of Brian', 'Holy Grail'])

Note from the Author or Editor:
Add the ">>>" prompt to the start of the u_list line and color it in black as per other examples.

The phrase "(H1, H2, H2, and so on)" should be "(H1, H2, H3, and so on)".

Also, there are two periods after the first sentence: "as the default.."

Note from the Author or Editor:
Change "H1, H2, H2, " to read "H1, H2, H3, ".

The error message "File error (put_and_store):" should be "File error (put_to_store):".

Also, this code contains some typographical quotes.

And the code does not handle pickling errors.

Note from the Author or Editor:
"put_and_store" should read "put_to_store".

The phrase "and sent it back to the browser" should be "and send it back to the browser".

Note from the Author or Editor:
Change "sent" to read "send" as indicated.

The phrase "in order to associate it data with its instance" should be "in order to associate its data with its instance."

Note from the Author or Editor:
Change "it data" to "its data" in third from last bullet point.

The test code contains typographical quotes instead of programmer quotes.

Note from the Author or Editor:
Change the typographical quotes in last five lines of code.

The phrase "you can import the into your code" should be "you can import it into your code".

Note from the Author or Editor:
Change "import the into" to "import it into".

The text in the "Sharpen your pencil Solution" contains printers quotes instead of code quotes.

Note from the Author or Editor:
Change all "printers quotes" to be code quotes.

The period after the word created should be a comma.

Note from the Author or Editor:
Replace the "." with a ",".

There is no space between the two sentences on this line: to unpickle.Create an empty list ...

Note from the Author or Editor:
Add a space before the "C".

The word "it's" should be "its" in the sentence ending with "printed to the screen on it's own line."

Note from the Author or Editor:
Yes, this is an issue in the comment (in green) in the code. Requires a new screen-shot from me to fix - it's *not* text.

The underscore which should be between "print" and "lol," i.e., "print_lol" appears underneath the 'n' and 't' in the word "print."

Note from the Author or Editor:
This is *not* an issue in the first printing, but appears to be in the PDF.

As with p. 421, 'predicited' should be 'predicted'

Note from the Author or Editor:
Uuuugugh! There's an error in the code at the bottom of the screenshot. This needs a new screenshot, but the code can be changed to remove the misspelling of "predicted".

"Let's try it with some of data..." should be "Let's try it with some data..."

Note from the Author or Editor:
Remove "of" from the second paragraph.

The note pointing to the line

"class BirthDetailsForm(djangoforms.ModelForm):"

states that the new class inherits from the "djangoforms.Model" class when it should say it inherits from the "djangoforms.ModelForm" class.

Note from the Author or Editor:
Change "djangoforms.Model" to read "djangoforms.ModelForm" in the third hand-written note on this page.

The words "with" and "which" appear to have been swapped:

"...write code with starts a new form, displays the form fields, terminates the form which a submit button..."

Note from the Author or Editor:
In the second paragraph of point 1, change "...write code with starts a new form, displays the form fields, terminates the form which a submit button..."
to read "...write code which starts a new form, displays the form fields, terminates the form with a submit button..."

SKD should be SDK in first line "Download the GAE Python SKD..."

Note from the Author or Editor:
Change "GAE Python SKD" to read "GAE Python SDK".

handers

should read:

handlers

Note from the Author or Editor:
Change "handers" to "handlers" as indicated.

No space after period that ends the sentence in the middle of the line.

"too.Your"

Note from the Author or Editor:
Add a space as indicated.

your think "column,"

should read:

you think "column,"

Note from the Author or Editor:
Change the "your" in the bubble speech box to be "you".

possibly ten of thousands

should read:

possibly tens of thousands

Note from the Author or Editor:
Change "ten of" to "tens of" on third line of text.

Should "not its operator precedence rules" have been "nor its operator precedence rules"? Both are a little syntactically awkward in that sentence.

Note from the Author or Editor:
Change "not its" to "nor its" in second paragraph.

"rather that using"

should read:

"rather than using"

Note from the Author or Editor:
Change "rather that" to "rather than" in last paragraph, last sentence.

"rows or data"

should perhaps read:

"rows of data"

Note from the Author or Editor:
Change "rows or data" to read "rows of data".

"amend you Android app"

should read:

"amend your Android app"

Note from the Author or Editor:
Change "you Android app" to "your Android app" in final paragraph.

"you SQLite database"

should read:

"your SQLite databse"

Note from the Author or Editor:
Change "you" to "your" in first sentence of first paragraph.

"because that have different ID values."

should be:

"because they have different ID values."

Note from the Author or Editor:
Change "that have" to "they have"

connecton

should be:

connection

Note from the Author or Editor:
Change "connecton" to "connection" under the Create entry.

"Take a look a this"

Should be:

"Take a look at this"

Note from the Author or Editor:
Change "a this" to "at this" in the first paragraph.

In a previous errata submission the last line of code was changed to read: "print(json.dumps(athlete))". However, in the updated text the second closing parenthesis is missing.

Note from the Author or Editor:
Add an extra ")" to the last line of code at bottom of page.

A previous errata pointed out that athlete_name should be changed to athlete_id. However, it was accidentally changed to athlete_is instead of athlete_id.

Note from the Author or Editor:
Change "athlete_is" at the start of the 4th last line of code to be "athlete_id".

There is an extraneous colon in the comment which reads: ... "line_spoken": is assigned the string "Is this the right room for an argument?" Remove the the colon.

Note from the Author or Editor:
Within the final hand-written comment, remove the ":" after "line_spoken".

"Understandably, the coach won't let your"
Should read:
"Understandably, the coach won't let you"

Note from the Author or Editor:
Change "your" to "you" in first sentence.

"If you app doesn't run"

Should read:

"If your app doesn't run"

By the way, I'm using the Indian edition if that makes a difference.

Note from the Author or Editor:
Change "you" to "your" in the Relax element.

"Simplty tap" should be "Simply tap"

Note from the Author or Editor:
Change "Simplty" to "Simply" as indicated at end of opening paragraph.

There is already an errata item for this, but it is listed as having been corrected on May 11, 2011. However, it was *not* corrected. (Other typos with that date have been corrected.) The phrase "when your were" should have been changed to "when you were."

Note from the Author or Editor:
Change "your" to "you".

The first sentence in the section under "Yeah, that might just work.", i.e., the sentence that ends with "to perform the nested printing", is missing a period at the end.

Note from the Author or Editor:
Add a period (.) after "nested printing" in middle paragraph.

Typo: "to remember when you actually put it" should be "to remember where you actually put it".

Note from the Author or Editor:
Change "when" to "where" is third answer.

The phrase "or count the number of items" should be "or count of the number of items" (or possibly "or counts the number of items").

Note from the Author or Editor:
Change "count the number" to "counts the number".

Missing apostrophe: "in your (and others) programs" should be "in your (and others') programs".

Note from the Author or Editor:
Change "(and others)" to "(and others')".

Missing apostrophe: "start of your functions code suite" should be "start of your function's code suite".

Note from the Author or Editor:
Change functions to function's in hand-written comment at top-right of page.

The comment: The "for" loop prints each item of the outer loop ONLY. Should read: The "for" loop prints each item of the outer list ONLY. (I.e., change "outer loop" to "outer list".)

Note from the Author or Editor:
Change "outer loop ONLY" to "outer list ONLY".

"Start be..." should be "Start by..."

Note from the Author or Editor:
Change "Start be" to read "Start by" in first paragraph.

Erroneous apostrophe "it's" should be "its".

Note from the Author or Editor:
Change it's to its.

Erroneous apostrophe "it's" should be "its".

Note from the Author or Editor:
Change it's to its.

Erroneous apostrophe: "TypeError's" should be "TypeErrors".

Note from the Author or Editor:
Remove the ' from TypeError's - it should not be there.

In the for loop usage graphic, the one that uses the large font size. In the first box after "for" it is written "target identifer" when it should be "target identifier".

Note from the Author or Editor:
Change "target identifer" to read "target identifier" within the box that follows the large "for" (in the diagram).

"...is based on the one use in the..." : "use" -> "used"

Note from the Author or Editor:
Change "use" to read "used".

You can include code like this in your program. It is also possible to interact with ==> you <== SQLite data from within IDLE?s shell. Whichever option you choose, you are interacting with your database using Python.

Should be "your". Very minor, I know....

Note from the Author or Editor:
Change "you SQLite" to "your SQLite" in second-to-last paragraph.

Change:

"Don't worry; yours in"

to:

"Don't worry, yours is"

Note from the Author or Editor:
Change "yours in" to "yours is" within the bottom-right annotation.

On page 191 in the code block that begins with, "class Athlete," there is a grammatical error. A comment states "# The code to initialize a "Athlete" object," where "a" should be "an."

Note from the Author or Editor:
Change "a Athlete" to "an Athlete" within the comment within the first code block.

On page 116 at the top left corner of the screen it says, "no dumb questiohns," where it should say, "no dumb questions."

Note from the Author or Editor:
Change "questiohns" to "questions" in page title.

Missing "it"

Change this:

becomes such a chore that you would rather find an excuse not to have to do.

to this:

becomes such a chore that you would rather find an excuse not to have to do it.

Note from the Author or Editor:
Change "...not to have to do." to be "...not to have to do so."

you --> your

Note from the Author or Editor:
Change "you" to "your" in first speech bubble.

change print("\t", end=")
to print("\t", end='')

Note from the Author or Editor:
The " associated with the end= is two single quotes, not a double quote. Unfortunately, the font/typeface used in the solution is making this a little confusing, as two single quotes in that typeface looks like a double. Just be sure to use '', not ".

>>> import nester.py
Traceback (most recent call last):
File "<string>", line 1, in <fragment>
builtins.ImportError: No module named py

Therefore Note should read:
Note: don't include the ".py" extension when naming your module.

Note from the Author or Editor:
The annotation is perhaps a little misleading. The key point is that when creating and saving a module, you include the ".py" extension in the file-name. However, when importing the module into a Python program the extension is assumed, so it's an error to include it. Saying "import mymodule" tells Python to find the "mymodule.py" file and import its code.

Of course if *an* different type of...

*an* should be 'a'

Note from the Author or Editor:
Change "an different" to "a different".

it's ignored or *a* error message is ...

*a* should be 'an'

Note from the Author or Editor:
Change "a error" to "an error".

.... operating systems command line

should be system's command line with an apostrophe s

Note from the Author or Editor:
Yes ... the command-line belongs to the OS, so change "system" to read "system's".

These exist in separate files from *you* code and allow...

*you* should be 'your'

Note from the Author or Editor:
Change "you code" to read "your code".

Change "The predicited time running" to "The predicted time running".

Note from the Author or Editor:
Last line of code in screenshot, change "predicited" to "predicted".

Change "strucutre" to "structure".

Note from the Author or Editor:
Change "strucutre" to "structure" in last paragraph.

Change "and he isn?t not logged in" to "and he isn't logged in".

Note from the Author or Editor:
Change "isn't not logged" to "is not logged" in second paragraph.

"As expected, the outout matches that from earlier."

outout should be output

Note from the Author or Editor:
Change "outout" to "output" within first line after screen-shot.

Descriptive text talks about adding a "to_dict" method to the AthleteList class.

However, the sample code to the exercise, given on page 286, actually implements a method called "as_dict".

The name "as_dict" is the one actually present in the chapter8 webapp code downloaded from the HeadFirstPython website.

Note from the Author or Editor:
Page 285 should refer to the method with the name "as_dict", as opposed to "to_dict" (change four times on page 285 and once on page 286).

Change:

"a call to thensend_to_server() function"

to:

"a call to the send_to_server() function"

Note from the Author or Editor:
Change "then" to "the" on second paragraph.

should be 'test_form.py' not 'test-form.py'

Note from the Author or Editor:
On the first line, change "test-form.py" to read "test_form.py" as that's the name used in the screenshot.

'all' should be 'call'

Note from the Author or Editor:
Change the word "all" to "call" within the 3rd line.

'wedapp' should be 'webapp'

Note from the Author or Editor:
Change "wedapp" to "webapp".

"If you make it too hard for your users to enter data into your system, things will likely things break."

Should be "...things will likely break."

Note from the Author or Editor:
Yes, too many "things".

"What?s we need here is some" should be "What we need here is some"

Note from the Author or Editor:
Change "What's we need" to "What we need".

"occured earlier when your were..." should be "when you were"

Note from the Author or Editor:
Change "when your were" to "when you were".

"...have been removed from this COD, but be sure to update your comments..." COD should be CODE

Note from the Author or Editor:
Yes, "cod" should be "code" within the brackets in part 1.

Note box #1 begins: "The code on the RIGHT starts by...". It should say: "The code on the LEFT starts by..."

Note from the Author or Editor:
Yes, "code on the right" should be "code in the left" for point 1.

"In your rush to release the LATES and greatest version of your module" should be "In your rush to release the LATEST and greatest version of your module"

Note from the Author or Editor:
Change "lates" to "latest" in paragraph under the picture of the computer.

Says to use "python3 setup.py sdisk upload" to upload changes to PyPi website.

Should be "python3 setup.py sdist upload".

Note from the Author or Editor:
Yes, that's a minor typo - "sdisk" should be "sdist".