
keystoneauth is a little special in the world, in that it's an user facing library and takes pride in staying compatible. As such it doesn't change much, so the likelihood that patches will land that break python3.5 is really low in the first place. Although the overall openstack python3 support goal puts a min of python3.6 - which is a great choice, keystoneauth has a big user, OpenStackSDK, that is keeping python3.5 because OpenStackSDK has a big user - Zuul, that still supports python3.5. To be friendly to everyone, keep the py35 unit tests just to make sure nobody lands f-strings or anything. Once Zuul drops python3.5 we can circle back around and drop it here too. Remove openstackdocstheme from test-requirements.txt. It only needs to be in doc/requirements.txt. Change-Id: If380bbf77b757655b1dc55322f4636ef83986fe5
26 lines
802 B
Plaintext
26 lines
802 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
hacking>=3.0,<3.1.0 # Apache-2.0
|
|
flake8-docstrings==0.2.1.post1 # MIT
|
|
flake8-import-order>=0.17.1 #LGPLv3
|
|
|
|
bandit<1.6.0,>=1.1.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0.0 # BSD
|
|
oslo.config>=5.2.0 # Apache-2.0
|
|
oslo.utils>=3.33.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
betamax>=0.7.0 # Apache-2.0
|
|
reno>=2.5.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
PyYAML>=3.12 # MIT
|
|
requests-kerberos>=0.8.0 # ISC
|
|
lxml!=3.7.0,>=3.4.1 # BSD
|
|
oauthlib>=0.6.2 # BSD
|