head 1.9; access; symbols pkgsrc-2023Q4:1.8.0.18 pkgsrc-2023Q4-base:1.8 pkgsrc-2023Q3:1.8.0.16 pkgsrc-2023Q3-base:1.8 pkgsrc-2023Q2:1.8.0.14 pkgsrc-2023Q2-base:1.8 pkgsrc-2023Q1:1.8.0.12 pkgsrc-2023Q1-base:1.8 pkgsrc-2022Q4:1.8.0.10 pkgsrc-2022Q4-base:1.8 pkgsrc-2022Q3:1.8.0.8 pkgsrc-2022Q3-base:1.8 pkgsrc-2022Q2:1.8.0.6 pkgsrc-2022Q2-base:1.8 pkgsrc-2022Q1:1.8.0.4 pkgsrc-2022Q1-base:1.8 pkgsrc-2021Q4:1.8.0.2 pkgsrc-2021Q4-base:1.8 pkgsrc-2021Q3:1.7.0.6 pkgsrc-2021Q3-base:1.7 pkgsrc-2021Q2:1.7.0.4 pkgsrc-2021Q2-base:1.7 pkgsrc-2021Q1:1.7.0.2 pkgsrc-2021Q1-base:1.7 pkgsrc-2020Q4:1.6.0.8 pkgsrc-2020Q4-base:1.6 pkgsrc-2020Q3:1.6.0.6 pkgsrc-2020Q3-base:1.6 pkgsrc-2020Q2:1.6.0.4 pkgsrc-2020Q2-base:1.6 pkgsrc-2020Q1:1.6.0.2 pkgsrc-2020Q1-base:1.6 pkgsrc-2019Q4:1.5.0.4 pkgsrc-2019Q4-base:1.5 pkgsrc-2019Q3:1.4.0.2 pkgsrc-2019Q3-base:1.4 pkgsrc-2019Q2:1.3.0.6 pkgsrc-2019Q2-base:1.3 pkgsrc-2019Q1:1.3.0.4 pkgsrc-2019Q1-base:1.3 pkgsrc-2018Q4:1.3.0.2 pkgsrc-2018Q4-base:1.3 pkgsrc-2018Q3:1.2.0.6 pkgsrc-2018Q3-base:1.2 pkgsrc-2018Q2:1.2.0.4 pkgsrc-2018Q2-base:1.2 pkgsrc-2018Q1:1.2.0.2 pkgsrc-2018Q1-base:1.2 pkgsrc-2017Q4:1.1.0.6 pkgsrc-2017Q4-base:1.1 pkgsrc-2017Q3:1.1.0.4 pkgsrc-2017Q3-base:1.1; locks; strict; comment @# @; 1.9 date 2024.03.06.20.27.46; author wiz; state Exp; branches; next 1.8; commitid hm1iVuEk6wOFJ81F; 1.8 date 2021.11.14.18.42.37; author adam; state Exp; branches; next 1.7; commitid ruLT0srhK69dfNgD; 1.7 date 2021.01.26.11.20.07; author adam; state Exp; branches; next 1.6; commitid KPtWLAzciPu4beFC; 1.6 date 2020.02.16.21.11.41; author adam; state Exp; branches; next 1.5; commitid qPyTZOSOsTk7yWWB; 1.5 date 2019.10.10.18.26.53; author adam; state Exp; branches; next 1.4; commitid aIjPNCW9J5pDMlGB; 1.4 date 2019.08.28.06.37.38; author adam; state Exp; branches; next 1.3; commitid zkrtYjf060fZeLAB; 1.3 date 2018.10.18.10.15.18; author adam; state Exp; branches; next 1.2; commitid ByzsqjmxWVZqxqWA; 1.2 date 2018.01.18.09.18.06; author adam; state Exp; branches; next 1.1; commitid E58gfcScf4K30lnA; 1.1 date 2017.09.17.04.00.15; author minskim; state Exp; branches; next ; commitid Qwg2j7ulotfPbv7A; desc @@ 1.9 log @py-alembic: update to 1.13.1. .. changelog:: :version: 1.13.1 :released: December 20, 2023 .. change:: :tags: bug, autogenerate :tickets: 1337 Fixed :class:`.Rewriter` so that more than two instances could be chained together correctly, also allowing multiple ``process_revision_directives`` callables to be chained. Pull request courtesy zrotceh. .. change:: :tags: bug, environment :tickets: 1369 Fixed issue where the method :meth:`.EnvironmentContext.get_x_argument` using the :paramref:`.EnvironmentContext.get_x_argument.as_dictionary` parameter would fail if an argument key were passed on the command line as a name alone, that is, without an equal sign ``=`` or a value. Behavior is repaired where this condition is detected and will return a blank string for the given key, consistent with the behavior where the ``=`` sign is present and no value. Pull request courtesy Iuri de Silvio. .. change:: :tags: bug, autogenerate :tickets: 1370 Fixed issue where the "unique" flag of an ``Index`` would not be maintained when generating downgrade migrations. Pull request courtesy Iuri de Silvio. .. change:: :tags: bug, versioning :tickets: 1373 Fixed bug in versioning model where a downgrade across a revision with two down revisions with one down revision depending on the other, would produce an erroneous state in the alembic_version table, making upgrades impossible without manually repairing the table. Thanks much to Saif Hakim for the great work on this. .. change:: :tags: bug, typing :tickets: 1377 Updated pep-484 typing to pass mypy "strict" mode, however including per-module qualifications for specific typing elements not yet complete. This allows us to catch specific typing issues that have been ongoing such as import symbols not properly exported. .. changelog:: :version: 1.13.0 :released: December 1, 2023 .. change:: :tags: bug, commands :tickets: 1234 Fixed issue where the ``alembic check`` command did not function correctly with upgrade structures that have multiple, top-level elements, as are generated from the "multi-env" environment template. Pull request courtesy Neil Williams. .. change:: :tags: usecase, operations :tickets: 1323 Updated logic introduced in :ticket:`151` to allow ``if_exists`` and ``if_not_exists`` on index operations also on SQLAlchemy 1.4 series. Previously this feature was mistakenly requiring the 2.0 series. .. change:: :tags: usecase :tickets: 1339 Replaced ``python-dateutil`` with the standard library module `zoneinfo `_. This module was added in Python 3.9, so previous version will been to install the backport of it, available by installing the ``backports.zoneinfo`` library. The ``alembic[tz]`` option has been updated accordingly. .. change:: :tags: installation, changed :tickets: 1359 Alembic 1.13 now supports Python 3.8 and above. .. change:: :tags: bug, autogenerate :tickets: 1361 Fixed autogenerate issue where ``create_table_comment()`` and ``drop_table_comment()`` rendering in a batch table modify would include the "table" and "schema" arguments, which are not accepted in batch as these are already part of the top level block. .. change:: :tags: bug, postgresql :tickets: 1321, 1327, 1356 Additional fixes to PostgreSQL expression index compare feature. The compare now correctly accommodates casts and differences in spacing. Added detection logic for operation clauses inside the expression, skipping the compare of these expressions. To accommodate these changes the logic for the comparison of the indexes and unique constraints was moved to the dialect implementation, allowing greater flexibility. .. changelog:: :version: 1.12.1 :released: October 26, 2023 .. change:: :tags: bug, autogenerate, regression :tickets: 1329 Fixed regression caused by :ticket:`879` released in 1.7.0 where the ".info" dictionary of ``Table`` would not render in autogenerate create table statements. This can be useful for custom create table DDL rendering schemes so it is restored. .. change:: :tags: bug, typing :tickets: 1325 Improved typing in the :paramref:`.EnvironmentContext.configure.process_revision_directives` callable to better indicate that the passed-in type is :class:`.MigrationScript`, not the :class:`.MigrationOperation` base class, and added typing to the example at :ref:`cookbook_no_empty_migrations` to illustrate. .. change:: :tags: bug, operations :tickets: 1335 Repaired :class:`.ExecuteSQLOp` so that it can participate in "diff" operations; while this object is typically not present in a reflected operation stream, custom hooks may be adding this construct where it needs to have the correct ``to_diff_tuple()`` method. Pull request courtesy Sebastian Bayer. .. change:: :tags: typing, bug :tickets: 1058, 1277 Improved the ``op.execute()`` method to correctly accept the ``Executable`` type that is the same which is used in SQLAlchemy ``Connection.execute()``. Pull request courtesy Mihail Milushev. .. change:: :tags: typing, bug :tickets: 930 Improve typing of the revision parameter in various command functions. .. change:: :tags: typing, bug :tickets: 1266 Properly type the :paramref:`.Operations.create_check_constraint.condition` parameter of :meth:`.Operations.create_check_constraint` to accept boolean expressions. .. change:: :tags: bug, postgresql :tickets: 1322 Fixed autogen render issue where expressions inside of indexes for PG need to be double-parenthesized, meaning a single parens must be present within the generated ``text()`` construct. .. change:: :tags: usecase :tickets: 1304 Alembic now accommodates for Sequence and Identity that support dialect kwargs. This is a change that will be added to SQLAlchemy v2.1. .. changelog:: :version: 1.12.0 :released: August 31, 2023 .. change:: :tags: bug, operations :tickets: 1300 Added support for ``op.drop_constraint()`` to support PostgreSQL ``ExcludeConstraint`` objects, as well as other constraint-like objects that may be present in third party dialects, by resolving the ``type_`` parameter to be ``None`` for this case. Autogenerate has also been enhanced to exclude the ``type_`` parameter from rendering within this command when ``type_`` is ``None``. Pull request courtesy David Hills. .. change:: :tags: bug, commands :tickets: 1299 Fixed issue where the ``revision_environment`` directive in ``alembic.ini`` was ignored by the ``alembic merge`` command, leading to issues when other configurational elements depend upon ``env.py`` being invoked within the command. .. change:: :tags: bug, autogenerate :tickets: 1302 Fixed issue where the ``ForeignKeyConstraint.match`` parameter would not be rendered in autogenerated migrations. Pull request courtesy Asib Kamalsada. .. change:: :tags: usecase, autogenerate :tickets: 1248 Change the default value of :paramref:`.EnvironmentContext.configure.compare_type` to ``True``. As Alembic's autogenerate for types was dramatically improved in version 1.4 released in 2020, the type comparison feature is now much more reliable so is now enabled by default. .. change:: :tags: feature, autogenerate :tickets: 1275 Added new feature to the "code formatter" function which allows standalone executable tools to be run against code, without going through the Python interpreter. Known as the ``exec`` runner, it complements the existing ``console_scripts`` runner by allowing non-Python tools such as ``ruff`` to be used. Pull request courtesy Mihail Milushev. .. seealso:: :ref:`post_write_hooks_config` .. changelog:: :version: 1.11.3 :released: August 16, 2023 .. change:: :tags: bug, autogenerate, postgresql :tickets: 1270 Improved autogenerate compare of expression based indexes on PostgreSQL to produce fewer wrong detections. .. change:: :tags: bug, autogenerate :tickets: 1291 Fixed issue with ``NULLS NOT DISTINCT`` detection in postgresql that would keep detecting changes in the index or unique constraint. .. change:: :tags: bug, commands :tickets: 1273 Added ``encoding="locale"`` setting to the use of Python's ``ConfigParser.read()``, so that a warning is not generated when using the recently added Python feature ``PYTHONWARNDEFAULTENCODING`` specified in :pep:`597`. The encoding is passed as the ``"locale"`` string under Python 3.10 and greater, which indicates that the system-level locale should be used, as was the case already here. Pull request courtesy Kevin Kirsche. .. changelog:: :version: 1.11.2 :released: August 4, 2023 .. change:: :tags: usecase, typing :tickets: 1253 Added typing to the default script mako templates. .. change:: :tags: usecase, autogenerate :tickets: 1248 Added support in autogenerate for ``NULLS NOT DISTINCT`` in the PostgreSQL dialect. .. change:: :tags: bug :tickets: 1261 Fixed format string logged when running a post write hook Pull request curtesy of Mathieu Défosse. .. change:: :tags: feature, operations :tickets: 151 Added parameters if_exists and if_not_exists for index operations. Pull request courtesy of Max Adrian. .. changelog:: :version: 1.11.1 :released: May 17, 2023 .. change:: :tags: bug, autogenerate, regression :tickets: 1243, 1245 As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been :ref:`clarified ` in the documentation), change :ticket:`1130` modified calling signatures for most operations to consider all optional keyword parameters to be keyword-only arguments, to match what was always documented and generated by autogenerate. However, two of these changes were identified as possibly problematic without a more formal deprecation warning being emitted which were the ``table_name`` parameter to :meth:`.Operations.drop_index`, which was generated positionally by autogenerate prior to version 0.6.3 released in 2014, and ``type_`` in :meth:`.Operations.drop_constraint` and :meth:`.BatchOperations.drop_constraint`, which was documented positionally in one example in the batch documentation. These two signatures have been restored to allow those particular parameters to be passed positionally. A future change will include formal deprecation paths (with warnings) for these arguments where they will again become keyword-only in a future "Significant Minor" release. .. change:: :tags: bug, typing :tickets: 1246 Fixed typing use of :class:`~sqlalchemy.schema.Column` and other generic SQLAlchemy classes. .. change:: :tags: bug, typing, regression :tickets: 1244 Restored the output type of :meth:`.Config.get_section` to include ``Dict[str, str]`` as a potential return type, which had been changed to immutable ``Mapping[str, str]``. When a section is returned and the default is not used, a mutable dictionary is returned. .. changelog:: :version: 1.11.0 :released: May 15, 2023 .. change:: :tags: bug, batch :tickets: 1237 Added placeholder classes for :class:`~.sqla.Computed` and :class:`~.sqla.Identity` when older 1.x SQLAlchemy versions are in use, namely prior to SQLAlchemy 1.3.11 when the :class:`~.sqla.Computed` construct was introduced. Previously these were set to None, however this could cause issues with certain codepaths that were using ``isinstance()`` such as one within "batch mode". .. change:: :tags: bug, batch :tickets: 1221 Correctly pass previously ignored arguments ``insert_before`` and ``insert_after`` in ``batch_alter_column`` .. change:: :tags: change, py3k :tickets: 1130 Argument signatures of Alembic operations now enforce keyword-only arguments as passed as keyword and not positionally, such as :paramref:`.Operations.create_table.schema`, :paramref:`.Operations.add_column.type_`, etc. .. change:: :tags: bug, postgresql :tickets: 1230 Fix autogenerate issue with PostgreSQL :class:`.ExcludeConstraint` that included sqlalchemy functions. The function text was previously rendered as a plain string without surrounding with ``text()``. .. change:: :tags: bug, mysql, regression :tickets: 1240 Fixed regression caused by :ticket:`1166` released in version 1.10.0 which caused MySQL unique constraints with multiple columns to not compare correctly within autogenerate, due to different sorting rules on unique constraints vs. indexes, which in MySQL are shared constructs. .. change:: :tags: misc :tickets: 1220 Update code snippets within docstrings to use ``black`` code formatting. Pull request courtesy of James Addison. .. change:: :tags: bug, typing :tickets: 1093 Updated stub generator script to also add stubs method definitions for the :class:`.Operations` class and the :class:`.BatchOperations` class obtained from :meth:`.Operations.batch_alter_table`. As part of this change, the class hierarchy of :class:`.Operations` and :class:`.BatchOperations` has been rearranged on top of a common base class :class:`.AbstractOperations` in order to type correctly, as :class:`.BatchOperations` uses different method signatures for operations than :class:`.Operations`. .. change:: :tags: bug, typing Repaired the return signatures for :class:`.Operations` that mostly return ``None``, and were erroneously referring to ``Optional[Table]`` in many cases. .. change:: :tags: usecase, commands :tickets: 1109 Added quiet option to the command line, using the ``-q/--quiet`` option. This flag will prevent alembic from logging anything to stdout. .. change:: :tags: bug, autogenerate :tickets: 1178 Modified the autogenerate implementation for comparing "server default" values from user-defined metadata to not apply any quoting to the value before comparing it to the server-reported default, except for within dialect-specific routines as needed. This change will affect the format of the server default as passed to the :paramref:`.EnvironmentContext.configure.compare_server_default` hook, as well as for third party dialects that implement a custom ``compare_server_default`` hook in their alembic impl, to be passed "as is" and not including additional quoting. Custom implementations which rely on this quoting should adjust their approach based on observed formatting. .. change:: :tags: bug, api, autogenerate :tickets: 1235 Fixed issue where :func:`.autogenerate.render_python_code` function did not provide a default value for the ``user_module_prefix`` variable, leading to ``NoneType`` errors when autogenerate structures included user-defined types. Added new parameter :paramref:`.autogenerate.render_python_code.user_module_prefix` to allow this to be set as well as to default to ``None``. Pull request courtesy tangkikodo. .. change:: :tags: usecase, asyncio :tickets: 1231 Added :meth:`.AbstractOperations.run_async` to the operation module to allow running async functions in the ``upgrade`` or ``downgrade`` migration function when running alembic using an async dialect. This function will receive as first argument an :class:`~sqlalchemy.ext.asyncio.AsyncConnection` sharing the transaction used in the migration context. .. changelog:: :version: 1.10.4 :released: April 24, 2023 .. change:: :tags: postgresql, autogenerate, feature :tickets: 1213 Added support for autogenerate comparison of indexes on PostgreSQL which include SQL sort option, such as ``ASC`` or ``NULLS FIRST``. The sort options are correctly detected only when defined using the sqlalchemy modifier functions, such as ``asc()`` or ``nulls_first()``, or the equivalent methods. Passing sort options inside the ``postgresql_ops`` dict is not supported. .. change:: :tags: bug, operations :tickets: 1215 Fixed issue where using a directive such as ``op.create_foreign_key()`` to create a self-referential constraint on a single table where the same column were present on both sides (e.g. within a composite foreign key) would produce an error under SQLAlchemy 2.0 and a warning under SQLAlchemy 1.4 indicating that a duplicate column were being added to a table. .. changelog:: :version: 1.10.3 :released: April 5, 2023 .. change:: :tags: bug, typing :tickets: 1191, 1201 Fixed various typing issues observed with pyright, including issues involving the combination of :class:`.Function` and :meth:`.MigrationContext.begin_transaction`. .. change:: :tags: bug, autogenerate :tickets: 1212 Fixed error raised by alembic when running autogenerate after removing a function based index. .. changelog:: :version: 1.10.2 :released: March 8, 2023 .. change:: :tags: bug, ops :tickets: 1196 Fixed regression where Alembic would not run with older SQLAlchemy 1.3 versions prior to 1.3.24 due to a missing symbol. Workarounds have been applied for older 1.3 versions. .. changelog:: :version: 1.10.1 :released: March 6, 2023 .. change:: :tags: bug, postgresql :tickets: 1184 Fixed issue regarding PostgreSQL :class:`.ExcludeConstraint`, where constraint elements which made use of :func:`.literal_column` could not be rendered for autogenerate. Additionally, using SQLAlchemy 2.0.5 or greater, :func:`.text()` constructs are also supported within PostgreSQL :class:`.ExcludeConstraint` objects for autogenerate render. Pull request courtesy Jan Katins. .. change:: :tags: bug, batch, regression :tickets: 1195 Fixed regression for 1.10.0 where :class:`.Constraint` objects were suddenly required to have non-None name fields when using batch mode, which was not previously a requirement. .. changelog:: :version: 1.10.0 :released: March 5, 2023 .. change:: :tags: bug, autogenerate :tickets: 1166 Fixed issue in index detection where autogenerate change detection would consider indexes with the same columns but with different order as equal, while in general they are not equivalent in how a database will use them. .. change:: :tags: feature, revisioning :tickets: 760 Recursive traversal of revision files in a particular revision directory is now supported, by indicating ``recursive_version_locations = true`` in alembic.ini. Pull request courtesy ostr00000. .. change:: :tags: bug, autogenerate, sqlite :tickets: 1165 Fixed issue where indexes on SQLite which include SQL expressions would not compare correctly, generating false positives under autogenerate. These indexes are now skipped, generating a warning, in the same way that expression-based indexes on PostgreSQL are skipped and generate warnings when SQLAlchemy 1.x installations are in use. Note that reflection of SQLite expression-based indexes continues to not yet be supported under SQLAlchemy 2.0, even though PostgreSQL expression-based indexes have now been implemented. .. change:: :tags: bug, mssql :tickets: 1187 Properly escape constraint name on SQL Server when dropping a column while specifying ``mssql_drop_default=True`` or ``mssql_drop_check=True`` or ``mssql_drop_foreign_key=True``. .. change:: :tags: usecase, autogenerate, postgresql Added support for autogenerate comparison of indexes on PostgreSQL which include SQL expressions, when using SQLAlchemy 2.0; the previous warning that such indexes were skipped are removed when the new functionality is in use. When using SQLAlchemy versions prior to the 2.0 series, the indexes continue to be skipped with a warning. .. changelog:: :version: 1.9.4 :released: February 16, 2023 .. change:: :tags: bug, mssql :tickets: 1177 Ongoing fixes for SQL Server server default comparisons under autogenerate, adjusting for SQL Server's collapsing of whitespace between SQL function arguments when reporting on a function-based server default, as well as its arbitrary addition of parenthesis within arguments; the approach has now been made more aggressive by stripping the two default strings to compare of all whitespace, parenthesis, and quoting characters. .. change:: :tags: bug, postgresql Fixed PostgreSQL server default comparison to handle SQL expressions sent as ``text()`` constructs, such as ``text("substring('name', 1, 3)")``, which previously would raise errors when attempting to run a server-based comparison. .. change:: :tags: bug, autogenerate :tickets: 1180 Removed a mis-use of the :paramref:`.EnvironmentContext.configure.render_item` callable where the "server_default" renderer would be erroneously used within the server default comparison process, which is working against SQL expressions, not Python code. .. change:: :tags: bug, commands Fixed regression introduced in 1.7.0 where the "config" object passed to the template context when running the :func:`.merge` command programmatically failed to be correctly populated. Pull request courtesy Brendan Gann. .. changelog:: :version: 1.9.3 :released: February 7, 2023 .. change:: :tags: bug, autogenerate :tickets: 1167 Fixed issue where rendering of user-defined types that then went onto use the ``.with_variant()`` method would fail to render, if using SQLAlchemy 2.0's version of variants. .. changelog:: :version: 1.9.2 :released: January 14, 2023 .. change:: :tags: bug, typing :tickets: 1146, 1147 Fixed typing definitions for :meth:`.EnvironmentContext.get_x_argument`. Typing stubs are now generated for overloaded proxied methods such as :meth:`.EnvironmentContext.get_x_argument`. .. change:: :tags: bug, autogenerate :tickets: 1152 Fixed regression caused by :ticket:`1145` where the string transformations applied to server defaults caused expressions such as ``(getdate())`` to no longer compare as equivalent on SQL Server, others. .. changelog:: :version: 1.9.1 :released: December 23, 2022 .. change:: :tags: bug, autogenerate :tickets: 1145 Fixed issue where server default compare would not work for string defaults that contained backslashes, due to mis-rendering of these values when comparing their contents. .. change:: :tags: bug, oracle Implemented basic server default comparison for the Oracle backend; previously, Oracle's formatting of reflected defaults prevented any matches from occurring. .. change:: :tags: bug, sqlite Adjusted SQLite's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side. .. change:: :tags: bug, mssql Adjusted SQL Server's compare server default implementation to better handle defaults with or without parens around them, from both the reflected and the local metadata side. .. changelog:: :version: 1.9.0 :released: December 15, 2022 .. change:: :tags: feature, commands :tickets: 724 Added new Alembic command ``alembic check``. This performs the widely requested feature of running an "autogenerate" comparison between the current database and the :class:`.MetaData` that's currently set up for autogenerate, returning an error code if the two do not match, based on current autogenerate settings. Pull request courtesy Nathan Louie. .. seealso:: :ref:`alembic_check` .. change:: :tags: bug, tests Fixed issue in tox.ini file where changes in the tox 4.0 series to the format of "passenv" caused tox to not function correctly, in particular raising an error as of tox 4.0.6. .. change:: :tags: bug, typing :tickets: 1110 Fixed typing issue where :paramref:`.revision.process_revision_directives` was not fully typed; additionally ensured all ``Callable`` and ``Dict`` arguments to :meth:`.EnvironmentContext.configure` include parameters in the typing declaration. Additionally updated the codebase for Mypy 0.990 compliance. .. changelog:: :version: 1.8.1 :released: July 13, 2022 .. change:: :tags: bug, sqlite :tickets: 1065 Fixed bug where the SQLite implementation of :meth:`.Operations.rename_table` would render an explicit schema name for both the old and new table name, which while is the standard ALTER syntax, is not accepted by SQLite's syntax which doesn't support a rename across schemas. In particular, the syntax issue would prevent batch mode from working for SQLite databases that made use of attached databases (which are treated as "schemas" in SQLAlchemy). .. change:: :tags: bug, batch :tickets: 1021 Added an error raise for the condition where :meth:`.Operations.batch_alter_table` is used in ``--sql`` mode, where the operation requires table reflection, as is the case when running against SQLite without giving it a fixed ``Table`` object. Previously the operation would fail with an internal error. To get a "move and copy" batch operation as a SQL script without connecting to a database, a ``Table`` object should be passed to the :paramref:`.Operations.batch_alter_table.copy_from` parameter so that reflection may be skipped. .. changelog:: :version: 1.8.0 :released: May 31, 2022 .. change:: :tags: feature, typing :tickets: 764 :pep:`484` typing annotations have been added to the ``env.py`` and revision template files within migration templates. Pull request by Nikita Sobolev. .. change:: :tags: usecase, operations :tickets: 1037 The ``op.drop_table()`` operation directive will now trigger the ``before_drop()`` and ``after_drop()`` DDL event hooks at the table level, which is similar to how the ``before_create()`` and ``after_create()`` hooks are triggered by the ``op.create_table()`` directive. Note that as ``op.drop_table()`` accepts only a table name and optional schema name, the ``Table`` object received by the event will not have any information within it other than the table name and schema name. .. change:: :tags: installation, changed :tickets: 1025 Alembic 1.8 now supports Python 3.7 and above. .. change:: :tags: changed, environment :tickets: 987 The "Pylons" environment template has been removed as of Alembic 1.8. This template was based on the very old pre-Pyramid Pylons web framework which has been long superseded by Pyramid. .. change:: :tags: bug, revisioning :tickets: 1026 Fixed issue where a downgrade using a relative revision would fail in case of multiple branches with a single effectively head due to interdependencies between revisions. .. change:: :tags: usecase, commands :tickets: 1027 Added new token ``epoch`` to the ``file_template`` option, which will populate the integer epoch as determined by ``int(create_date.timestamp())``. Pull request courtesy Caio Carvalho. .. change:: :tags: bug, batch :tickets: 1034 Fixed issue in batch mode where CREATE INDEX would not use a new column name in the case of a column rename. @ text @@@comment $NetBSD$ bin/alembic-${PYVERSSUFFIX} ${PYSITELIB}/${WHEEL_INFODIR}/LICENSE ${PYSITELIB}/${WHEEL_INFODIR}/METADATA ${PYSITELIB}/${WHEEL_INFODIR}/RECORD ${PYSITELIB}/${WHEEL_INFODIR}/WHEEL ${PYSITELIB}/${WHEEL_INFODIR}/entry_points.txt ${PYSITELIB}/${WHEEL_INFODIR}/top_level.txt ${PYSITELIB}/alembic/__init__.py ${PYSITELIB}/alembic/__init__.pyc ${PYSITELIB}/alembic/__init__.pyo ${PYSITELIB}/alembic/__main__.py ${PYSITELIB}/alembic/__main__.pyc ${PYSITELIB}/alembic/__main__.pyo ${PYSITELIB}/alembic/autogenerate/__init__.py ${PYSITELIB}/alembic/autogenerate/__init__.pyc ${PYSITELIB}/alembic/autogenerate/__init__.pyo ${PYSITELIB}/alembic/autogenerate/api.py ${PYSITELIB}/alembic/autogenerate/api.pyc ${PYSITELIB}/alembic/autogenerate/api.pyo ${PYSITELIB}/alembic/autogenerate/compare.py ${PYSITELIB}/alembic/autogenerate/compare.pyc ${PYSITELIB}/alembic/autogenerate/compare.pyo ${PYSITELIB}/alembic/autogenerate/render.py ${PYSITELIB}/alembic/autogenerate/render.pyc ${PYSITELIB}/alembic/autogenerate/render.pyo ${PYSITELIB}/alembic/autogenerate/rewriter.py ${PYSITELIB}/alembic/autogenerate/rewriter.pyc ${PYSITELIB}/alembic/autogenerate/rewriter.pyo ${PYSITELIB}/alembic/command.py ${PYSITELIB}/alembic/command.pyc ${PYSITELIB}/alembic/command.pyo ${PYSITELIB}/alembic/config.py ${PYSITELIB}/alembic/config.pyc ${PYSITELIB}/alembic/config.pyo ${PYSITELIB}/alembic/context.py ${PYSITELIB}/alembic/context.pyc ${PYSITELIB}/alembic/context.pyi ${PYSITELIB}/alembic/context.pyo ${PYSITELIB}/alembic/ddl/__init__.py ${PYSITELIB}/alembic/ddl/__init__.pyc ${PYSITELIB}/alembic/ddl/__init__.pyo ${PYSITELIB}/alembic/ddl/_autogen.py ${PYSITELIB}/alembic/ddl/_autogen.pyc ${PYSITELIB}/alembic/ddl/_autogen.pyo ${PYSITELIB}/alembic/ddl/base.py ${PYSITELIB}/alembic/ddl/base.pyc ${PYSITELIB}/alembic/ddl/base.pyo ${PYSITELIB}/alembic/ddl/impl.py ${PYSITELIB}/alembic/ddl/impl.pyc ${PYSITELIB}/alembic/ddl/impl.pyo ${PYSITELIB}/alembic/ddl/mssql.py ${PYSITELIB}/alembic/ddl/mssql.pyc ${PYSITELIB}/alembic/ddl/mssql.pyo ${PYSITELIB}/alembic/ddl/mysql.py ${PYSITELIB}/alembic/ddl/mysql.pyc ${PYSITELIB}/alembic/ddl/mysql.pyo ${PYSITELIB}/alembic/ddl/oracle.py ${PYSITELIB}/alembic/ddl/oracle.pyc ${PYSITELIB}/alembic/ddl/oracle.pyo ${PYSITELIB}/alembic/ddl/postgresql.py ${PYSITELIB}/alembic/ddl/postgresql.pyc ${PYSITELIB}/alembic/ddl/postgresql.pyo ${PYSITELIB}/alembic/ddl/sqlite.py ${PYSITELIB}/alembic/ddl/sqlite.pyc ${PYSITELIB}/alembic/ddl/sqlite.pyo ${PYSITELIB}/alembic/environment.py ${PYSITELIB}/alembic/environment.pyc ${PYSITELIB}/alembic/environment.pyo ${PYSITELIB}/alembic/migration.py ${PYSITELIB}/alembic/migration.pyc ${PYSITELIB}/alembic/migration.pyo ${PYSITELIB}/alembic/op.py ${PYSITELIB}/alembic/op.pyc ${PYSITELIB}/alembic/op.pyi ${PYSITELIB}/alembic/op.pyo ${PYSITELIB}/alembic/operations/__init__.py ${PYSITELIB}/alembic/operations/__init__.pyc ${PYSITELIB}/alembic/operations/__init__.pyo ${PYSITELIB}/alembic/operations/base.py ${PYSITELIB}/alembic/operations/base.pyc ${PYSITELIB}/alembic/operations/base.pyo ${PYSITELIB}/alembic/operations/batch.py ${PYSITELIB}/alembic/operations/batch.pyc ${PYSITELIB}/alembic/operations/batch.pyo ${PYSITELIB}/alembic/operations/ops.py ${PYSITELIB}/alembic/operations/ops.pyc ${PYSITELIB}/alembic/operations/ops.pyo ${PYSITELIB}/alembic/operations/schemaobj.py ${PYSITELIB}/alembic/operations/schemaobj.pyc ${PYSITELIB}/alembic/operations/schemaobj.pyo ${PYSITELIB}/alembic/operations/toimpl.py ${PYSITELIB}/alembic/operations/toimpl.pyc ${PYSITELIB}/alembic/operations/toimpl.pyo ${PYSITELIB}/alembic/py.typed ${PYSITELIB}/alembic/runtime/__init__.py ${PYSITELIB}/alembic/runtime/__init__.pyc ${PYSITELIB}/alembic/runtime/__init__.pyo ${PYSITELIB}/alembic/runtime/environment.py ${PYSITELIB}/alembic/runtime/environment.pyc ${PYSITELIB}/alembic/runtime/environment.pyo ${PYSITELIB}/alembic/runtime/migration.py ${PYSITELIB}/alembic/runtime/migration.pyc ${PYSITELIB}/alembic/runtime/migration.pyo ${PYSITELIB}/alembic/script/__init__.py ${PYSITELIB}/alembic/script/__init__.pyc ${PYSITELIB}/alembic/script/__init__.pyo ${PYSITELIB}/alembic/script/base.py ${PYSITELIB}/alembic/script/base.pyc ${PYSITELIB}/alembic/script/base.pyo ${PYSITELIB}/alembic/script/revision.py ${PYSITELIB}/alembic/script/revision.pyc ${PYSITELIB}/alembic/script/revision.pyo ${PYSITELIB}/alembic/script/write_hooks.py ${PYSITELIB}/alembic/script/write_hooks.pyc ${PYSITELIB}/alembic/script/write_hooks.pyo ${PYSITELIB}/alembic/templates/async/README ${PYSITELIB}/alembic/templates/async/alembic.ini.mako ${PYSITELIB}/alembic/templates/async/env.py ${PYSITELIB}/alembic/templates/async/env.pyc ${PYSITELIB}/alembic/templates/async/env.pyo ${PYSITELIB}/alembic/templates/async/script.py.mako ${PYSITELIB}/alembic/templates/generic/README ${PYSITELIB}/alembic/templates/generic/alembic.ini.mako ${PYSITELIB}/alembic/templates/generic/env.py ${PYSITELIB}/alembic/templates/generic/env.pyc ${PYSITELIB}/alembic/templates/generic/env.pyo ${PYSITELIB}/alembic/templates/generic/script.py.mako ${PYSITELIB}/alembic/templates/multidb/README ${PYSITELIB}/alembic/templates/multidb/alembic.ini.mako ${PYSITELIB}/alembic/templates/multidb/env.py ${PYSITELIB}/alembic/templates/multidb/env.pyc ${PYSITELIB}/alembic/templates/multidb/env.pyo ${PYSITELIB}/alembic/templates/multidb/script.py.mako ${PYSITELIB}/alembic/testing/__init__.py ${PYSITELIB}/alembic/testing/__init__.pyc ${PYSITELIB}/alembic/testing/__init__.pyo ${PYSITELIB}/alembic/testing/assertions.py ${PYSITELIB}/alembic/testing/assertions.pyc ${PYSITELIB}/alembic/testing/assertions.pyo ${PYSITELIB}/alembic/testing/env.py ${PYSITELIB}/alembic/testing/env.pyc ${PYSITELIB}/alembic/testing/env.pyo ${PYSITELIB}/alembic/testing/fixtures.py ${PYSITELIB}/alembic/testing/fixtures.pyc ${PYSITELIB}/alembic/testing/fixtures.pyo ${PYSITELIB}/alembic/testing/plugin/__init__.py ${PYSITELIB}/alembic/testing/plugin/__init__.pyc ${PYSITELIB}/alembic/testing/plugin/__init__.pyo ${PYSITELIB}/alembic/testing/plugin/bootstrap.py ${PYSITELIB}/alembic/testing/plugin/bootstrap.pyc ${PYSITELIB}/alembic/testing/plugin/bootstrap.pyo ${PYSITELIB}/alembic/testing/requirements.py ${PYSITELIB}/alembic/testing/requirements.pyc ${PYSITELIB}/alembic/testing/requirements.pyo ${PYSITELIB}/alembic/testing/schemacompare.py ${PYSITELIB}/alembic/testing/schemacompare.pyc ${PYSITELIB}/alembic/testing/schemacompare.pyo ${PYSITELIB}/alembic/testing/suite/__init__.py ${PYSITELIB}/alembic/testing/suite/__init__.pyc ${PYSITELIB}/alembic/testing/suite/__init__.pyo ${PYSITELIB}/alembic/testing/suite/_autogen_fixtures.py ${PYSITELIB}/alembic/testing/suite/_autogen_fixtures.pyc ${PYSITELIB}/alembic/testing/suite/_autogen_fixtures.pyo ${PYSITELIB}/alembic/testing/suite/test_autogen_comments.py ${PYSITELIB}/alembic/testing/suite/test_autogen_comments.pyc ${PYSITELIB}/alembic/testing/suite/test_autogen_comments.pyo ${PYSITELIB}/alembic/testing/suite/test_autogen_computed.py ${PYSITELIB}/alembic/testing/suite/test_autogen_computed.pyc ${PYSITELIB}/alembic/testing/suite/test_autogen_computed.pyo ${PYSITELIB}/alembic/testing/suite/test_autogen_diffs.py ${PYSITELIB}/alembic/testing/suite/test_autogen_diffs.pyc ${PYSITELIB}/alembic/testing/suite/test_autogen_diffs.pyo ${PYSITELIB}/alembic/testing/suite/test_autogen_fks.py ${PYSITELIB}/alembic/testing/suite/test_autogen_fks.pyc ${PYSITELIB}/alembic/testing/suite/test_autogen_fks.pyo ${PYSITELIB}/alembic/testing/suite/test_autogen_identity.py ${PYSITELIB}/alembic/testing/suite/test_autogen_identity.pyc ${PYSITELIB}/alembic/testing/suite/test_autogen_identity.pyo ${PYSITELIB}/alembic/testing/suite/test_environment.py ${PYSITELIB}/alembic/testing/suite/test_environment.pyc ${PYSITELIB}/alembic/testing/suite/test_environment.pyo ${PYSITELIB}/alembic/testing/suite/test_op.py ${PYSITELIB}/alembic/testing/suite/test_op.pyc ${PYSITELIB}/alembic/testing/suite/test_op.pyo ${PYSITELIB}/alembic/testing/util.py ${PYSITELIB}/alembic/testing/util.pyc ${PYSITELIB}/alembic/testing/util.pyo ${PYSITELIB}/alembic/testing/warnings.py ${PYSITELIB}/alembic/testing/warnings.pyc ${PYSITELIB}/alembic/testing/warnings.pyo ${PYSITELIB}/alembic/util/__init__.py ${PYSITELIB}/alembic/util/__init__.pyc ${PYSITELIB}/alembic/util/__init__.pyo ${PYSITELIB}/alembic/util/compat.py ${PYSITELIB}/alembic/util/compat.pyc ${PYSITELIB}/alembic/util/compat.pyo ${PYSITELIB}/alembic/util/editor.py ${PYSITELIB}/alembic/util/editor.pyc ${PYSITELIB}/alembic/util/editor.pyo ${PYSITELIB}/alembic/util/exc.py ${PYSITELIB}/alembic/util/exc.pyc ${PYSITELIB}/alembic/util/exc.pyo ${PYSITELIB}/alembic/util/langhelpers.py ${PYSITELIB}/alembic/util/langhelpers.pyc ${PYSITELIB}/alembic/util/langhelpers.pyo ${PYSITELIB}/alembic/util/messaging.py ${PYSITELIB}/alembic/util/messaging.pyc ${PYSITELIB}/alembic/util/messaging.pyo ${PYSITELIB}/alembic/util/pyfiles.py ${PYSITELIB}/alembic/util/pyfiles.pyc ${PYSITELIB}/alembic/util/pyfiles.pyo ${PYSITELIB}/alembic/util/sqla_compat.py ${PYSITELIB}/alembic/util/sqla_compat.pyc ${PYSITELIB}/alembic/util/sqla_compat.pyo @ 1.8 log @py-alembic: updated to 1.7.5 1.7.5 Released: November 11, 2021 bug [bug] [tests] Adjustments to the test suite to accommodate for error message changes occurring as of SQLAlchemy 1.4.27. 1.7.4 Released: October 6, 2021 bug [bug] [regression] Fixed a regression that prevented the use of post write hooks on python version lower than 3.9 [bug] [environment] Fixed issue where the MigrationContext.autocommit_block() feature would fail to function when using a SQLAlchemy engine using 2.0 future mode. 1.7.3 Released: September 17, 2021 bug [bug] [mypy] Fixed type annotations for the “constraint_name” argument of operations create_primary_key(), create_foreign_key(). Pull request courtesy TilmanK. 1.7.2 Released: September 17, 2021 bug [bug] [typing] Added missing attributes from context stubs. [bug] [mypy] Fixed an import in one of the .pyi files that was triggering an assertion error in some versions of mypy. [bug] [ops] [regression] Fixed issue where registration of custom ops was prone to failure due to the registration process running exec() on generated code that as of the 1.7 series includes pep-484 annotations, which in the case of end user code would result in name resolution errors when the exec occurs. The logic in question has been altered so that the annotations are rendered as forward references so that the exec() can proceed. 1.7.1 Released: August 30, 2021 bug [bug] [installation] Corrected “universal wheel” directive in setup.cfg so that building a wheel does not target Python 2. The PyPi files index for 1.7.0 was corrected manually. Pull request courtesy layday. [bug] [pep484] Fixed issue in generated .pyi files where default values for Optional arguments were missing, thereby causing mypy to consider them as required. [bug] [batch] [regression] Fixed regression in batch mode due to 883 where the “auto” mode of batch would fail to accommodate any additional migration directives beyond encountering an add_column() directive, due to a mis-application of the conditional logic that was added as part of this change, leading to “recreate” mode not being used in cases where it is required for SQLite such as for unique constraints. 1.7.0 Released: August 30, 2021 changed [changed] [installation] Alembic 1.7 now supports Python 3.6 and above; support for prior versions including Python 2.7 has been dropped. [changed] [installation] Make the python-dateutil library an optional dependency. This library is only required if the timezone option is used in the Alembic configuration. An extra require named tz is available with pip install alembic[tz] to install it. [changed] [installation] The dependency on pkg_resources which is part of setuptools has been removed, so there is no longer any runtime dependency on setuptools. The functionality has been replaced with importlib.metadata and importlib.resources which are both part of Python std.lib, or via pypy dependency importlib-metadata for Python version < 3.8 and importlib-resources for Python version < 3.9 (while importlib.resources was added to Python in 3.7, it did not include the “files” API until 3.9). feature [feature] [environment] Enhance version_locations parsing to handle paths containing spaces. The new configuration option version_path_separator specifies the character to use when splitting the version_locations string. The default for new configurations is version_path_separator = os, which will use os.pathsep (e.g., ; on Windows). [feature] [tests] Created a “test suite” similar to the one for SQLAlchemy, allowing developers of third-party dialects to test their code against a set of Alembic tests that have been specially selected to exercise back-end database operations. At the time of release, third-party dialects that have adopted the Alembic test suite to verify compatibility include CockroachDB and SAP ASE (Sybase). [feature] [general] pep-484 type annotations have been added throughout the library. Additionally, stub .pyi files have been added for the “dynamically” generated Alembic modules alembic.op and alembic.config, which include complete function signatures and docstrings, so that the functions in these namespaces will have both IDE support (vscode, pycharm, etc) as well as support for typing tools like Mypy. The files themselves are statically generated from their source functions within the source tree. usecase [usecase] [batch] Named CHECK constraints are now supported by batch mode, and will automatically be part of the recreated table assuming they are named. They also can be explicitly dropped using op.drop_constraint(). For “unnamed” CHECK constraints, these are still skipped as they cannot be distinguished from the CHECK constraints that are generated by the Boolean and Enum datatypes. Note that this change may require adjustments to migrations that drop or rename columns which feature an associated named check constraint, such that an additional op.drop_constraint() directive should be added for that named constraint as there will no longer be an associated column for it; for the Boolean and Enum datatypes, an existing_type keyword may be passed to BatchOperations.drop_constraint as well. See also Changing the Type of Boolean, Enum and other implicit CHECK datatypes Including CHECK constraints bug [bug] [operations] Fixed regression due to 803 where the .info and .comment attributes of Table would be lost inside of the DropTableOp class, which when “reversed” into a CreateTableOp would then have lost these elements. Pull request courtesy Nicolas CANIART. [bug] [batch] [sqlite] Batch “auto” mode will now select for “recreate” if the add_column() operation is used on SQLite, and the column itself meets the criteria for SQLite where ADD COLUMN is not allowed, in this case a functional or parenthesized SQL expression or a Computed (i.e. generated) column. [bug] [commands] Re-implemented the python-editor dependency as a small internal function to avoid the need for external dependencies. [bug] [postgresql] Fixed issue where usage of the PostgreSQL postgresql_include option within a Operations.create_index() would raise a KeyError, as the additional column(s) need to be added to the table object used by the construct internally. The issue is equivalent to the SQL Server issue fixed in 513. Pull request courtesy Steven Bronson. 1.6.5 Released: May 27, 2021 bug [bug] [autogenerate] Fixed issue where dialect-specific keyword arguments within the DropIndex operation directive would not render in the autogenerated Python code. As support was improved for adding dialect specific arguments to directives as part of 803, in particular arguments such as “postgresql_concurrently” which apply to the actual create/drop of the index, support was needed for these to render even in a drop index operation. Pull request courtesy Jet Zhou. 1.6.4 Released: May 24, 2021 bug [bug] [op directives] [regression] Fixed regression caused by just fixed 844 that scaled back the filter for unique=True/index=True too far such that these directives no longer worked for the op.create_table() op, this has been fixed. 1.6.3 Released: May 21, 2021 bug [bug] [autogenerate] [regression] Fixed 1.6-series regression where UniqueConstraint and to a lesser extent Index objects would be doubled up in the generated model when the unique=True / index=True flags were used. [bug] [autogenerate] Fixed a bug where paths defined in post-write hook options would be wrongly escaped in non posix environment (Windows). [bug] [regression] [versioning] Fixed regression where a revision file that contained its own down revision as a dependency would cause an endless loop in the traversal logic. 1.6.2 Released: May 6, 2021 bug [bug] [regression] [versioning] Fixed additional regression nearly the same as that of 838 just released in 1.6.1 but within a slightly different codepath, where “alembic downgrade head” (or equivalent) would fail instead of iterating no revisions. 1.6.1 Released: May 6, 2021 bug [bug] [regression] [versioning] Fixed regression in new revisioning traversal where “alembic downgrade base” would fail if the database itself were clean and unversioned; additionally repairs the case where downgrade would fail if attempting to downgrade to the current head that is already present. 1.6.0 Released: May 3, 2021 feature [feature] [autogenerate] Fix the documentation regarding the default command-line argument position of the revision script filename within the post-write hook arguments. Implement a REVISION_SCRIPT_FILENAME token, enabling the position to be changed. Switch from str.split() to shlex.split() for more robust command-line argument parsing. [feature] Implement a .cwd (current working directory) suboption for post-write hooks (of type console_scripts). This is useful for tools like pre-commit, which rely on the working directory to locate the necessary config files. Add pre-commit as an example to the documentation. Minor change: rename some variables from ticket 819 to improve readability. bug [bug] [autogenerate] Refactored the implementation of MigrateOperation constructs such as CreateIndexOp, CreateTableOp, etc. so that they no longer rely upon maintaining a persistent version of each schema object internally; instead, the state variables of each operation object will be used to produce the corresponding construct when the operation is invoked. The rationale is so that environments which make use of operation-manipulation schemes such as those those discussed in Fine-Grained Autogenerate Generation with Rewriters are better supported, allowing end-user code to manipulate the public attributes of these objects which will then be expressed in the final output, an example is some_create_index_op.kw["postgresql_concurrently"] = True. Previously, these objects when generated from autogenerate would typically hold onto the original, reflected element internally without honoring the other state variables of each construct, preventing the public API from working. [bug] [environment] Fixed regression caused by the SQLAlchemy 1.4/2.0 compatibility switch where calling .rollback() or .commit() explicitly within the context.begin_transaction() context manager would cause it to fail when the block ended, as it did not expect that the transaction was manually closed. [bug] [autogenerate] Improved the rendering of op.add_column() operations when adding multiple columns to an existing table, so that the order of these statements matches the order in which the columns were declared in the application’s table metadata. Previously the added columns were being sorted alphabetically. [bug] [versioning] The algorithm used for calculating downgrades/upgrades/iterating revisions has been rewritten, to resolve ongoing issues of branches not being handled consistently particularly within downgrade operations, as well as for overall clarity and maintainability. This change includes that a deprecation warning is emitted if an ambiguous command such as “downgrade -1” when multiple heads are present is given. In particular, the change implements a long-requested use case of allowing downgrades of a single branch to a branchpoint. Huge thanks to Simon Bowly for their impressive efforts in successfully tackling this very difficult problem. [bug] [batch] ¶ Added missing batch_op.create_table_comment(), batch_op.drop_table_comment() directives to batch ops. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.7 2021/01/26 11:20:07 adam Exp $ d3 6 a8 7 ${PYSITELIB}/${EGG_INFODIR}/PKG-INFO ${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt ${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt ${PYSITELIB}/${EGG_INFODIR}/entry_points.txt ${PYSITELIB}/${EGG_INFODIR}/not-zip-safe ${PYSITELIB}/${EGG_INFODIR}/requires.txt ${PYSITELIB}/${EGG_INFODIR}/top_level.txt d43 3 a134 6 ${PYSITELIB}/alembic/templates/pylons/README ${PYSITELIB}/alembic/templates/pylons/alembic.ini.mako ${PYSITELIB}/alembic/templates/pylons/env.py ${PYSITELIB}/alembic/templates/pylons/env.pyc ${PYSITELIB}/alembic/templates/pylons/env.pyo ${PYSITELIB}/alembic/templates/pylons/script.py.mako @ 1.7 log @py-alembic: updated to 1.5.2 1.5.2 [bug] [regression] [versioning] Fixed regression where new “loop detection” feature introduced in 757 produced false positives for revision names that have overlapping substrings between revision number and down revision and/or dependency, if the downrev/dependency were not in sequence form. [bug] [environment] Fixed regression where Alembic would fail to create a transaction properly if the sqlalchemy.engine.Connection were a so-called “branched” connection, that is, one where the .connect() method had been called to create a “sub” connection. 1.5.1 [bug] [commands] [installation] Fixed installation issue where the “templates” directory was not being installed, preventing commands like “list_templates” and “init” from working. 1.5.0 [changed] [environment] To accommodate SQLAlchemy 1.4 and 2.0, the migration model now no longer assumes that the SQLAlchemy Connection will autocommit an individual operation. This essentially means that for databases that use non-transactional DDL (pysqlite current driver behavior, MySQL), there is still a BEGIN/COMMIT block that will surround each individual migration. Databases that support transactional DDL should continue to have the same flow, either per migration or per-entire run, depending on the value of the Environment.configure.transaction_per_migration flag. [changed] [environment] A CommandError is raised if a sqlalchemy.engine.Engine is passed to the MigrationContext.configure() method instead of a sqlalchemy.engine.Connection object. Previously, this would be a warning only. [changed] Alembic 1.5.0 now supports Python 2.7 and Python 3.6 and above, as well as SQLAlchemy 1.3.0 and above. Support is removed for Python 3 versions prior to 3.6 and SQLAlchemy versions prior to the 1.3 series. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.6 2020/02/16 21:11:41 adam Exp $ d39 1 d65 6 d73 1 d93 1 d115 6 d160 30 d202 3 @ 1.6 log @py-alembic: updated to 1.4.0 1.4.0 [feature] [batch] Added new parameters BatchOperations.add_column.insert_before, BatchOperations.add_column.insert_after which provide for establishing the specific position in which a new column should be placed. Also added Operations.batch_alter_table.partial_reordering which allows the complete set of columns to be reordered when the new table is created. Both operations apply only to when batch mode is recreating the whole table using recreate="always". Thanks to Marcin Szymanski for assistance with the implementation. bug [bug] [autogenerate] Adjusted the unique constraint comparison logic in a similar manner as that of 421 did for indexes in order to take into account SQLAlchemy’s own truncation of long constraint names when a naming convention is in use. Without this step, a name that is truncated by SQLAlchemy based on a unique constraint naming convention or hardcoded name will not compare properly. [bug] [autogenerate] A major rework of the “type comparison” logic is in place which changes the entire approach by which column datatypes are compared. Types are now compared based on the DDL string generated by the metadata type vs. the datatype reflected from the database. This means we compare types based on what would actually render and additionally if elements of the types change like string length, those changes are detected as well. False positives like those generated between SQLAlchemy Boolean and MySQL TINYINT should also be resolved. Thanks very much to Paul Becotte for lots of hard work and patience on this one. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.5 2019/10/10 18:26:53 adam Exp $ d13 3 a132 6 ${PYSITELIB}/alembic/testing/exclusions.py ${PYSITELIB}/alembic/testing/exclusions.pyc ${PYSITELIB}/alembic/testing/exclusions.pyo ${PYSITELIB}/alembic/testing/fixture_functions.py ${PYSITELIB}/alembic/testing/fixture_functions.pyc ${PYSITELIB}/alembic/testing/fixture_functions.pyo a141 6 ${PYSITELIB}/alembic/testing/plugin/plugin_base.py ${PYSITELIB}/alembic/testing/plugin/plugin_base.pyc ${PYSITELIB}/alembic/testing/plugin/plugin_base.pyo ${PYSITELIB}/alembic/testing/plugin/pytestplugin.py ${PYSITELIB}/alembic/testing/plugin/pytestplugin.pyc ${PYSITELIB}/alembic/testing/plugin/pytestplugin.pyo d148 3 @ 1.5 log @py-alembic: updated to 1.2.1 1.2.1 bug [bug] [command] Reverted the name change of the “revisions” argument to command.stamp() to “revision” as apparently applications are calling upon this argument as a keyword name. Pull request courtesy Thomas Bechtold. Special translations are also added to the command line interface so that it is still known as “revisions” in the CLI. [bug] [tests] Removed the “test requirements” from “setup.py test”, as this command now only emits a removal error in any case and these requirements are unused. 1.2.0 feature [feature] [command] Added new --purge flag to the alembic stamp command, which will unconditionally erase the version table before stamping anything. This is useful for development where non-existent version identifiers might be left within the table. Additionally, alembic.stamp now supports a list of revision identifiers, which are intended to allow setting up muliple heads at once. Overall handling of version identifiers within the alembic.stamp command has been improved with many new tests and use cases added. [feature] [runtime] Added new feature MigrationContext.autocommit_block(), a special directive which will provide for a non-transactional block inside of a migration script. The feature requres that: the database driver (e.g. DBAPI) supports the AUTOCOMMIT isolation mode. The directive also necessarily needs to COMMIT the existing transaction in progress in order to enter autocommit mode. [feature] [commands] Added “post write hooks” to revision generation. These allow custom logic to run after a revision Python script is generated, typically for the purpose of running code formatters such as “Black” or “autopep8”, but may be used for any arbitrary post-render hook as well, including custom Python functions or scripts. The hooks are enabled by providing a [post_write_hooks] section in the alembic.ini file. A single hook is provided which runs an arbitrary Python executable on the newly generated revision script, which can be configured to run code formatters such as Black; full examples are included in the documentation. [feature] [environment] Added new flag --package to alembic init. For environments where the Alembic migration files and such are within the package tree and importable as modules, this flag can be specified which will add the additional __init__.py files in the version location and the environment location. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.4 2019/08/28 06:37:38 adam Exp $ d130 6 d139 12 d154 3 @ 1.4 log @py-alembic: updated to 1.1.0 1.1.0: bug [bug] [commands] Fixed bug where the double-percent logic applied to some dialects such as psycopg2 would be rendered in --sql mode, by allowing dialect options to be passed through to the dialect used to generate SQL and then providing paramstyle="named" so that percent signs need not be doubled. For users having this issue, existing env.py scripts need to add dialect_opts={"paramstyle": "named"} to their offline context.configure(). See the alembic/templates/generic/env.py template for an example. [bug] [py3k] Fixed use of the deprecated “imp” module, which is used to detect pep3147 availability as well as to locate .pyc files, which started emitting deprecation warnings during the test suite. The warnings were not being emitted earlier during the test suite, the change is possibly due to changes in py.test itself but this is not clear. The check for pep3147 is set to True for any Python version 3.5 or greater now and importlib is used when available. Note that some dependencies such as distutils may still be emitting this warning. Tests are adjusted to accommodate for dependencies that emit the warning as well. [bug] [mysql] Fixed issue where emitting a change of column name for MySQL did not preserve the column comment, even if it were specified as existing_comment. [bug] [setup] Removed the “python setup.py test” feature in favor of a straight run of “tox”. Per Pypa / pytest developers, “setup.py” commands are in general headed towards deprecation in favor of tox. The tox.ini script has been updated such that running “tox” with no arguments will perform a single run of the test suite against the default installed Python interpreter. usecase [usecase] [commands] The “alembic init” command will now proceed if the target directory exists as long as it’s still empty. Previously, it would not proceed if the directory existed. The new behavior is modeled from what git does, to accommodate for container or other deployments where an Alembic target directory may need to be already mounted instead of being created with alembic init. Pull request courtesy Aviskar KC. misc [change] Alembic 1.1 bumps the minimum version of SQLAlchemy to 1.1. As was the case before, Python requirements remain at Python 2.7, or in the 3.x series Python 3.4. [change] [internals] The test suite for Alembic now makes use of SQLAlchemy’s testing framework directly. Previously, Alembic had its own version of this framework that was mostly copied from that of SQLAlchemy to enable testing with older SQLAlchemy versions. The majority of this code is now removed so that both projects can leverage improvements from a common testing framework. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.3 2018/10/18 10:15:18 adam Exp $ d100 3 @ 1.3 log @py-alembic: updated to 1.0.1 1.0.1: Fixed an issue where revision descriptions were essentially being formatted twice. Any revision description that contained characters like %, writing output to stdout will fail because the call to config.print_stdout attempted to format any additional args passed to the function. This fix now only applies string formatting if any args are provided along with the output text. Fixed issue where removed method union_update() was used when a customized MigrationScript instance included entries in the .imports data member, raising an AttributeError. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.2 2018/01/18 09:18:06 adam Exp $ a123 9 ${PYSITELIB}/alembic/testing/compat.py ${PYSITELIB}/alembic/testing/compat.pyc ${PYSITELIB}/alembic/testing/compat.pyo ${PYSITELIB}/alembic/testing/config.py ${PYSITELIB}/alembic/testing/config.pyc ${PYSITELIB}/alembic/testing/config.pyo ${PYSITELIB}/alembic/testing/engines.py ${PYSITELIB}/alembic/testing/engines.pyc ${PYSITELIB}/alembic/testing/engines.pyo a126 3 ${PYSITELIB}/alembic/testing/exclusions.py ${PYSITELIB}/alembic/testing/exclusions.pyc ${PYSITELIB}/alembic/testing/exclusions.pyo a129 21 ${PYSITELIB}/alembic/testing/mock.py ${PYSITELIB}/alembic/testing/mock.pyc ${PYSITELIB}/alembic/testing/mock.pyo ${PYSITELIB}/alembic/testing/plugin/__init__.py ${PYSITELIB}/alembic/testing/plugin/__init__.pyc ${PYSITELIB}/alembic/testing/plugin/__init__.pyo ${PYSITELIB}/alembic/testing/plugin/bootstrap.py ${PYSITELIB}/alembic/testing/plugin/bootstrap.pyc ${PYSITELIB}/alembic/testing/plugin/bootstrap.pyo ${PYSITELIB}/alembic/testing/plugin/noseplugin.py ${PYSITELIB}/alembic/testing/plugin/noseplugin.pyc ${PYSITELIB}/alembic/testing/plugin/noseplugin.pyo ${PYSITELIB}/alembic/testing/plugin/plugin_base.py ${PYSITELIB}/alembic/testing/plugin/plugin_base.pyc ${PYSITELIB}/alembic/testing/plugin/plugin_base.pyo ${PYSITELIB}/alembic/testing/plugin/pytestplugin.py ${PYSITELIB}/alembic/testing/plugin/pytestplugin.pyc ${PYSITELIB}/alembic/testing/plugin/pytestplugin.pyo ${PYSITELIB}/alembic/testing/provision.py ${PYSITELIB}/alembic/testing/provision.pyc ${PYSITELIB}/alembic/testing/provision.pyo a132 9 ${PYSITELIB}/alembic/testing/runner.py ${PYSITELIB}/alembic/testing/runner.pyc ${PYSITELIB}/alembic/testing/runner.pyo ${PYSITELIB}/alembic/testing/util.py ${PYSITELIB}/alembic/testing/util.pyc ${PYSITELIB}/alembic/testing/util.pyo ${PYSITELIB}/alembic/testing/warnings.py ${PYSITELIB}/alembic/testing/warnings.pyc ${PYSITELIB}/alembic/testing/warnings.pyo @ 1.2 log @py-alembic: use PYVERSSUFFIX and ALTERNATIVES @ text @d1 2 a2 2 @@comment $NetBSD: PLIST,v 1.1 2017/09/17 04:00:15 minskim Exp $ bin/alembic${PYVERSSUFFIX} @ 1.1 log @databases/py-alembic: Import version 0.9.5 from pkgsrc-wip Alembic is a database migrations tool written by the author of SQLAlchemy. A migrations tool 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, and allows the scripts to execute in some sequential manner. Packaged by Kamel Ibn Aziz Derouiche and updated by me. @ text @d1 2 a2 2 @@comment $NetBSD$ bin/alembic @