Move runtime test resources into setup.cfg [extras]
testscenarios and testresources are only needed if you're using the oslo.db testing fixtures downstream, otherwise you don't need this at runtime in a deployment, so move them into the setup.cfg [extras] group. If a consumer of oslo.db wants to use the db test fixtures then they install oslo.db like 'sudo pip install oslo.db[fixtures]'. This should trigger a major version bump for the library when it lands. Closes-Bug: #1429233 Change-Id: I1a7c5b6a7b29cd3a50655f60606cc0b025400a96
This commit is contained in:
parent
15e905093e
commit
30cb737256
|
@ -14,5 +14,3 @@ SQLAlchemy<1.1.0,>=0.9.7
|
|||
sqlalchemy-migrate>=0.9.6
|
||||
stevedore>=1.5.0 # Apache-2.0
|
||||
six>=1.9.0
|
||||
testresources>=0.2.4
|
||||
testscenarios>=0.4
|
||||
|
|
|
@ -54,6 +54,11 @@ keywords = _ gettext ngettext l_ lazy_gettext
|
|||
mapping_file = babel.cfg
|
||||
output_file = oslo.db/locale/oslo.db.pot
|
||||
|
||||
[extras]
|
||||
fixtures =
|
||||
testresources>=0.2.4
|
||||
testscenarios>=0.4
|
||||
|
||||
[pbr]
|
||||
# NOTE(viktors): uncomment ``warnerrors`` line, when setup.cfg we then
|
||||
# want to treat sphinx warnings as errors
|
||||
|
|
Loading…
Reference in New Issue