Rather than introduce new logic, took the approach of making the message
itself more general.

(Suggested by Michael Hudson.)

repr(66.6) == "66.6", so doubt that the claimed output has ever been seen.
Changed it to 66.25 everywhere, and manually verified that the new claimed
output is correct.

request.  Tim says that "correct 'fuzzy' comparison of floats cannot
be automated."  (The motivation behind adding the new option
was verifying interactive examples in Python's latex documentation;
several such examples use numbers that don't print consistently on
different platforms.)

* Have groupby() be careful about decreffing structure members.

the expected output to match corresponding number literals in the
actual output if their values are equal (to ten digits of precision).

the proper path directories for compiling extension modules.

Added a clarifying line to the docs.

fact that compiler.ast.Function now takes a "decorators" argument.

the htons() function.

- Fixed indentation for a verbatim block

but not entirely obvious use case.

Also, add a testcase.

Formerly, the list_extend() code used several local variables to remember
its state across iterations.  Since an iteration could call arbitrary
Python code, it was possible for the list state to be changed.  The new
code uses dynamic structure references instead of C locals.  So, they
are always up-to-date.

After list_resize() is called, its size has been updated but the new
cells are filled with NULLs.  These needed to be filled before arbitrary
iteration code was called; otherwise, that code could attempt to modify
a list that was in a semi-invalid state.  The solution was to change
the ob->size field back to a value reflecting the actual number of valid
cells.

by factoring out the common prefix (the delimiter).

Backported to 2.3.