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 "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
PDF |
Page xiii
Note with footprints |
Although perhaps not trivial, tt?s not too
probably should by
Although perhaps not trivial, it?s not too
Note from the Author or Editor: Thanks. We'll take care of these kinds of typos during the copyedit.
|
Chris Schuermyer |
Jul 09, 2013 |
|
PDF |
Page 6
Python tip |
We?ll work though
should be
We?ll work through
Note from the Author or Editor: We'll take care of this during the copyedit. Thanks!
|
Chris Schuermyer |
Jul 09, 2013 |
|
PDF |
Page 7
Tip |
'worth nothing' should be 'worth noting'
Note from the Author or Editor: We'll fix these things in the copyedit, which is coming up soon when a dedicated copyeditor will go through the language with a fine-tooth comb. Thank you for pointing them out, though.
|
Chris Schuermyer |
Jul 09, 2013 |
|
ePub |
Page 18
3rd paragraph |
so take a moment to crate one and, then, review Twitter's liberal
crate instead of create
comma, usage, on a par, with Mein Kampf,
Not sure about the page number on ePub in iBook on iPad. There is a number 18 to the left, but I'm not sure if that is at the top or the bottom of the page.
The book format is a bit of an anachronism with this sort of publishing.
Note from the Author or Editor: Thanks very much for the feedback (but keep in mind that the book hasn't bee copyedited yet - a good copyeditor will help me sort out all of the misspellings (which are not that easy to find in my docbook editor, believe it or not) and with my excessive, use, of commas :)
I'll update this in my docbook so it'll be corrected for the next interim update.
I hope you're enjoying it so far. Please keep the feedback coming (but don't wear yourself out with grammar at this point - I'm sure there's lots of slip ups here and there.)
|
Anonymous |
May 13, 2013 |
|
PDF |
Page 327
code |
In the code it says
follower_ids = get_friends_followers_ids(twitter_api, fid, friends_limit=-1, followers_limit=limit)
but it didn't work for me, I had to change fid into user_id=fid
Note from the Author or Editor: Thanks. You are right that this is a bug in the current PDF and GitHub code. I just fixed it on GitHub and the fix will be reflected in the next Early Access update, which should come out next week. I really appreciate you reporting this issue. Feel free to report other issues (both code related and discussion related) directly on GitHub if that's easier for you.
|
synth |
Jul 25, 2013 |
|