Will backport myself.

(closes SF bug #1008998)

(closes SF bug #1093173)

(closes SF bug #853800; markup adjusted)

(closes SF patch #1084092; modified per comments in SF)

(closes SF patch #1031233; modified)

(closes SF patch #1104868)

(closes SF patch #1094815)

2. Restore use of set_indentation_params(), was dead code since
   Autoindent.py was merged into EditorWindow.py.
3. Make usetabs, indentwidth, tabwidth, context_use_ps1 instance vars
   and set in EditorWindow.__init__()
4. In PyShell.__init__() set usetabs, indentwidth and context_use_ps1
   explicitly (config() is eliminated).
5. Add Tabnanny check when Module is Run/F5, not just when Checked.
6. Discourage using an indent width other than 8 when using tabs to
   indent Python code.

M EditorWindow.py
M NEWS.txt
M PyShell.py
M ScriptBinding.py

inscrutable READ_TIMESTAMP.

erroring out.

Don't print the same (host, port) tuple thrice when debugging, but first print
(host, port), then (ip, port) and then the error message.

this allows for better handling of newline characters in quoted fields (and
hopefully resolves Bug 967934).

the changes.

user error messages (otherwise difficult to do without instrumenting
the source).

to floats.

PyNumber_Check, rather than trying to convert to a float.  Reimplemented
writer - now raises exceptions when it sees a quotechar but neither
doublequote or escapechar are set. Doublequote results are now more
consistent (eg, single quote should generate """", rather than "",
which is ambiguous).

gets).