| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: If7b9e9fca39e6a6abe45900ff396345c778bbaa9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 :paramref:`.Environment.configure.transaction_per_migration`
flag.
Compatibility is established such that the entire library should
not generate any SQLAlchemy 2.0 deprecation warnings and
SQLALCHEMY_WARN_20 is part of conftest.py. (one warning remains
for the moment that needs to be resolved on the SQLAlchemy side)
The test suite requires SQLAlchemy 1.4.0b2 for testing 1.4;
1.4.0b1 won't work.
Test suite / setup also being modernized, as we are at
SQLAlchemy 1.3 we can now remove the majority of the testing
suite plugin.
Change-Id: If55b1ea3c12ead66405ab3fadc76d15d89dabb90
|
|
|
|
|
| |
Fixes: #748
Change-Id: I18df97bdce5de6adb222d3f16486272e95b1b1a6
|
|
|
|
|
|
|
|
| |
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.
Change-Id: I53a798bdedad88d8f9708ed3fb6d8ed1aa49f526
Fixes: #592
|
|
|
|
|
|
|
|
| |
mysqlclient is no longer working in Python 3.4, and as pip is also
emitting warnings for dropped support, in order to maintain CI
we need to drop Python 3.4. Also include 3.7, 3.8 in classifiers.
Change-Id: I6fb2514934b6133d2a484621a0d7003b424c66f4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
.. seealso::
https://github.com/pypa/setuptools/issues/1684
https://github.com/pytest-dev/pytest/issues/5534
Change-Id: Ib92ef8d20ad0e6f1e1b9d25051b788788cc69b02
Fixes: #592
|
|
|
|
|
|
|
|
| |
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-Id: I68074fb4b59c96c4a596396a69aa143c65d048b5
|
|
|
|
| |
Change-Id: I6c224a8b4061a02cb31d07161bb67632a6b3d1e3
|
|
|
|
| |
Change-Id: I850c35cef1b4baed7b30510429d1785d0bf5673a
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Alembic is now under the sqlalchemy.org domain
for the website and all repos are moving under github.com/sqlalchemy.
Change-Id: Id9ce08b61ed0ccdf50396f911838b21112e61652
|
|
|
|
|
| |
Change-Id: Ib00d07058997e97a992084bd949ebb6ed2bcb2e2
References: I867e2b36122f578e69f2444ef9712cd73995cce3
|
|
|
|
|
|
| |
https://github.com/pytest-dev/pytest/issues/4181 is fixed
Change-Id: I867e2b36122f578e69f2444ef9712cd73995cce3
|
|
|
|
|
|
|
|
| |
references:
https://github.com/pytest-dev/pytest/issues/4181
Change-Id: Iad3b6845e94753c55771419ccd1f99852bc89159
|
|
|
|
| |
Change-Id: I42db26db364c7a4146b184da14e258ac93afce32
|
|
|
|
|
|
|
| |
With the 1.0 release, Alembic's minimum SQLAlchemy support version
moves to 0.9.0, previously 0.7.9.
Change-Id: I299d8af11c5982c4a792da1fcb96e4b437af687d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For Alembic 1.0, Python 2.6 / 3.3 support is being dropped, allowing a
fixed setup.py to be built as well as universal wheels. Pull request
courtesy Hugo.
Change-Id: Iff9018ea6c5a65b3560f7ca72e0ef233c822ec27
Fixes: #491
|
|/
|
|
| |
Change-Id: Ia4c29125de1373cdd7a327ea1a960415828466ca
|
|
|
|
|
|
|
|
|
| |
Using dateutil.tz to link string names to tzinfo objects,
the create_date can now generate using a named timezone
rather than datetime.now().
Change-Id: I9f151cb9e11da3d68be63d7141f60e7eccb9812c
Fixes: #425
|
| |
|
|\ |
|
| | |
|
| | |
|
|/
|
|
| |
nose still works via run_tests.py.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
like to run tests against 0.8 and even late 0.7 versions with the same
capabilities, as well as run parallel testing against all of them.
we need a consistent system to get that all to work, so for now
we have the whole SQLA system shoved into here, not ideal but we have
a very good testing situation for now. Once we target 0.9.4 at the lowest
we should be able to move all this out.
- re-support 0.7, starting at 0.7.6 which is where things mostly work.
All tests, taking into account known skips and fails which are
added here for 0.7, early 0.8s, pass on 0.7.9.
|
|
|
|
| |
- some workarounds to get 0.8 mostly working
|
| |
|
|
|
|
| |
than line length
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
when "setup.py test" is run, #96
- add version detection for 0.8, apply this version detection to
test_autogenerate:AutogenRenderTest.test_render_fk_constraint_kwarg
and emit explicit append_constraint() for each FK if not on 0.8 as FKs
do not auto-attach in 0.7, #96
- add a README containing instructions for running tests and setting up
optional database backens, #96
|
|
|
|
| |
- its beta
|
| |
|
|
|
|
|
|
| |
file handles are closed.
- PyPy is supported.
|
| |
|
| |
|
|
|
|
|
|
|
| |
- more docs
- get env.py to work in --sql mode even without the DBAPI installed,
using just the URL
- add get_section_option()
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- long lines/whitespace
- fix "list_templates"
- will support py3k immediately
|
|
|
|
| |
- can't import sqlalchemy.test anymore
|
| |
|
|
|
|
| |
- figuring out operation system
|
|
|