Log message:
SQLAlchemy release 1.0.14 is now available.

This is the latest release in the 1.0 series which includes a variety of bug \ 
fixes that have accumulated since the last 1.0 release. This release happens to \ 
only feature Core and dialect level changes; none are ORM specific. All \ 
applicable fixes here are also in the 1.1 series, most of which are already \ 
released as of 1.1.0b2. As the 1.1 series moves towards final release, the 1.0 \ 
series will move into "maintenance" mode with very few additional \ 
changes being made.

Log message:
Changes 1.0.13

Fixed bug in “evaluate” strategy of Query.update() and Query.delete() \ 
which would fail to accommodate a bound parameter with a “callable” \ 
value, as which occurs when filtering by a many-to-one equality expression along \ 
a relationship.

Fixed bug whereby the event listeners used for backrefs could be inadvertently \ 
applied multiple times, when using a deep class inheritance hierarchy in \ 
conjunction with mutiple mapper configuration steps.

Fixed bug whereby passing a text() construct to the Query.group_by() method \ 
would raise an error, instead of intepreting the object as a SQL fragment.

Anonymous labeling is applied to a func construct that is passed to \ 
column_property(), so that if the same attribute is referred to as a column \ 
expression twice the names are de-duped, thus avoiding “ambiguous \ 
column” errors. Previously, the .label(None) would need to be applied in \ 
order for the name to be de-anonymized.

Fixed regression appearing in the 1.0 series in ORM loading where the exception \ 
raised for an expected column missing would incorrectly be a NoneType error, \ 
rather than the expected NoSuchColumnError.

Log message:
Release 1.0.12 is a bug fix release resolving a handful of issues reported in \ 
the past few weeks. Primary development continues on the 1.1 series which is \ 
slated for initial releases in the spring.

1.0.12 includes relatively minor fixes, including a revision to a fix made for \ 
version 1.0.10 where we're attempting to report on the "cause" of an \ 
error that is interrupted by a later failure to emit a ROLLBACK on the MySQL \ 
platform. While Python 3 solves this problem using exception chaining and cause \ 
reporting, on Python 2 we emit a warning so that the cause isn't totally \ 
concealed. The condition has been expanded to emit this warning in a much wider \ 
range of scenarios.

Log message:
Release 1.0.11, only twelve days after 1.0.10's release, is expedited to correct \ 
for one ORM-related regression introduced by a 1.0.10 fix; some other fairly \ 
significant bugfixes involving more recently added features, all reported \ 
subsequent to the release of 1.0.10, were also fixed. Fixes include a major \ 
issue in the "baked lazy loader" extension when used as a \ 
systemwide-replacement for lazy loading, a major series of fixes to the \ 
"eager_defaults" mapper persistence option, and a revision to 1.0.10's \ 
fix for a particular polymorphic joined-eager loading issue.

Log message:
Changes 1.0.9:
Release 1.0.9 is a bugfix release, pushing out a collection of mostly small \ 
fixes that have accumulated over the past few months. In particular there is one \ 
small but important fix for users of the latest cx_Oracle library (5.2 or \ 
greater) in conjunction with Python 3 that corrects for an important issue in \ 
correctly detecting the version of this DBAPI and its Unicode behavior.

Log message:
Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
	distfiles/D6.data.ros.gz
	distfiles/cstore0.2.tar.gz
	distfiles/data4.tar.gz
	distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Log message:
Release 1.0.8 comes almost immediately after 1.0.7, as a new issue involving the \ 
connection pool has been identified and fixed which impacts any application that \ 
relies upon consistent behavior of the .info dictionary on a connection that is \ 
undergoing reconnect attempts. Applications and libraries which make use of \ 
connection pool event handlers may benefit from this release, as it repairs the \ 
behavior of the .info dictionary and reduces the likelihood of stale connections \ 
being passed to the "checkout" handler.

Log message:
Release 0.9.9 is a large maintenance release featuring 30 changes, mostly bug \ 
fixes. A handful of modest feature adds are also present, including new Core \ 
features for SQLite, Postgresql, and new API features to provide better control \ 
of transaction isolation level when using the ORM.

Log message:
Update py-sqlalchemy to 0.9.8.

Changes since 0.9.4: bug fixes in preparation for 1.0.0. See full changelog:

http://docs.sqlalchemy.org/en/latest/changelog/changelog_09.html

Log message:
Updated to latest stable release, 0.9.4. This was required, because some
newer py-sqlalchemy-* packages won't work with our archive version. Changes
are too numerous to list here. Check:
http://docs.sqlalchemy.org/en/latest/changelog/