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: I709f3609f52b7d75a0c176d5ecb0704600a00c8b
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: If044570184e1df33c8754a39a782ea94e4ea165f
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)
Also indicates that we support python 3.9.
Change-Id: Ic6dd48a11ae639ad9bc0ebeeffce7483c8bed588
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: Ide75d5a0fb9215a81f0410b6ffa77849463cf888
These translation sections are not needed anymore, Babel can
generate translation files without them.
Change-Id: Ib2b1a9bd05148ab6c0a164b4463232b36f423de0
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: I2fd048c0d9bf7d93d6c7c515056abe7287019974
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
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
Change-Id: I2c59ca525fa329b91720149cff3faee00fafff97
openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss
Change-Id: I078a42e74409de8068b78e2e3e644b696070c3ac
With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as
errors is setting warning-is-error in build_sphinx section. Migrate
the setting from the old warnerrors one.
Change-Id: If31f68a80ab9e490dbf1457c274ac9f0c78239c4
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: I0f71ce22b44cdb59340f4101c60c507367842603
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.service/locale/oslo.service.pot to
oslo_service/locale/oslo_service.pot. For this we need to update
setup.cfg.
Update also domain name in i18n.py.
The project has no translations currently, let's remove the outdated
pot files, the updated scripts work without them. So, we can just
delete the files and once there are translations, an updated pot file
together with translations can be imported automatically.
Change-Id: I4bbe492faee1c04ede16b3a4e9da2a9521eecccd
We have decided to remove Python 2.6 support, this commit
removes Python 2.6 classifier before dropping any Python
2.6 support in code.
Change-Id: I3f93645b3ad29f3793af5bd26338153e67d5ac5f
the current value is launchpad url which is not
relevant value and is replaced with oslo wiki page
Change-Id: Id67c74a7f6f0615d4c2ac824cfbf7e858c3811cc
Because of copy-pasted wsgi functionality in projects(nova, cinder,
glance, etc.) it is added to oslo.service with perspective to remove
it from other projects.
DocImpact
Change-Id: If8840168f10cc3561f4f01e6d456d6b4fd1de8b5
It is not always desirable to log full set of conf at service
start. This change adds new option "log_options" that allows to
enable or disable logging values of all registered options.
Also moved list_opts function for service submodule to service.py
as service and eventlet_backdoor opts have to be grouped together
and changed the entrypoint accordingly.
Change-Id: I2a97ebf736fd361e6f1d05796d5077bc9627ff85
Closes-Bug: #1461250
oslo-config-generator relies on entrypoints listed
in setup.cfg to add options to the generated sample conf
files in different projects. So expose options avaliable in
oslo.service using the following entrypoints:
* oslo.service.periodic_task
* oslo.service.service
* oslo.service.sslutils
The following commands can be used to generate sample conf:
tox -evenv -- oslo-config-generator --namespace oslo.service.periodic_task
tox -evenv -- oslo-config-generator --namespace oslo.service.service
tox -evenv -- oslo-config-generator --namespace oslo.service.sslutils
bp graduate-oslo-service
Change-Id: I61372047b70341e3536db21aa3f1bd9d99c08185
Ghanshyam Mann