iteritems and itervalues' previous object were both an iterator *and* and
iterable.  The tests expected an iterator but were given an iterable.

Should the 2to3 conversion for iter(values|items|keys) change the code to
``iter(dict.keys())`` to be more compatible?

There are some methods in minidom that return dict.keys() directly.  There were
left alone since the tests passed without touching them, but it might be
prudent to just wrap them in a 'list' call to be safe for people expecting a
list.

Clearly this is not the right way to fix this; UserDict and MixinDict
ought to be redesigned with the new dict API in mind.  But I'm not
claiming to be in charge of library redesign, I only want zero failing
tests.

(PEP 3106 requires subset comparisons too, those will come later if someone
really wants them. :-)

  and .keys(), .items(), .values() return dict views.

The dict views aren't fully functional yet; in particular, they can't
be compared to sets yet.  but they are useful as "iterator wells".

There are still 27 failing unit tests; I expect that many of these
have fairly trivial fixes, but there are so many, I could use help.

(Not for dict_values, where it can't be done faster than
the default implementation which just iterates the elements.)

One was a modified line that was echoed in an exception;
the other two were softspace problems, fixed clumsily but effectively.

a different feature with the same name).
The change to test_doctest.txt reduces the doctest failures to 3.

old print would suppress the softspace after \t.