Here's a "keyword" module which, in the spirit of "token.py", updates
the list of keywords automatically from a source file (in this case,
"graminit.c" seemed like a reasonable choice, easier than "Grammar/Grammar").

You get "kwlist", a sorted list of keywords; "kwdict", a dictionary
mapping each keyword to 1; and "iskeyword", a function which tells
you if a given string happens to be a keyword.

This makes it possible to write 1L<<1000000, memory permitting.

was some locking code in this file that needed it...

last variable to which a floating point expression is assigned.  The
macro passes its address to a dummy function so that the optimizer
can't delay calculating its value until after the macro.

(it should return a list of tuples, not a list of lists).

	Create the .pyo files corresponding to the .py and .pyc files as
	well.

	to use for the cached module code object.

Add prototypes for parsestr() and parsestrplus() (unrelated, but
seemed to make sense.)

errors in initializing the dictionary.

recognized by the code generator and code generation for the test and
the subsequent suite is suppressed.

One must write *exactly* ``if __debug__:'' or ``elif __debug__:'' --
no parentheses or operators must be present, or the optimization is
not carried through.  Whitespace doesn't matter.  Other uses of
__debug__ will find __debug__ defined as 0 or 1 in the __builtin__
module.

This is done for backward compatibility with Python 1.4.

this mode, all tests are run in verbose mode with their output to
stdout.  No comparing of output is done.

of day, day of week, and season.

Fix the weekday predictions -- these seemed to be all bogus.  The new
predictions seem to correspond with strftime() on Solaris and IRIX, so
I believe they are correct.

Get rid of the test for non-standard format %C returning "the same as
date(1)".  This is hard to do reliably without opening a pipe to date,
and moreover, on IRIX 6.2, %C yields the Century.  So we use that
instead.  (We don't complain about this in non-verbose mode anyway.)

integer overflow in << operator.

it anyway.

Fred: sorry, I hadn't checked these changes in.  This should fix your
tracebacks!