We also remove these unnecessary linter dependencies from
test-requirements.txt.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Icf2296c1ad1548ffe8be0610800f1c6c5d33c473
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I1dfb59aaccbc50deda08863007536c46f4445a44
Within 2023.2 python version 3.9 and 3.10 are the
supported python runtimes [1].
[1] https: //review.opendev.org/c/openstack/governance/+/872232
Change-Id: I45f418ea67bd24a91ec0ca1989b7c54b234a2242
In Zed cycle testing runtime, we are targetting to drop the
python 3.6/3.7 support, project started adding python 3.8 as minimum,
example nova:
- 56b5aed08c/setup.cfg (L13)
Change-Id: Ia82c3c5e8d16fa9d111430a57588e49ab512775a
... so that the middleware can be loaded using the python egg instead
of the direct path.
Closes-Bug: #1940738
Change-Id: I57408766c120d2c9784f3886457e91ee7d30de1b
... so that its options can be rendered by oslo-config-generator by
adding the entry point.
This change also updates the base oslo.middleware entry point to
include options of the middleware because the base entry point is
supposed to include all options in the oslo.middleware library.
Closes-Bug: #1940747
Change-Id: Ic9d79d9c46fc1dc78aa4d089e36219b2a34f4099
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: Ic9487a052e549a91fcf09b94e5fae525548f8d68
These translation sections are not needed anymore, Babel can
generate translation files without them.
Change-Id: I39beb972383622d4c4a3b17cb9c3d30674bca5bc
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: I568967e4ae45a47bb625d9ed8b172e56d58d78ac
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Update classifiers
- Use newer openstackdocstheme version
- Switch to hacking 3.0, fix problems found
Change-Id: I539b00204279c7645ef4a3f804f64a1e7af30f05
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: Idd212417ed7c8fbf715bfca0179e5220fbc73901
This change removes the now unused "warnerrors" setting,
which is replaced by "warning-is-error" in sphinx
releases >= 1.5 [1].
[1] http://lists.openstack.org/pipermail/openstack-dev/
2017-March/113085.html
Change-Id: If356e8bfd2ff414037a8688409798b13044fe3b2
Now that there exists only a gate job for Python 3.5 and not 3.4,
we should remove those references to the 3.4 that is untested.
Change-Id: I6264d7d2e1d97291b58b4358f3c397c1fbc320ac
The healthcheck middleware has actually wrongly been designed as a
filter, whereas it is its own application.
This patch fixes that by exporting the healthcheck middleware as an
application, while keeping the old behaviour for compatibility with
existing deployment.
Change-Id: I1ff43c71449f1955267faf6a85f4d70f705db097
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: I73178227e44caee792e6f7e4f4ddf4cfb07e096d
It is standard practice in oslo.middleware to allow configuration via
both the paste file and the oslo.config file. Projects such as keystone
don't allow shipping default configuration in the paste.ini files.
Use the configuration methods provided by the existing base middleware
to allow configuing via oslo.config and register the sample options
available for the middleware.
Closes-Bug: #1634329
Change-Id: I33b7b1f9d945280265eb3b712cb85a2d66616c17
Allow sample config generators to retrieve the options for the
http-proxy-to-wsgi middleware.
Change-Id: I862c9238b791098c9bb9ce4558db5b21dad14a30
Closes-Bug: #1590218
Follow new infra setup for translations, see spec
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
for full details.
This basically renames
oslo.middleware/locale/oslo.middleware.pot to
oslo_middleware/locale/oslo_middleware.pot. For this we need to update
setup.cfg.
Update also domain name in i18n.py.
Change-Id: I5d9c146d6bc9392930c93414c04dda89c16044c1
Short Story:
If we don't do this then we have to drop,
assert:support-upgrade from nova (Really Really Bad!)
Longer Story:
We need to support kilo paste-ini until liberty-eol per policies
already in place. To do that an alternative would have been
to cap global-requirements, but that got ruled out, please
see work and reasons here:
I5731b0278e266699fe716733b6dd4f7238a35586
There's also another new spec openstack-specs that is gathering
a lot of positive votes regarding backward compat:
I72e4e9cfa0539f6b326a0296c065fa3cb754f8ae
Note that this is not a straight revert of:
I1479f37f500a358cdf7ad416f0257288b65c9245
As i just want to drop the tests and keep the files to a
minimum. The grenade job is enough to test the older
scenario (which was failing) which we need to support.
Change-Id: I04739bc3987786b4bc1fefc70fabaa69b3de52b4
Closes-Bug: 1524404
Define filter factories so other projects can reference them by name
and can take advantage of the python egg instead of referencing
by the direct path.
Change-Id: Id05c319c1d19261618471fa75983cf8020fc60b6
Closes-Bug: 1500509
Since most openstack applications do not run on a single
port it is useful to be able to have a single healthcheck
plugin that can respond to requests for different ports with
different files; this way for example keystone admin port can
be disabled while its public port can be kept active (without
having to run two different applications, one for the admin
endpoint and one for the public endpoint).
Change-Id: I0bafb5a2091e54c9f01f24812438296b75afaf63
Create separate option discovery functions for each piece of middleware,
so an application that only uses one piece can include only those
options in its sample configuration file.
Test the results with some unit tests that simply ensure the functions
do not raise exceptions, and by adding configuration options to the
documentation for the library, using the new integration of oslo.config
with sphinx.
Change-Id: I4c777cd70c063441f430c48ab1f9c9cac2c1fc75
Similar to the previous fix, this change ensures that all of the
contents of the library are packaged when the .git repository is not
present.
Change-Id: I125ca872b1784dc389594b59f035cd24b1435c9f
Move the public API out of oslo.middleware to oslo_middleware. Retain
the ability to import from the old namespace package for backwards
compatibility for this release cycle.
bp/drop-namespace-packages
Change-Id: If88c65c82b64f096a02f7ec62e019aea4de2f9d3
Universal is used to identify pure-Python module(by bdist_wheel). For
these, it is sufficient to build a wheel with _any_ Python ABI version
and publish that to PyPI (by whatever means).
Change-Id: I99b5c30b7d7feb00eed1c9b4c7c8a0df4e41da84
* Adding a group name to prevent collision with keystone
middleware library option
* Adds an opts module for the config generator to use.
* Makes the option in sizelimit private since we don't want consumers
using them directly.
* Moves the options to an oslo_middleware group with appropriate
deprecated_opts settings to keep existing configs working.
Closes-Bug: #1368490
Change-Id: I72263bd363a79275a314de727a04277276866565
Ensure each exported class has a docstring.
Add API to the sphinx docs.
Fix a few formatting issues so the rendered docs look OK.
Change-Id: Ieef7bae3783a084249169fe9b80ab17518eee15f
Stephen Finucane