this allows for better handling of newline characters in quoted fields (and
hopefully resolves Bug 967934).

the changes.

user error messages (otherwise difficult to do without instrumenting
the source).

to floats.

PyNumber_Check, rather than trying to convert to a float.  Reimplemented
writer - now raises exceptions when it sees a quotechar but neither
doublequote or escapechar are set. Doublequote results are now more
consistent (eg, single quote should generate """", rather than "",
which is ambiguous).

gets).

Clarified that the returned object is file-like rather than an actual file.

when this limit is reached. Limit defaults to 128k, and is changed
by module set_field_limit() method. Previously, an unmatched quote
character could result in the entire file being read into the field
buffer, potentially exhausting virtual memory.

only contains instances of the dialect type, we can refer directly to the
dialect instances rather than creating new ones. In other words, if the
dialect comes from the registry, and we apply no further modifications,
the reader/writer can use the dialect object directly.

dialect type (which has a better idea of what is and isn't valid).

was done because we were previously performing validation of the dialect
from python, but this is now down within the C module. Also, the method
we were using to detect classes did not work with new-style classes.

record objects of internal dialect type, rather than instances of
python objects.

it for all failures, potentially masking other exceptions).

same as None.

rather than using PyString_Check/PyUnicode_Check.

profile.help() point at the library reference instead of profile.doc.

writer objects (other GC infrastructure already in place).

left in stream).

a delimiter. Previously, the 'network location' (<authority> in RFC 2396) would
become 'www.example.com?query=spam', while RFC 2396 does not allow a '?' in
<authority>. See bug #548176 for further discussion.

removing some duplication and gaining some flexibility in the process.

there's no need to subclass OptionParser.

* Document hasFeature(), createDocument(), CreateDocumentType(),
  hasAttribute(), hasAttributeNS().

* In the documentation for createDocument(), it is now stated that the Python
  DOM API allows implementations to forego creation of the document element
  child node, if no namespace and local name arguments are given. (This
  possibility is left open and unaddressed in the W3C spec).

* Addition by me: use 'name' rather than 'attname', for consistency with the
  DOM specification and the Python DOM API implementation.