[ 1124295 ] Function's __name__ no longer accessible in restricted mode

[ 1124295 ] Function's __name__ no longer accessible in restricted mode

which I introduced with a bit of mindless copy-paste when making
__name__ writable.  You can't assign to __name__ in restricted mode,
which I'm going to pretend was intentional :)

Closes bug #1124278.

defined.

_some_ user-defined class instance.  That it was also an exception isn't
interesting, but does interfere with Michael Hudson's new-style exception
patch.  This just changes the doctest example, to use an instance of a
non-exception class.

broke the "raise SystemExit(46)" case when doing new-style exceptions,
but I'd much rather have found out here than in test_tempfile (growl).

Licensed to PSF under a Contributor Agreement.

X).

9.

Applies patch #1095802.  Thanks Jack Jansen.

(closes SF bug #1115989)

sanity checks on tzname if HAVE_TZNAME defined.

Closes bug #1096244.  Thanks Gregory Bond.

2.344).

dateTime.iso8601 elements still unmarshal into xmlrpclib.DateTime objects

var == None and var != None
with
var is None and var is not None

and type(var) == int
with
instanceof(var, int)

...as recomended in PEP 8 [1].

* Use +=
* Replace loop logic with str.splitlines equivalent
* Don't use variable names that shadow tuple, list, and str
* Use dict.get instead of equivalent try/except
* Minor loop logic simplications

of a "in" or "not in" test.

Inspired by Skip's idea to recognize the throw-away nature of sequences
in this context and to transform their type to one with better performance.

(John J Lee)

Minor code clarification and simplification.