The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Ib4184a05e753c3d1368167b91fc43bcc64a176c3
pyScss v1.3.6 is released with setuptools fix.
There is no need to blacklist setuptools 46.0.0 now,
so commit a8ff45ade2 is also reverted.
Change-Id: Ia8b27922f3354d42f62538ddee3ed5044968556d
setuptools 46.0.0 contradicts pyScss 1.3.4 because 'Feature' were deprecated.
Please see https://github.com/pypa/setuptools/issues/2017
Change-Id: Iafab38336daf5d84ef9e19248b59adccfacc29ec
keyring drops py2 support so lets ensure our requirements wont allow us
to install 19.X releases on py2.
scikit-learn drops support for 3.4 or lower with release 0.21.0.
Setting the minimum supported python for both to 3.4 to be consistent
with u-c. When we remove the 3.4 constraints we'll also need to fix g-r
Similarly sphinx 2.0.0 drop py27 support do express that in
global-requirements.
There isn't a need to update u-c as they're already correct:
$ grep -E '^(Sphinx|keyring)' upper-constraints.txt
keyring===18.0.1;python_version=='2.7'
keyring===19.0.1;python_version=='3.4'
keyring===19.0.1;python_version=='3.5'
keyring===19.0.1;python_version=='3.6'
Sphinx===1.8.5;python_version=='2.7'
Sphinx===2.0.1;python_version=='3.4'
Sphinx===2.0.1;python_version=='3.5'
Sphinx===2.0.1;python_version=='3.6'
This may cause knock-on effects for projects using either of these in
lower-constraints, but that's less impactful than all the 'red' in the
gate right now
Also 'correct' the Sphinx requirement in test-requirements so we get the
correct version when running under python2. We need to do this anyway as
docs jobs typically run unconstrained
Change-Id: If558f184c959e4b63b56dec3ca1571d1034cfe5c
When the TC merged I2637dd714cbb6d38ef8b8dc1083e359207118284 we're
supposed to invoke stestr rather than testr so lets do that
Change-Id: Ic5b984949462e9d96d0ba122531d7f0a3d733891
Listing hacking in test-requirements is deprecated, as
it is a blacklisted linter and the global requirements update
bot wouldn't update it anyway. Instead use it just as a
dep on the pep8 tox env.
Change-Id: Idb4bcd8e4ffe1738a7306f9e1e5530b7e1e8dc8f
Add a bashate environment for checking shell code quality.
Exclude bashate warnings:
E006: Line too long:
E010: The "do" should be on same line as for
In my opinion the places that trip these do not impact code readability
Change-Id: Iab0a34542c3938f127515291eca8f027f3accaa0
Use openstackdocstheme instead of obsolete oslosphinx.
Fix display problem with removing extraneous whitespace in README.rst.
Change-Id: I791e830c6a13476152fb26a95de6832a6c50adae
In change I38580a5f765c7bb586dcf2786e91be15a8eba235 we skipped one of the
docutils versions due to a breaking release that was not supported by
sphinx. This has now been fixed in the latter[0].
With Sphinx 1.5.1, the blocking of docutils 0.13.1 is not needed
anymore, so remove the condition. This line could be removed completely,
but for that it first needs to be removed from all projects.
[0] https://github.com/sphinx-doc/sphinx/issues/3212
Change-Id: I01b7b6f3fac75e284debe211129b7b1e87c756d9
Hacking checks are not automatically pushed out via the OpenStack
proposal bot. This change allows for a more modern version of
hacking.
Change-Id: Iffa8f959da8ebed1ca0ffc355f22054d2a6b37da
The 0.13.1 release breaks some documentation jobs when it tries to build
docs with remote images. This has been reported upstream[0]. The version
matches the supported docutils versions for sphinx.
[0] https://sourceforge.net/p/docutils/bugs/301/
Change-Id: I38580a5f765c7bb586dcf2786e91be15a8eba235
Move packaging and pyyaml from test-requirement.txt to requirements.txt.
Also add requests as it's needed by validate-projects
This is needed as some projects in the gate are pip installing the
requiremets repo and now they're failing with runtime errors.
Change-Id: Ic88cecd6d2664e447a696c58c123de18f35f7cd2
If you mistakenly pass a path that isn't a directory, or doens't exist,
you get a traceback that ends with:
---
File "/Users/tony8129/projects/openstack/openstack/requirements/openstack_requirements/cmds/update.py", line 229, in _copy_requires
dest_path, project.merge_setup_cfg(proj['setup.cfg'], output_extras)))
KeyError: 'setup.cfg'
ERROR: InvocationError: '.../openstack/requirements/.tox/update/bin/update-requirements -H -s ./nova'
---
This is a little confusing. This patch checks that the arg is a
directory so a more explicit error can be generated.
Change-Id: I9f3f43d5c9b90746bbf2d651ee4cb37afade1528
Add a command and tox environment to let us define a job to ensure that
all repos in projects.txt have the check-requirements job defined. Two
projects are missing the job now, so this patch depends on the patch to
add those jobs.
Change-Id: I61658a7265a77e72401978dda558f41b28a81d92
Depends-On: I81e1c70257e28583e776171580d75341e620bf8d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Since this is now published on
docs.openstack.org/developer/requirements/ , update theme to use
OpenStack branding.
Include the oslosphinx extension, rename base names from DevStack to
requirements.
Change-Id: Icedd2bbce155b4667c6fe205ca61b9f707a1a8b5
Add a simple doc publisher target that just includes the existing
README.
Some of the infra jobs that fail requirements try to point you to the
requirements documentation; currently this is given as a raw RST link
to the web-view of the git tree. It would be nicer to publish this as
formatted HTML like all the other docs.
Change-Id: I56b60a950c64880dd551d11e1997cd5ecbae283c
Hervé Beraud