As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: If7467b704270d1d98226e5cbaa903d4713e63c1d
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Add release notes and update the python
classifier for the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>
Change-Id: I0f9d7f3cd2309bc52ec95ba642b22140ac691654
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: I5b94727986da22c5cfc56a939ff3c4a14f009d2a
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: Idfa3b9d4d41a3cb456fe9f24872dd6cdd17299bf
This repo is now testing only with Python 3, so let's 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
- Update classifiers
- Update requirements, no need for python_version anymore
- Use newer openstackdocstheme and Sphinx versions
- Cleanup */source/conf.py to remove now obsolete content.
- Remove Babel from requirements, it's not needed for running.
- Update hacking to 3.0, fix problems found
Change-Id: I9eb22328474f52c2e225ae2a24c895c0e2bb63d7
Also turn on warning-is-error for the sphinx build.
Change-Id: I4a839924212fde7e6ae31a87ea8a0c6cf45313e9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Python 3.3 is not supported from Mitaka, as per Infra.
This patch removes the support and update to py35
for the same. Updated in venv also.
Change-Id: Ida50a9b6415cfc19bdbe37b3f6a60dc4c7aca73a
Follow new infra setup for translations, see spec
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
for full details.
Prepare babel-django.cfg qnd remove babel.cfg.
This repository is django related. So, follow Django repos convention in OpenStack.
This basically renames
designate-dashboard/locale/designate-dashboard.pot to
designatedashboard/locale/django.pot to follow Django POT file convention.
setup.cfg babel entries are kept as this repository has
only python files and it still works, they have been updated for new
setup.
Change-Id: I388c6b92b9e9d7a0c9d7b81b4c495a65088e4856
As of mitaka, the infra team won't have the resources available to
reasonably test py26, also the oslo team is dropping py26 support
from their libraries. sine we rely on oslo for a lot of our work,
and depend on infra for our CI, we should drop py26 support too.
Change-Id: Ia229285086c24bf8e1e52887a0aa513c66e68727
Related-Bug: #1519510
Bump preversion to mark the start of the Mitaka development branch.
The liberty release branch will be cut from the previous commit.
Change-Id: Iff82330e7aa9e493bc294e23302c5c7844183b3e
To start translation, we need to initially import the
translation file - and place it at the proper place so that
the usual CI scripts can handle it.
The proper place is for all python projects
$PROJECT/locale/$PROJECT.pot - see setup.cfg.
Further imports will be done by the OpenStack Proposal bot.
Change-Id: I12910da652c462422915bd7090cde5598754ca14
Ghanshyam Mann