| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
after black is applied, rewrite imports and fix
remaining whitespace / identifier issues.
Change-Id: I49474c085b5f4a4b52e4cf90c9705d6a896d4003
|
| |
|
|
|
|
|
| |
run black -l 79 against source code, set up for
full flake8 testing.
Change-Id: I4108e1274d49894b9898ec5bd3a1147933a473d7
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed bug where the :meth:`.Script.as_revision_number` method
did not accommodate for the 'heads' identifier, which in turn
caused the :meth:`.EnvironmentContext.get_head_revisions`
and :meth:`.EnvironmentContext.get_revision_argument` methods
to be not usable when multiple heads were present.
The :meth:.`EnvironmentContext.get_head_revisions` method returns
a tuple in all cases as documented.
Change-Id: I085d9b6c3f4ceafd6828d24983768a3d3916ce00
Fixes: #482
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
get_current_heads() directly; therefore we don't need to
do this in alembic.command, which we were doing for stamp but
not downgrade/upgrade. The slight change here is that the
context.get_starting_revision_argument() method will
return an abbreviated starting rev as abbreviated in
all cases, including the stamp command, where we previously
were converting a stamp argument first, but not for the
upgrade or downgrade commands.
- Fixed bug where using a partial revision identifier as the
"starting revision" in ``--sql`` mode in a downgrade operation
would fail to resolve properly. fixes #269
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
by far the most significant change Alembic has seen since its inception;
while the workflow of most commands hasn't changed, and the format
of version files and the ``alembic_version`` table are unchanged as well,
a new suite of features opens up in the case where multiple version
files refer to the same parent, or to the "base". Merging of
branches, operating across distinct named heads, and multiple
independent bases are now all supported. The feature incurs radical
changes to the internals of versioning and traversal, and should be
treated as "beta mode" for the next several subsequent releases
within 0.7.
fixes #167
|
| | |
|
| | |
|
| |
|
|
| |
than line length
|
| |
|
|
|
|
|
| |
the use of the new io.* package introduced some incompatibilities on Py2k.
These should be resolved, due to the introduction of new adapter types
for translating from io.* to Py2k file types, StringIO types.
Thanks to Javier Santacruz for help with this.
|
| |
|
|
|
|
|
|
|
| |
When output_encoding is set, wraps the output buffer into a io.TextIOWrapper class
This means that the output_buffer has to be a io.IOBase instance
in order to work along with the TextIOWrapper
Handles wrapping when the buffer is Python2 stdtout, which has 'file' type
Adds test for this situation
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change does not affect to any behaviors of it, but is just stylish
improvements to remove 2to3 dependency.
1. All old-style absolute imports e.g. `from alembic import util` are
replaced by relative imports e.g. `from . import util`.
2. Use of proxy modules (`alembic.op` and `alembic.context`) are replaced
by deferred import patterns, but these modules still exist.
3. Imports are grouped by 3 types of their origins (standard libraries,
third party libraries, and local modules) and blank lines are put between
each group of imports. This style is from PEP 8:
<http://www.python.org/dev/peps/pep-0008/#imports>
For stylish change, I can't do that much, because it was intentionally done
as it was by the author. If the author will allow me to make it more closer
to PEP 8 style, I will do that as well.
|
| | |
|
| |
|
|
|
| |
when downgrade --sql is used without specifying
specific start/end versions. #66
|
| | |
|
| |
|
|
|
|
| |
file handles are closed.
- PyPy is supported.
|
| |
|
|
|
| |
- add support for actual DB connections, test.cfg, etc.
- add PG server default comparison tests, #6
|
| | |
|
|
|
- more environment functions
- clean up start:end system
- docs
|
