Added tag 2.0alpha2 for changeset 42f57fdc53a5

Update version numbers so we can tag the current state

Fix problem found when running unittests under Python 2.6: datetime.time.isoformat()
doesn't take a 'sep' argument like datetime.datetime.isoformat() does.

Minor tweaks for compatibility with Python 2.3 and 2.4. The biggest
one is Python 2.3 which doesn't have the Decimal type, use float instead.

Oops, one line that was deleted snuck back in, was harmless though.

Tagged 2.0 alpha 1

A few minor tweaks to the django backend, it seems to pass all Django unittests now!

Get the packaging cleaned up somewhat.

Fix problem where I used the wrong attribute name to access an Exeption's message.

Subclassed bpgsql.Cursor to return rows as tuples instead of lists, to
satisfy Django regressiontests/backends doctests.

Add a Django 1.0 backend that passes a lot, but not all, of the Django unittests.

Reorganize a bit so the Cursor.rowcount attribute can show usable
values for operations other than SELECT, such as INSERT, UPDATE, and DELETE.
This is something the Django unittests are looking for.

Fixed problem preventing Connection class from being subclassed.

Be consistent about the syntax used for raising exceptions, use the modern
style that will be required in Python 3.0

Ran pylint, made changes to help improve code quality.

Rework type conversions to help it come closer to passing Django unittests.
Seems the trick is to convert unicode to utf-8 before doing string escapes.

Took out logging calls, found after doing some profiling that the hit is pretty significant.

Tweak a few minor things to allow it to start to work as a Django 1.0 DB backend.

Cleanup the organization of the code and rename conversion functions to
be more descriptive.

Move the _TypeManager functionality right into the Connection class.
It's easier to deal with, and the Connection class can be subclassed
to extend the new _initialize_types method to add more types.