As per the current release tested runtime, we
need to test python 3.8 to python 3.11 so using the
generic python testing template which run the python
versions jobs as per the current release runtime.
Also, updating the same in python classifier in setup.cfg
Change-Id: I8db58eb19a9e39067e8102df81a647450b2c1cf9
In the Zed cycle, we have dropped the Python 3.6/3.7 [1] testing and its
support. Update the Python classifiers to reflect this.
Change-Id: Ieb80faf01d87e7fa7d717b74de6c5ec518ef9b05
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
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: Icccc9cc2b3a0d236746c4b58a8815d25d8b0a443
cliff is used by stestr which is used by more things than just
openstack projects - one of them being zuul which still supports
python 3.5. Let's keep supporting 3.5 here for now.
Change-Id: I14fca07853677d041215649cb55caf1e0dc49753
Put these in place as a setup for the new versions of the doc build
jobs. Keep using them from the normal dep list until the jobs are
changed.
While we're here, update the docs env to use sphinx-build instead of
python setup.py build_sphinx. Also add python2.7 to the docs env, since
I accidentally tried building it with my python3 tox and it blew up
substantially.
Change-Id: I0fcc50c4c396758e839c329ce786a6f609bb1342
Remove the dependency on the demoapp and just add it to the import
path so it is available to be imported. Copy the entry point settings
into the main cliff setup.cfg to ensure they are registered for the
doc build to find.
Change-Id: I390410bc5247e8b6c8d0a8fec8e7ecb223d8d6c1
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This ensures requirements bot recognizes existing entries in the
section and doesn't add duplicate requirements as it happened in
https://review.openstack.org/#/c/494775
Change-Id: I33af866e1dea650cd913e08bd3eff4b5bc09bb13
cliff is a library that is used outside of OpenStack, too. Having
a build requirement that needs something OpenStack specific makes
life in cases (eg. for downstream packagers) more difficult.
So let's make openstackdocstheme an optional requirement.
Change-Id: I0f94a431be083b8b4baec850b1885ba07b5bf5c2
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: I0af218e58e32a06b7bd9cef661fc75f801689323
The gating on python 3.4 is restricted to <= Mitaka. This is due
to the change from Ubuntu Trusty to Xenial, where only python3.5
is available. There is no need to continue to keep these settings.
Change-Id: I8fc96da9fcbdebdbd71491b7115e65a1e67bd252
Now that there is a passing gate job, we can claim
support for Python 3.5 in the classifier.
This patch also adds the convenience py35 venv.
Change-Id: Ia67e5efb2deb62942914b31d04f217308d0be304
This change replaces the cliff-tablib json formatter with an internal
replacement. It differs from the tablib formatter in the following ways:
- by default outputs with an indent of 2 spaces. The --noindent formatting
argument outputs with no indentation, to save space or to pipe to tools
which can't handle multi-line input.
- emit_one serialises a simple dict where the column name is the key
and the data item is the value (rather than a list of dicts with
'Field' and 'Value' keys)
The cliff release which contains this change will need a corresponding
cliff-tablib release which removes the json formatter from its setup.py
entry_points.
Change-Id: I7f9b1f339d96ead347a0c9d95ec7004a78d8c9d5
Related-Bug: #1308744
This change replaces the cliff-tablib yaml formatter with an internal
replacement. It differs from the tablib formatter in the following ways:
- always outputs with block formatting rather than the PyYAML default
of deciding based on value content
- emit_one serialises a simple dict where the column name is the key
and the data item is the value (rather than a list of dicts with
'Field' and 'Value' keys)
- emit_one preserves column order by printing a single-item dict for
each column_name
The cliff release which contains this change will need a corresponding
cliff-tablib release which removes the yaml formatter from its setup.py
entry_points.
Change-Id: I691dbab3dee7c5ec28b1083f87ab1f5c051d582b
Related-Bug: #1308744
The value format for the show command is very handy for shell
scripting and a value format for the list command would be just
as handy. It will allow command substitution and piping like:
os container list --format value | grep tmp | while read NAME
do
os container delete $NAME
done
Change-Id: If9784c27d689073e9145b2cb8077ac604025a4c3
Move the requirements definitions and documentation files to the
standard places used by other OpenStack projects so our doc publishing
jobs will work.
Remove the todo extension and all todo items from the documentation.
Change-Id: Iea630d827976fe517afacf4e373b3a125efff9c9
It may be useful to have a value only output formatter to perform operationgs like:
TOKEN=$(openstack token create -c id -f value)
Rather than:
eval $(openstack token create -c id -f shell)
TOKEN="${id}"
Change-Id: I7bda3cc1a1d154a05e8e31eed564dae1e82066d6
Closes-Bug: #1292578
Ghanshyam Mann