x/yview_scroll/moveto.)

and it opens the source.

Other stuff so the PyShell window can be resurrected from the Windows menu.

Create a simple Windows menu.  (Imperfect when Untitled windows exist.)
Add wakeup() method: deiconify, raise, focus.

reliably; check return value of vsprintf().

broken; it asked for the current thread state when there was none.
Fixed by using the saved event_tstate.

	from a.b import c
	import a . b

Add a label at the bottom showing the exception info.

Features: text editor with syntax coloring and undo;
subclassed into interactive Python shell which adds history.

thread state of the thread calling mainloop() (or another event
handling function) rather than the thread state of the function that
created the client data structure.

canonical definition of extend() is very similar to append() except
that the former doesn't list-ify the argument!

something in the latest win342 build).

object that implements the buffer interface, but requires a buffer
that contains 8-bit character data.  Greg Stein.

that (as far as the data type is concerned!) this is character data.

Add a new member to the PyBufferProcs struct, bf_getcharbuffer.  For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below.  Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then).  If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)

As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags.  In 1.5.1 and before,
this slot was always zero.  In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1.  The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.

Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.