refactor the copying of file data. new: shutil.copyfileobj(fsrc, fdst)

debug_cycle(), and don't cast the pointer to a long.  Neither needs
the literal `0x' prefix as %p automatically inserts this (on Linux at
least).

Adds caching and reverts back the 'return' to 'exit()' in
AC_TRY_RUN as recommended by the Autoconf documentation.

rest of the Python C code: space between "if", "for" and "(", no space
between "(", ")" and function call parameters, etc.

so we get better error messages.

<nascheme@enme.ucalgary.ca>, markup & minor revisions from Fred
Drake.

Patch by Thomas Wouters <thomas@xs4all.net> with small changes of mine
(in main(), use return instead of exit).

Closes patch #100832

Patch by Thomas Wouters <thomas@xs4all.net> with small changes of mine
(in main(), use return instead of exit).

Closes patch #100832
(but I can't assign it to myself, nor close it -- sorry)

fix to the code to make it behave like the module docstring.

* There was no error reported if the .read() method returns a non-string
* If read() returned too much data, the buffer would be overflowed causing a
  core dump
* Used strncpy, not memcpy, which seems incorrect if there are embedded \0s.
* The args and bytes objects were leaked

	The first two warnings seem harmless enough,
	but the last one looks like a potential bug: an
	uninitialized int is returned on error. (I also
	ended up reformatting some of the code,
	because it was hard to read.)

Changed parameter in getsockaddrlen from unsigned to socklen_t.

mac-specific functions to have a PyMac_ name.

consensus where it should go).

- ANSIfication step 3: enable "require prototypes" flags. Still lots of warnings, mainly on init routines and bgen stuff.

header files included.

Added a declaration of fileno() if we use GUSI. Not sure whether it should go here or in pyport.h really...

    use PyString_AS_STRING macro on local string object
    when resizing string, make sure resized string will always be big enough
    split string containing error message across two lines
add test to string_tests that causes resizing

Comment change only.

Update the "in" / "not in" description to accomodate the current use
of the __contains__() discipline.  This patch also incorporates
suggestions from Marc-Andre Lemburg <mal@lemburg.com>, minor markup
revisions from Fred Drake, and some rewording of the first affected
paragraph (also from Fred).

Closes SourceForge patch #100831.

used for indentation related errors.  This patch includes Ping's
improvements for indentation-related error messages.

Closes SourceForge patches #100734 and #100856.

change eliminate to delete (-d)

elements (since the table was pretty screwed up); this is how it is done
elsewhere in the manual.

I could use some help creating descriptions of the specific error
identifiers (input conditions that lead to each error, etc.).

The Compare close contains a close method that checks to see if there
is any unconsumed data in the Compare instance; i.e. if the canonical
output file contains more data than was produced by the current test
run. This method was never called, allowing differences to go
undetected.

Fix is to call close after the test is run (after __import__)

output/test_long and output/test_popen2 needed trivial changes
output/test_select contained lots of text, but test_select.py produced
    no output

Change a cast, intialize a local, and make some sprintf() format strings
type-appropriate (add the "l" to "%d").

Closes SourceForge patch #100737.

the documentation; the cases `? foo' and `! foo' failed.