summaryrefslogtreecommitdiff
path: root/test-requirements.txt
Commit message (Collapse)AuthorAgeFilesLines
* Cap jsonschema 3.2.0 as the minimal versionHervé Beraud2020-05-261-1/+1
| | | | | | | | | | | | Previous versions of jsonschema (<3.2.0) doesn't support python 3.8 [1]. Python 3.8 is part of the victoria supported runtimes [2] so we now force to use jsonschema version 3.2.0 to avoid issues, remove ambiguity and ensure that everything works with python 3 in general. [1] https://github.com/Julian/jsonschema/pull/627 [2] https://governance.openstack.org/tc/reference/runtimes/victoria.html#python-runtimes-for-victoria Change-Id: I8e91b4b19d6d71e052061074ad927623a2892830
* Use unittest.mock instead of third party mockussuri-em2.1.0Sean McGinnis2020-03-131-1/+0
| | | | | | | | Now that we no longer support py27, we can use the standard library unittest.mock module instead of the third party mock lib. Change-Id: Ieb1746b1ad7571cb87f5b1e7a6876ce72e6b76c3 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* Uncap jsonschemaSean McGinnis2020-03-131-1/+1
| | | | | | | | jsonschema was uncapped in the global requirements. We need to uncap it locally now too. Change-Id: Ia6ad2c7e62aebc81386610e9d16c8bb8a162d70f Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
* Update hacking versionjacky062019-03-061-1/+1
| | | | | | Use latest release 1.1.0 and compatible changes w.r.t pep8 Change-Id: I360c621d313b76bf88e91ff8be9e759d8367c847
* Updated from global requirementsOpenStack Proposal Bot2018-01-311-1/+1
| | | | Change-Id: I6f0d1ff2c139d77511937326d0d050135b97e0e2
* Split docs requirements and update tox.iniMonty Taylor2018-01-311-5/+1
| | | | | | Get ourselves up to date with the latest in PTI hotness. Change-Id: Ied98273dcfa0b9622d603a8e9a8e2146fb1e081f
* Updated from global requirementsOpenStack Proposal Bot2017-12-051-3/+3
| | | | Change-Id: I760104d4a94f67da4677e1ecf8f47150605d4d33
* Updated from global requirementsOpenStack Proposal Bot2017-09-161-1/+1
| | | | Change-Id: I1bbda934cc65d508f1cece8c5adc714e9f464707
* Updated from global requirementsOpenStack Proposal Bot2017-09-131-2/+2
| | | | Change-Id: I6ecb4e80d2944bf592a2cbd41695643bc49f832d
* Updated from global requirementsOpenStack Proposal Bot2017-08-181-2/+2
| | | | Change-Id: I805c30c0a522c03721a97118594030b9c8dfcd51
* Updated from global requirementsOpenStack Proposal Bot2017-08-121-1/+1
| | | | Change-Id: Iad6eba535f48d0f09e5507db32399623f63a4f88
* Updated from global requirementsOpenStack Proposal Bot2017-07-271-1/+1
| | | | Change-Id: I611163aecdc4810e6fd1d7e47e60171d72db0ea3
* Manually sync with g-rDirk Mueller2017-07-241-15/+15
| | | | Change-Id: I4298bb7c2d66632b716b0dbeae64c9dca2b3434d
* switch from oslosphinx to openstackdocsthemeDoug Hellmann2017-06-221-1/+1
| | | | | Change-Id: Ie45909df0b5a118d0200a1ee71277f4dbfe41d08 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
* Merge "modify test-requirement according to requirements project"Jenkins2017-03-091-3/+3
|\
| * modify test-requirement according to requirements projectxhzhf2017-03-091-3/+3
| | | | | | | | | | | | | | | | | | | | the OpenStack requirements project has modify version requirement of docutils/oslosphinx. The link is below https://review.openstack.org/#/c/418772/ So modify test-requirement like other project Closes-Bug: #1666149 Change-Id: I145ba596926cac0efab75fb4a1548eea338a2d5a
* | Merge "Remove the keystoneclient auth fallback"Jenkins2017-03-041-1/+0
|\ \
| * | Remove the keystoneclient auth fallbackMonty Taylor2017-02-151-1/+0
| |/ | | | | | | | | | | | | OSC doesn't use this codepath anyway (to my knowledge) and it masks errors in exceptionally strange ways. Change-Id: I15ec5aacb037813a98ac9ea8e9504a5d1cc90837
* | [Fix gate]Update test requirementricolin2017-03-021-1/+1
|/ | | | | | | | | Since pbr already landed and the old version of hacking seems not work very well with pbr>=2, we should update it to match global requirement. Partial-Bug: #1668848 Change-Id: I09ae994782889aae05250a8e5bf9f5b630b2d502
* Add docutils contraint on 0.13.1 to fix buildingSteve Martinelli2016-12-151-0/+1
| | | | | | | See: http://lists.openstack.org/pipermail/openstack-dev/2016-December/108742.html Change-Id: Id183b0d3a6339e10f2f1f4a5dc78352d5c3f27ed
* Remove discover from test-requirements.txtThomas Bechtold2016-04-111-1/+0
| | | | | | | discover is only needed for python 2.6 which is no longer supported. Change-Id: I8faeb05def94ac4adb2fe870fe141678dbd412ae
* Clean up removed hacking rule from [flake8] ignore listsLiuNanke2016-01-191-1/+1
| | | | | | | | | | | | | | | We bump hacking>=0.10.2, and hacking removed some rules, for the full list of rules please see [1]. So don't need them any more. Hacking related commits: Remove H904 in commit b1fe19ebebe47a36b905d709467f5e82521bbd96 Remove H803 in commit f01ce4fd822546cbd52a0aedc49184bddbfe1b10 Remove H307 in commit ec4833b206c23b0b6f9c6b101c70ab925a5e9c67 Remove H305 in commit 8f1fcbdb9aa4fc61349e5e879153c722195b1233 [1]https://github.com/openstack-dev/hacking/blob/master/setup.cfg#L30 Change-Id: I24b82c1913d3d42cc5228b1db700b787623fcdc5
* Use reno for release notesMonty Taylor2015-12-301-0/+1
| | | | | | | | The OpenStack Release team has created a great release notes management tool that integrates with Sphinx. Start using it. For reference on how to use it, see http://docs.openstack.org/developer/reno/ Change-Id: I8153ec7861b508297a28a1916771776dee2deafe
* Add methods for getting Session and Client objectsMonty Taylor2015-11-031-0/+2
| | | | | | | | | These come originally from the shade library, but are helpful for things like the client libs themselves. Once one has a CloudConfig, there is really one and only one correct way to get both a session and a Client. Change-Id: I1b4d4321828864fddab85a127fbf63f4c8384ab9
* Use json for in-tree cloud dataMonty Taylor2015-11-031-0/+1
| | | | | | | | | | | | | | In preparation for sharing the default and vendor data with other projects, potentially even non-python ones, move the data into json format, which is slighly less exciting to read, but has more widespread standard library support. The user-facing config file will still be in yaml format, because that's easier on the eyes and it's expected to be read and edited by humans. Continue to accept yaml everywhere, because an end user may have dropped a yaml config file into a dir somewhere, and that's fine. Change-Id: I269d31e61da433ac20abb39acdde0f9f9fe12837
* Add keystoneclient to test-requirementsMonty Taylor2015-04-111-5/+6
| | | | | | | | | | The auth parameter name validation requires keystoneclient and can't be tested if it's not there. While we're at it - update the current requirements to be inline with global requirements. Change-Id: I6da62476f3851670545143184f9f29479f1caaca
* More comprehensive unit tests for os-client-configClint Byrum2015-02-271-0/+2
| | | | | | This includes ensuring that yaml of a sane format can be loaded. Change-Id: I698b3139b7e44f000d2a413d17e79914ef542a22
* Remove babel and add pyyamlMonty Taylor2014-09-211-1/+1
|
* Initial Cookiecutter Commit.Monty Taylor2014-09-201-0/+15
View Lorry Controller Status