Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I416c61dddf1cc5989fa01bb11bbdcc52cddc66a2
UPPER_CONSTRAINTS_FILE is old name and deprecated.
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
For more info. please refer [1].
[1] https://zuul-ci.org/docs/zuul-jobs/python-roles.html#rolevar-tox.tox_constraints_file
Change-Id: Ib606ad3175a55b7884684adad8e2da87fefae0ab
This patch upadte pylint version to 2.6.0 in
test-requirements.txt and wrapt version to 1.11
to fix CI jobs.
Change-Id: Iba2a2321ee2ff459466918150d825c55c2596473
The current job only checks whether the repository can be installed.
It specifies a tempest regex, but it is invalid, and anyway
the tempest tests do not touch horizon and its plugins, so
the job can just inherit from devstack instead of devstack-tempest.
Drop the distribution-specific suffix, ubuntu is the default.
Change-Id: I3d9cc639f5d5f523a1cdf395acacbfd88920e339
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I420adfab0ff40fffd9a211d72ad6c953a495676e
Update to newest hacking version, it has only minimal changes and full
support for Python 3.
Python modules related to coding style checks (listed in blacklist.txt in
openstack/requirements repo) are dropped from lower-constraints.txt
as they are not actually used in tests (other than pep8).
Change-Id: I67f390e6d7b6fb9eeb7522728ba293d3337b3327
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: Id14fccdefc6ec2ed5078eeb0a22f623b16c375c9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Make a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
- Remove unused oslosphinx requirement
Change-Id: I845d02c5fb7cf57beb3628821156bff7310733ca
We don't support python2 anymore so we don't need this compatibility
library.
This patch remove six useage.
Change-Id: Ib2fa617a9c0ea7a21652fee28964fc09600d6d54
Django 1.11 ends its extended support in April 2020 (which is before
Ussuri release), so horizon drops Django 1.11 support in Ussuri.
tox envs for non-primary Django versions are no longer needed in tox.ini
as testing environments for non-primary Django versions are setup in
the zuul jobs now.
horizon>=17.1.0 is required to use Django 2.2. requirements.txt and
lower-constraints.txt are updated accordingly. for more info. please
refer [1].
Depends-On: https://review.opendev.org/#/c/700733/
[1] https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin
Change-Id: I499c5f2fb06caa70c939b6e503f65c14c2c2e474
babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.
This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.
Change-Id: I68b0eecd6b17be0e059fccdbced5784151c0e492
1. Update tox.ini file, add py37 and remove py35 in envlst for UT.
2. Upgrade pylint,astroid,keystoneauth1 version
Change-Id: Ibb7a5ad85343d0ffe5c50d6c72865bce6657ea36
Horizon defined a project template 'horizon-non-primary-django-jobs'
for django jobs. This patch use that template to run django jobs
here. For information please refer [1]
[1] https://review.opendev.org/#/c/681969/
Change-Id: I2a8bc45f838e9dc56ad015c44e034cf5d009d2ab
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I66374a28c0ae20772bde47c785c5a368045e7824