python-alembic
A database migration tool for SQLAlchemy
- Sources inherited from project devel:languages:python
- Devel package for openSUSE:Factory
-
6
derived packages
- Links to openSUSE:Factory / python-alembic
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:smarty12:Python/python-alembic && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
alembic-1.11.1.tar.gz | 0001176522 1.12 MB | |
python-alembic.changes | 0000110159 108 KB | |
python-alembic.spec | 0000003120 3.05 KB |
Revision 146 (latest revision is 161)
Dirk Mueller (dirkmueller)
committed
(revision 146)
- update to 1.11.1: * As Alembic 1.11.0 is considered a major release (Alembic does not use semver, nor does its parent project SQLAlchemy; this has been `clarified <versioning_scheme>` in the documentation), * :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. * Fixed typing use of :class:`~sqlalchemy.schema.Column` and other generic SQLAlchemy classes. * 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. * 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".
Comments 0