Accepting request 303943 from home:benoit_monin:branches:devel:languages:python

- update to 0.7.5.post2
- set minimum version for SQLAlchemy to 0.7.6
- use update-alternatives for alembic binary
- always run the tests when building the package

OBS-URL: https://build.opensuse.org/request/show/303943
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-alembic?expand=0&rev=36

python-alembic.changes

@@ -1,3 +1,49 @@
+-------------------------------------------------------------------
+Sat Apr 25 15:53:02 UTC 2015 - benoit.monin@gmx.fr
+
+- update to 0.7.5.post2:
+  * Added a new feature Config.attributes, to help with the use
+    case of sharing state such as engines and connections on the
+    outside with a series of Alembic API calls; also added a new
+    cookbook section to describe this simple but pretty important
+    use case.
+  * The format of the default env.py script has been refined a bit;
+    it now uses context managers not only for the scope of the
+    transaction, but also for connectivity from the starting
+    engine. The engine is also now called a “connectable” in
+    support of the use case of an external connection being passed
+    in.
+  * Added support for “alembic stamp” to work when given “heads” as
+    an argument, when multiple heads are present.
+  * The --autogenerate option is not valid when used in conjunction
+    with “offline” mode, e.g. --sql. This now raises a
+    CommandError, rather than failing more deeply later on. Pull
+    request courtesy Johannes Erdfelt.
+  * Fixed bug where the mssql DROP COLUMN directive failed to
+    include modifiers such as “schema” when emitting the DDL.
+  * Postgresql “functional” indexes are necessarily skipped from
+    the autogenerate process, as the SQLAlchemy backend currently
+    does not support reflection of these structures. A warning is
+    emitted both from the SQLAlchemy backend as well as from the
+    Alembic backend for Postgresql when such an index is detected.
+  * Fixed bug where MySQL backend would report dropped unique
+    indexes and/or constraints as both at the same time. This is
+    because MySQL doesn’t actually have a “unique constraint”
+    construct that reports differently than a “unique index”, so it
+    is present in both lists. The net effect though is that the
+    MySQL backend will report a dropped unique index/constraint as
+    an index in cases where the object was first created as a
+    unique constraint, if no other information is available to make
+    the decision. This differs from other backends like Postgresql
+    which can report on unique constraints and unique indexes
+    separately.
+  * Fixed bug where using a partial revision identifier as the
+    “starting revision” in --sql mode in a downgrade operation
+    would fail to resolve properly.
+- set minimum version for SQLAlchemy to 0.7.6
+- use update-alternatives for alembic binary
+- always run the tests when building the package
+
 -------------------------------------------------------------------
 Thu Feb  5 15:04:20 UTC 2015 - tbechtold@suse.com