The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
| Version |
Location |
Description |
Submitted By |
Corrected |
| Printed |
Page N/A
N/A |
Note from the author:
I keep a separate errata list, which may or may
not intersect with the list kept here over time.
Please see the following web page for my errata
and updates lists:
http://www.rmi.net/~lutz/lp3e-updates.html<p>
Given that there is a newer edition of this book,
chances are good that I will be maintaining errata
on my own list, instead of the redundant set here.
Thanks,
--Mark Lutz
|
Mark Lutz
 |
|
| Printed |
Page xxxvii
3rd bullet item, bad backquotes formatting |
In the Python 3.0 changes section, this bullet item describes the demise of the
backquotes expression, but seems to show this using straight quotes.
Backquotes are formatted properly later, on pages 96 and 136.
|
Anonymous |
Jul 2008 |
| Printed |
Page xxxix
6th bullet item from page bottom, missing comma |
Also in the Python 3.0 section, a comma in program code was deleted, also somewhere in the
production process. The "except name value" should read as "except name, value" as described
later in the book (see pages 583, 594, 612, and 614).
|
Anonymous |
Jul 2008 |
| Printed |
Page 5
on the first line |
Python mplements
should be:
Python implements
|
Anonymous |
Jul 2008 |
| Printed |
Page 31
4th paragraph |
The Vaults of Parnassus web site http://www.vex.net/parnassus/ does not exist as far as I can tell. I see all kinds of writing about it on a Google search and the address on page 31 which I have reiterated above doesn't get me anywhere but shows a plethora of sites which use the words vaults of parnassus in links but when I click on them I get some CIA style message: Forbidden
You don't have permission to access /parnassus/ on this server.
I was at this for over an hour and found no such site as that on page 31 - http://www.vex.net/parnassus/.
Note from the Author or Editor:
The Vaults of Parnassus, mentioned on page 31 of the 3rd and prior Edition of this book, is no more. It is an ex-website; it has ceased to be; (insert the rest of the Dead Parrot sketch here...). We removed it from the new edition of the book, but it was still valid when the prior edition came online. Today, use PyPI or search Google for extensions.
|
Dave Rose |
|
| Printed |
Page 72
first code block |
...error text omittted...
should be:
...error text omitted...
|
Anonymous |
Jul 2008 |
| Printed |
Page 132
Tip at top of page, 3rd line |
No space between "of" and "small" in the line:
"...mutable sequence ofsmall integers..."
|
Anonymous |
Jul 2008 |
| Printed |
Page 175
2nd full code block, 2nd comment |
# This works: can chage mutables inside
should be:
# This works: can change mutables inside
|
Anonymous |
Jul 2008 |
| Printed |
Page 226
first sentence on page, |
In the very first sentence on this page, the "rwords" should be "words"
|
Anonymous |
Jul 2008 |
| Printed |
Page 233
sidebar "Why You Will Care: print and stdout", 3rd paragraph |
...it doesn't care what SYS.SYTDOUT is, only...
should be:
...it doesn't care what SYS.STDOUT is, only...
|
Anonymous |
Jul 2008 |
| Printed |
Page 277
Answer #7 |
"A comfy couch" was never one of the weapons employed by the Spanish Inquisition—"a comfy chair" would be more accurate.
Note from the Author or Editor:
Yep -- I transposed furniture here somehow. I'm not sure this qualifies as a tecnical mistake (and it's not exactly going to make the Mars Rover run into a boulder or anything...), but it merits a patch in future printings.
|
Eric Knibbe |
|
| Printed |
Page 305
paragraph 4, sentence 2 |
Sentence 2 of paragraph 4 on this page incorrectly states that the * operator, and hence the times
function "will work on numbers (performing multiplication), two strings or a string and a number
(performing repetition), or any other combination of objects supporting the expected interface". This
is incorrect -- * works on two numbers, or a string and a number, but not on two strings. That is,
string * string is not a valid operation.
In fact, if you pass two strings into the times function, it generates an exception, the point of the
next paragraph in the book.
|
Anonymous |
Jul 2008 |
| PDF |
Page 322
1st code sample |
Code sample
>>>def maker(N):
... def action(X):
... return X ** N
...return action
...
does not compile, indentation on "return action" is wrong.
Note from the Author or Editor:
This is a known errata, and has been fixed in later
printings of the book.
Please see the following page, where I keep track of
book corrections, and post general notes about both
the book and recent changes in Python:
http://www.rmi.net/~lutz/lp3e-updates.html
|
Juan Manuel Tamayo |
|
| Printed |
Page 325
3rd example code block |
The line "return acts" should be indented one level.
Note from the Author or Editor:
This is a known errata, and has been fixed in later
printings of the book.
Please see the following page, where I keep track of
book corrections, and post general notes about both
the book and recent changes in Python:
http://www.rmi.net/~lutz/lp3e-updates.html
|
Eric Knibbe |
|
| Printed |
Page 456
in "Class Method Calls", transposed variable names |
In 2 spots of this section, I transposed the I1/I2 and C2/C3 variable names. The typo should be
apparent from the surrounding text, but it could also be a bit confusing given the introductory
nature of this section. Specifically: in this section's very first sentence, "C2.w" should be "C3.w";
in the last sentence of this section's second paragraph, "C3.w(I1)" should be "C3.w(I2)."
|
Anonymous |
Jul 2008 |
| Printed |
Page 507
2nd line from bottom of page, typo in code comment |
There is a case typo in the commented-out line here. It should read "#print C.m.X", with the
uppercase
|
Anonymous |
Jul 2008 |
| Printed |
Page 591
1st paragraph lines[-2] |
It reads:
"Mixing from into the same statement ...."
but shoud be:
"Mixing finally into the same statement ...."
Note from the Author or Editor:
This is a known errata, and has been fixed in later
printings of the book.
Please see the following page, where I keep track of
book corrections, and post general notes about both
the book and recent changes in Python:
http://www.rmi.net/~lutz/lp3e-updates.html
|
Anonymous |
|
