Hello community, here is the log from the commit of package python-alembic for openSUSE:Factory checked in at 2013-04-26 07:43:28 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-alembic (Old) and /work/SRC/openSUSE:Factory/.python-alembic.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-alembic", Maintainer is "" Changes: -------- --- /work/SRC/openSUSE:Factory/python-alembic/python-alembic.changes 2013-03-08 09:39:21.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.python-alembic.new/python-alembic.changes 2013-04-26 07:43:30.000000000 +0200 @@ -1,0 +2,42 @@ +Sun Apr 14 15:53:22 UTC 2013 - [email protected] + +- Update to version 0.5.0 + + added version_table_schema argument to EnvironmentContext.configure(), + complements the version_table argument to set an optional remote schema + for the version table. + + added output_encoding option to EnvironmentContext.configure(), used with --sql + mode to apply an encoding to the output stream. + + added Operations.create_primary_key() operation, will genenerate an + ADD CONSTRAINT for a primary key. + + upgrade and downgrade commands will list the first line of the docstring + out next to the version number. + + added –head-only option to “alembic current”, will print current version + plus the symbol “(head)” if this version is the head or not. + + the rendering of any construct during autogenerate can be customized, in particular + to allow special rendering for user-defined column, constraint subclasses, using new render + _item argument to EnvironmentContext.configure(). + + fix format of RENAME for table that includes schema with Postgresql; the + schema name shouldn’t be in the “TO” field. + + fix bug whereby double quoting would be applied to target column name during an sp_rename operation. + + fix transactional_ddl flag for SQLite, MySQL dialects set to False. MySQL doesn’t support it, + SQLite does but current pysqlite driver does not. + + fix Autogenerate will render additional table keyword arguments like “mysql_engine” and + others within op.create_table(). + + fix bug whereby create_index() would include in the constraint columns that are added + to all Table objects using events, externally to the generation of the constraint. + This is the same issue that was fixed for unique constraints in version 0.3.2. + + fix worked around a backwards-incompatible regression in Python3.3 regarding argparse; + running “alembic” with no arguments now yields an informative error in py3.3 as with + all previous versions. + + fix host of argument name changes within migration operations for consistency. Keyword + arguments will continue to work on the old name for backwards compatibility, however required + positional arguments will not: + * Operations.alter_column() - name -> new_column_name - old name will work for backwards compatibility. + * Operations.create_index() - tablename -> table_name - argument is positional. + * Operations.drop_index() - tablename -> table_name - old name will work for backwards compatibility. + * Operations.drop_constraint() - tablename -> table_name - argument is positional. + * Operations.drop_constraint() - type -> type_ - old name will work for backwards compatibility + + SQLAlchemy 0.6 is no longer supported by Alembic - minimum version is 0.7.3, full support is as of 0.7.9. +- Initial python3 support + +------------------------------------------------------------------- New Changes file: --- /dev/null 2013-04-05 00:01:41.916011506 +0200 +++ /work/SRC/openSUSE:Factory/.python-alembic.new/python3-alembic.changes 2013-04-26 07:43:35.000000000 +0200 @@ -0,0 +1,198 @@ +------------------------------------------------------------------- +Thu Apr 25 12:35:26 UTC 2013 - [email protected] + +- Ship hg exported tarball until 0.6.0 is released. Fixes Python-3.3 + compatibility issues + +------------------------------------------------------------------- +Tue Apr 23 08:16:36 UTC 2013 - [email protected] + +- Dont't buildrequire argparse, it is part of the Python3 standard library +- Run 2to3 to actually generate py3 code +- Fix unittests, one test fails on encoding, drop that for now + +------------------------------------------------------------------- +Sun Apr 14 15:53:22 UTC 2013 - [email protected] + +- Update to version 0.5.0 + + added version_table_schema argument to EnvironmentContext.configure(), + complements the version_table argument to set an optional remote schema + for the version table. + + added output_encoding option to EnvironmentContext.configure(), used with --sql + mode to apply an encoding to the output stream. + + added Operations.create_primary_key() operation, will genenerate an + ADD CONSTRAINT for a primary key. + + upgrade and downgrade commands will list the first line of the docstring + out next to the version number. + + added –head-only option to “alembic current”, will print current version + plus the symbol “(head)” if this version is the head or not. + + the rendering of any construct during autogenerate can be customized, in particular + to allow special rendering for user-defined column, constraint subclasses, using new render + _item argument to EnvironmentContext.configure(). + + fix format of RENAME for table that includes schema with Postgresql; the + schema name shouldn’t be in the “TO” field. + + fix bug whereby double quoting would be applied to target column name during an sp_rename operation. + + fix transactional_ddl flag for SQLite, MySQL dialects set to False. MySQL doesn’t support it, + SQLite does but current pysqlite driver does not. + + fix Autogenerate will render additional table keyword arguments like “mysql_engine” and + others within op.create_table(). + + fix bug whereby create_index() would include in the constraint columns that are added + to all Table objects using events, externally to the generation of the constraint. + This is the same issue that was fixed for unique constraints in version 0.3.2. + + fix worked around a backwards-incompatible regression in Python3.3 regarding argparse; + running “alembic” with no arguments now yields an informative error in py3.3 as with + all previous versions. + + fix host of argument name changes within migration operations for consistency. Keyword + arguments will continue to work on the old name for backwards compatibility, however required + positional arguments will not: + * Operations.alter_column() - name -> new_column_name - old name will work for backwards compatibility. + * Operations.create_index() - tablename -> table_name - argument is positional. + * Operations.drop_index() - tablename -> table_name - old name will work for backwards compatibility. + * Operations.drop_constraint() - tablename -> table_name - argument is positional. + * Operations.drop_constraint() - type -> type_ - old name will work for backwards compatibility + + SQLAlchemy 0.6 is no longer supported by Alembic - minimum version is 0.7.3, full support is as of 0.7.9. +- Initial python3 support + +------------------------------------------------------------------- +Thu Jan 17 12:31:01 UTC 2013 - [email protected] + +- Set nose version requirement + +------------------------------------------------------------------- +Mon Jan 14 16:02:38 UTC 2013 - [email protected] + +- Update to version 0.4.2: + + Fixed bug where autogenerate would fail if a Column to be added to + a table made use of the ".key" paramter. + + Added a workaround to setup.py to prevent "NoneType" error from + occuring when "setup.py test" is run. + + Added a README.unittests with instructions for running the test + suite fully. +- Changes from version 0.4.1: + + Added support for autogenerate render of ForeignKeyConstraint + options onupdate, ondelete, initially, and deferred. + + Explicit error message describing the case when downgrade --sql + is used without specifying specific start/end versions. + + Fixed the minute component in file_template + which returned the month part of the create date. + +------------------------------------------------------------------- +Mon Jan 14 16:00:10 UTC 2013 - [email protected] + +- Disable testsuite on SLE + +------------------------------------------------------------------- +Fri Nov 23 10:43:42 UTC 2012 - [email protected] + +- Update to version 0.4.0: + + [feature] Support for tables in alternate schemas + has been added fully to all operations, as well as to + the autogenerate feature. When using autogenerate, + specifying the flag include_schemas=True to + Environment.configure() will also cause autogenerate + to scan all schemas located by Inspector.get_schema_names(), + which is supported by *some* (but not all) + SQLAlchemy dialects including Postgresql. + *Enormous* thanks to Bruno Binet for a huge effort + in implementing as well as writing tests. #33. + + [feature] The command line runner has been organized + into a reusable CommandLine object, so that other + front-ends can re-use the argument parsing built + in. #70 + + [feature] Added "stdout" option to Config, provides + control over where the "print" output of commands like + "history", "init", "current" etc. are sent. #43 + + [bug] Fixed the "multidb" template which was badly out + of date. It now generates revision files using + the configuration to determine the different + upgrade_<xyz>() methods needed as well, instead of + needing to hardcode these. Huge thanks to + BryceLohr for doing the heavy lifting here. #71 + + [bug] Fixed the regexp that was checking for .py files + in the version directory to allow any .py file through. + Previously it was doing some kind of defensive checking, + probably from some early notions of how this directory + works, that was prohibiting various filename patterns + such as those which begin with numbers. #72 + + [bug] Fixed MySQL rendering for server_default which + didn't work if the server_default was a generated + SQL expression. Courtesy Moriyoshi Koizumi. + + [feature] Added support for alteration of MySQL + columns that have AUTO_INCREMENT, as well as enabling + this flag. Courtesy Moriyoshi Koizumi. + +------------------------------------------------------------------- +Wed Jun 6 12:13:48 UTC 2012 - [email protected] + +- Update to version 0.3.4: + + [bug] Fixed command-line bug introduced by the + "revision_environment" feature. +- Changes from version 0.3.3: + + [feature] New config argument + "revision_environment=true", causes env.py to + be run unconditionally when the "revision" command + is run, to support script.py.mako templates with + dependencies on custom "template_args". + + [feature] Added "template_args" option to configure() + so that an env.py can add additional arguments + to the template context when running the + "revision" command. This requires either --autogenerate + or the configuration directive "revision_environment=true". + + [bug] Added "type" argument to op.drop_constraint(), + and implemented full constraint drop support for + MySQL. CHECK and undefined raise an error. + MySQL needs the constraint type + in order to emit a DROP CONSTRAINT. #44 + + [feature] Added version_table argument to + EnvironmentContext.configure(), allowing for the + configuration of the version table name. #34 + + [feature] Added support for "relative" migration + identifiers, i.e. "alembic upgrade +2", + "alembic downgrade -1". Courtesy + Atsushi Odagiri for this feature. + + [bug] Fixed bug whereby directories inside of + the template directories, such as __pycache__ + on Pypy, would mistakenly be interpreted as + files which are part of the template. #49 + +------------------------------------------------------------------- +Wed May 23 12:55:05 UTC 2012 - [email protected] + +- Update to version 0.3.2: + + [feature] Basic support for Oracle added + + [feature] Added support for UniqueConstraint in autogenerate + + [bug] Fixed support of schema-qualified ForeignKey target in column alter operations, + + [bug] Fixed bug whereby create_unique_constraint() would include in + the constraint columns that are added to all Table objects using events, + externally to the generation of the constraint. +- Changes from version 0.3.1: + + [bug] bulk_insert() fixes: + 1. bulk_insert() operation was not working most likely since the 0.2 series + when used with an engine + 2. Repaired bulk_insert() to complete when used against a lower-case-t + table and executing with only one set of parameters, working + around SQLAlchemy bug #2461 in this regard. + 3. bulk_insert() uses "inline=True" so that phrases like RETURNING and + such don't get invoked for single-row bulk inserts. + 4. bulk_insert() will check that you're passing a list of dictionaries + in, raises TypeError if not detected. +- Changes from version 0.3.0: + + [general] The focus of 0.3 is to clean up and more fully document the + public API of Alembic, including better accessors on the MigrationContext + and ScriptDirectory objects. Methods that are not considered to be + public on these objects have been underscored, and methods which should + be public have been cleaned up and documented, including: + MigrationContext.get_current_revision() + ScriptDirectory.iterate_revisions() + ScriptDirectory.get_current_head() + ScriptDirectory.get_heads() + ScriptDirectory.get_base() + ScriptDirectory.generate_revision() + + [feature] Added a bit of autogenerate to the public API in the form of + the function alembic.autogenerate.compare_metadata. + +------------------------------------------------------------------- +Wed Mar 7 08:25:45 UTC 2012 - [email protected] + +- Initial version ++++ 1 more lines (skipped) ++++ between /dev/null ++++ and /work/SRC/openSUSE:Factory/.python-alembic.new/python3-alembic.changes Old: ---- alembic-0.4.2.tar.gz New: ---- alembic-0.5.0.tar.gz python3-alembic.changes python3-alembic.spec zzzeek-alembic-5c05656a0f81.zip ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-alembic.spec ++++++ --- /var/tmp/diff_new_pack.8x8u8b/_old 2013-04-26 07:43:41.000000000 +0200 +++ /var/tmp/diff_new_pack.8x8u8b/_new 2013-04-26 07:43:41.000000000 +0200 @@ -17,7 +17,7 @@ Name: python-alembic -Version: 0.4.2 +Version: 0.5.0 Release: 0 Url: http://bitbucket.org/zzzeek/alembic Summary: A database migration tool for SQLAlchemy @@ -25,14 +25,16 @@ Group: Development/Languages/Python Source: http://pypi.python.org/packages/source/a/alembic/alembic-%{version}.tar.gz BuildRoot: %{_tmppath}/%{name}-%{version}-build +BuildRequires: python-devel +BuildRequires: python-distribute +# Test requirements: BuildRequires: python-Mako BuildRequires: python-SQLAlchemy >= 0.7.5 BuildRequires: python-argparse -BuildRequires: python-devel -BuildRequires: python-distribute BuildRequires: python-nose >= 0.11 Requires: python-Mako Requires: python-SQLAlchemy >= 0.7.5 +Requires: python-argparse %if 0%{?suse_version} && 0%{?suse_version} <= 1110 %{!?python_sitelib: %global python_sitelib %(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")} %else @@ -63,7 +65,7 @@ python setup.py install --prefix=%{_prefix} --root=%{buildroot} #NOTE(saschpe): Check back -%if 0%{?suse_version} >= 1110 +%if 0%{?suse_version} >= 1130 %check nosetests %endif ++++++ python3-alembic.spec ++++++ # # spec file for package python3-alembic # # Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # Name: python3-alembic Version: 0.5.0 Release: 0 Url: http://bitbucket.org/zzzeek/alembic Summary: A database migration tool for SQLAlchemy License: MIT Group: Development/Languages/Python #Source: http://pypi.python.org/packages/source/a/alembic/alembic-%{version}.tar.gz #NOTE(saschpe): Temporarily use hg version until 0.6.0 is released. # To fix Python-3 compat issues Source: zzzeek-alembic-5c05656a0f81.zip BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: python3-devel BuildRequires: python3-distribute BuildRequires: unzip # Test requirements: BuildRequires: python3-Mako BuildRequires: python3-SQLAlchemy >= 0.7.5 BuildRequires: python3-nose >= 0.11 Requires: python3-Mako Requires: python3-SQLAlchemy >= 0.7.5 BuildArch: noarch %description Alembic is a new database migrations tool, written by the author of SQLAlchemy <http://www.sqlalchemy.org>. A migrations tool offers the following functionality: * Can emit ALTER statements to a database in order to change the structure of tables and other constructs * Provides a system whereby "migration scripts" may be constructed; each script indicates a particular series of steps that can "upgrade" a target database to a new version, and optionally a series of steps that can "downgrade" similarly, doing the same steps in reverse. * Allows the scripts to execute in some sequential manner. %prep #%%setup -q -n alembic-%{version} %setup -q -n zzzeek-alembic-5c05656a0f81 mv docs html && rm -rf html/build %build python3 setup.py build %install python3 setup.py install --prefix=%{_prefix} --root=%{buildroot} # Avoid conflict with alembic python2 package mv %{buildroot}/%{_bindir}/alembic %{buildroot}/%{_bindir}/alembic-%{py3_ver} %check nosetests-%{py3_ver} %files %defattr(-,root,root,-) %doc CHANGES LICENSE README.rst html %{_bindir}/alembic-%{py3_ver} %{python3_sitelib}/* %changelog ++++++ alembic-0.4.2.tar.gz -> alembic-0.5.0.tar.gz ++++++ ++++ 4278 lines of diff (skipped) -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
