| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
It was causing the release tarball to have an extra ".dev." in its filename,
which then broke the script that uploads the release to PyPI.
Change-Id: I995fb3e0393468568601e8614c0532b93fbe8ceb
|
| |/
|
|
|
|
| |
We don't need this since we're using pbr.
Change-Id: I7c5985fac66d5e7a4fca1b3945a18a364a94e971
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes:
File ".../versioning/version.py", line 30, in __init__
if self < 0:
OverflowError: Python int too large to convert to C long
Don't use __cmp__ which is deprecated and restricted to C
long ints, rather than python's arbitrary precision ints.
Copied from Pádraig Brady's Fedora patch:
http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=a01bf449
Co-authored-by: Pádraig Brady <pbrady@redhat.com>
Change-Id: I71f349f97507525b2f2edaf034005d67b6cc3987
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version 0.8 of SQLAlchemy added support of indexes
on expressions in addition to plain table columns,
which changed the way indexes are created.
This broke support of dropping columns of composite
indexes for SQLite: due to limitations of ALTER in
SQLite every time a column is dropped, we recreate
the whole table without the given column; if a
column is a part of a composite index, we change the
index definition to omit that column and then indexes
are recreated too.
SQLAlchemy versions starting from 0.8 no more pay
attention to 'columns' attribute of Index instances
when generating DDL for indexes, so when one of columns
of a composite index is dropped, we try to create a
new index on the column that doesn't exist anymore,
which of course fails.
Closes-Bug: #1241038
Change-Id: I777b8ce36e36f49bfb0889908811a063cf1a527b
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In addition to running tests with different Python and SQLAlchemy
versions, they should also be run on different DB backends, which
are used in production (PostgreSQL and MySQL).
This patch:
- modifies test_db.cfg to run tests on PostgreSQL and MySQL
(Jenkins Slave credentials are used here, to ensure these
tests are always run by Jenkins gate); if a backend is not
available, test cases will be skipped for it
- concurrency is set to 1 (sharing of the one MySQL or PostgreSQL
DB among different test runner processes would lead to
race conditions)
- fixes tests dropping FK columns in MySQL: in earlier MySQL
versions dropping a column that is a part of a FK constraint
would lead to dropping of the FK too. As of MySQL 5.5 that's
not the case anymore: if one tries to drop such column, he/she
will get a very obscure error (something like "Error on rename
of './openstack_citest/#sql-4af_aa2' to './openstack_citest/tmp_adddropcol'
(errno: 150)") '\nALTER TABLE tmp_adddropcol DROP COLUMN r2').
So the solution if to drop FK constraints first, and only then
the columns it is made up of
Change-Id: I8c5d2874c83e7df46da69969ed54d85437c849e7
|
| |
|
|
|
|
|
|
| |
Update to needing 1.6, which gives us the ability to alter how the
software is installed into the virtualenv. It also brings in pip 1.4,
which lets us avoid getting pre-releases of things we weren't expecting.
Change-Id: I3189f06610d776a032b5f8bf0910f59e4ed45719
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pbr updated itself to remove the d2to1 dependency. One of the main
reasons for this is a direct upstream dependency on distribute, which
causes the distribute/setuptools merge bug to get triggered, which
breaks people's system if they install with pip < 1.4.
Remove d2to1 references, and also bump the required version requested of
pbr to a version late enough to no longer depend on d2to1.
Remove the version specifier from setup.py, because setup_requires has
no way to trigger a version requirement upgrade. The flat version should
be sufficient for the setup.py interface in perpetuity.
Remove the setup-hook from setup.cfg, as it is no longer needed.
Change-Id: I40d3507c77802d13fd894aa16714b2ed6aa7d59f
|
| |
|
|
|
|
|
|
|
|
| |
In commit 0.7.2-16-gc670d1d the _index_identifier() implementation
was copied from sqlalchemy, as that function was renamed
in sqlalchemy 0.8. Instead handle call the renamed function
when appropriate, to decouple ourselves from the sqlalchemy
implementation.
Change-Id: I97b22c20d96758fc5b6bd55318218edb26c5b5d0
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The test suite should be run for all possible combinations
of Python and SQLAlchemy versions we claim to support, which
are Python 2.6 and 2.7 and SQLAlchemy 0.7.x (old stable) and
0.8.x (mainline stable).
py26/py27 tox envs install the latest stable version of SQLAlchemy
(currently, 0.8.x branch), so two additional tox environments added
to run the test suite with SQLAlchemy 0.7.x (for both Python 2.6 and 2.7).
Change-Id: I50c7009d8b808ce3bbb1f0a27c50f5cb5116cdb3
|
| |
|
|
|
|
|
|
| |
pip versions >= 1.4 will not install pytz unless a minimum
version containing a letter is specified (this workaround is
taken from Babel Python library).
Change-Id: Ic013fca82816cd89e446282d3936e38ea2c39274
|
| |
|
|
|
|
|
| |
RTFD only has a single requirements field, so make one that installs the
total set of needed requirements to allow docs to build properly.
Change-Id: I79b8202a6a7944cec052a2431dff670258bf7171
|
| |
|
|
| |
Change-Id: Ib541ac9d6b397300e34ca8b65aad459b612858c3
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
fixes #72
|
| | |
|
| |
|
|
|
| |
excludeTables correctly
Fixes issue 140
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
add build-req.pip with build requirements
|
| |
|
| |
fix issue numbers (use trac issue prefix for pre 0.3 versions)
|
| |
|
| |
update documentation meta data, rewrap index.rst
|
| | |
|
| | |
|
| |
|
| |
use explicit code-block markup
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
(fixes issue 125)
|
| | |
| |
| |
| | |
INSERT happen
|
