[Sqlalchemy-commits] commit/sqlalchemy: 4 new changesets

[Bitbucket <com...@bi...>]

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/4e8f8d549906/
Changeset:   4e8f8d549906
Branch:      None
User:        zzzeek
Date:        2014-03-03 20:44:52
Summary:     - fix oracle failures here due to mis-ordering

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/15866e58e206/
Changeset:   15866e58e206
Branch:      None
User:        zzzeek
Date:        2014-03-03 21:43:46
Summary:     - documentation and changelog

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/5793d7ff4791/
Changeset:   5793d7ff4791
Branch:      multi_db_tests
User:        zzzeek
Date:        2014-03-03 21:44:41
Summary:     edit

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/ea05a2321819/
Changeset:   ea05a2321819
Branch:      None
User:        zzzeek
Date:        2014-03-03 21:55:17
Summary:     - Support has been added for pytest to run tests.   This runner
is currently being supported in addition to nose, and will likely
be preferred to nose going forward.   The nose plugin system used
by SQLAlchemy has been split out so that it works under pytest as
well.  There are no plans to drop support for nose at the moment
and we hope that the test suite itself can continue to remain as
agnostic of testing platform as possible.  See the file
README.unittests.rst for updated information on running tests
with pytest.

The test plugin system has also been enhanced to support running
tests against mutiple database URLs at once, by specifying the ``--db``
and/or ``--dburi`` flags multiple times.  This does not run the entire test
suite for each database, but instead allows test cases that are specific
to certain backends make use of that backend as the test is run.
When using pytest as the test runner, the system will also run
specific test suites multiple times, once for each database, particularly
those tests within the "dialect suite".   The plan is that the enhanced
system will also be used by Alembic, and allow Alembic to run
migration operation tests against multiple backends in one run, including
third-party backends not included within Alembic itself.
Third party dialects and extensions are also encouraged to standardize
on SQLAlchemy's test suite as a basis; see the file README.dialects.rst
for background on building out from SQLAlchemy's test platform.

Affected #:  47 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.