integer overflow in << operator.

it anyway.

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

nonzero.

on-line list of same.

- Changed FragLoader.h to CodeFragments.h
- Removed Desk.h

- Changed FragLoader.h to CodeFragments.h
- Removed Desk.h
- Regenerated bgen modules from new universal headers
- Changed some of the s# in PyArg_ParseTuple to m# (unfortunately:
  this should have been a different commit)

and there is already a similar demo in Demo/classes/Complex.py.

Lee is wondering whether to withdraw his patchs.  Sigh.

extensively in test_strftime.py anyway).

and there, etc. These projects are still CW10.

  in importdl.c (I had just one crash too many with a static python
  importing a dynamic module)
- On powerpc, enable USE_CACHE_ALIGNED with a linesize of 32 bytes.

Also grandly renamed.

Here's the new interface:

When WITH_READLINE is defined, two functions are defined:

  - PyOS_GnuReadline (what used to be my_readline() with WITH_READLINE)
  - PyOS_ReadlineInit (for Dave Ascher)

Always, these functions are defined:

  - PyOS_StdioReadline (what used to be my_readline() without WITH_READLINE)
  - PyOS_Readline (the interface used by tokenizer.c and [raw_]input().

There's a global function pointer PyOS_ReadlineFunctionPointer,
initialized to NULL.  When PyOS_Readline finds this to be NULL, it
sets it to either PyOS_GnuReadline or PyOS_StdioReadline depending on
which one makes more sense (i.e. it uses GNU only if it is defined
*and* stdin is indeed a tty device).

An embedding program that has its own wishes can set the function
pointer to a function of its own design.  It should take a char*
prompt argument (which may be NULL) and return a string *ending in a
\n character* -- or "" for EOF or NULL for a user interrupt.

--Guido van Rossum (home page: http://www.python.org/~guido/)