- test py36

- Current mysqlclient does not accept "bytes" on py3k, SQLAlchemy 0.9
still lists this client (the original mysqldb version) as
"supports_unicode_statements=False" so is no longer functional on py3k.
- Rollback transaction after table drop; it seems py3.6 sqlite3
suddenly turned on transactional DDL for SQLite

Change-Id: Ic3b7881583bde5602e54811cf6a149761038b9fd
This commit is contained in:
Mike Bayer 2017-01-11 10:29:57 -05:00
parent c5ac1cddd6
commit a0d6ab0385
2 changed files with 5 additions and 2 deletions

View File

@ -35,8 +35,8 @@ class TestMigrationContext(TestBase):
self.transaction = self.connection.begin()
def tearDown(self):
version_table.drop(self.connection, checkfirst=True)
self.transaction.rollback()
version_table.drop(self.connection, checkfirst=True)
self.connection.close()
def make_one(self, **kwargs):

View File

@ -1,6 +1,9 @@
[tox]
minversion=1.8.dev1
envlist = py{27,33,34,35}-sqla{09,10,11}, py{27}-sqla{079,084}
# current mysqlclient fails with <=SQLA 0.9 on py3k due to
# old unicode statements flag
envlist = py{27,33,34,35,36}-sqla{10,11}, py{27}-sqla{079,084,09}
SQLA_REPO = {env:SQLA_REPO:git+http://git.sqlalchemy.org/sqlalchemy.git}