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
Change-Id: I1e206c4e9611c90438de842bbc1cb9af6cbc21cc
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
Signed-off-by: Takashi Natsume <takanattie@gmail.com>
Change-Id: I216ef60919713cd397c8a46146339d144930e40b
These translation sections are not needed anymore, Babel can
generate translation files without them.
Change-Id: I6bcedbda2940dd76df8b6de4038ef0b3a40f16b7
This change removes the requirement for python 2 and removes testing for
it, but tries to leave the code compatible with python2 where possible.
Co-Authored-By: Nate Johnston <nate.johnston@redhat.com>
Change-Id: I711ae939b5eaa1816af15b22527c38858507127f
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and
dropping unit tests for Python 3.5. Using the Zuul template for Train
will ensure that all projects that support Python3 will be tested
against the agreed runtime versions, and make it easier to update them
in future.
Specifically this patch:
- Uses the openstack-python3-train-jobs zuul template rather than
templates for python 36/37.
- Adds Python 3.7 to the setup.cfg classifier.
- Adds py37 to the envlist of tox.ini.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I92e07412e06d5e0bcd4a3ef63643d140243f8205
Depends-On: https://review.opendev.org/#/c/641878/
By default setuptools produces a version-specific wheel file so
installation under other versions of Python require extra work at
install time. This change turns on "universal" wheel support, so that
the wheel file will be marked as supporting both Python 2 and 3.
Change-Id: I00bc3d736e87bcc3a122b688c5e10e82b1b03d84
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
policy-in-code will be supported by the main neutron repo
because the neutron API layer uses the policy code in the neutron repo.
However, neutron_lib.context refers to its own policy enforcer,
so we need a small code to support policy-in-code in neutron-lib side.
Part of blueprint get-policy-from-neutron-lib
Change-Id: I4923a069f4080dc53a8fb359f5a1518de06feb2f
The command to build docs is updated to match that run in the gate.
The previous command is to ensure no warning, but sphinx 1.5 or later
has warning-is-error option and there is no need to run a different
command in tox docs target.
Change-Id: Ieac8afd096a158aff6403326104ced31adcb77e1
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: I9701f7ac1551dc60f0f75f64a322a6841108dfe2
Python 3.3 is not supported from Mitaka, as per Infra.
This patch removes the support for the same.
Change-Id: I4554f8f7510aea4e3bf66fa68f62d43140112d09
Now that there is a passing gate job, we can claim support
for Python 3.5 in the classifier. This patch adds the
convenience py35 venv.
Change-Id: I78adc9d836059fe9a2e8d1010408dd440d9d620e
This patch updates our hacking checks as follows:
- Hacking checks are now registered via entry points so
they can be used via flake8 CLI. By default they are disabled.
Hacking check doc string is also updated to support pep8
parsing of check code.
- The existing hacking.checks.factory() is moved to a more
meaningful name; marking as deprecated.
- A private neutron-lib specific hacking check factory is provided
and used in tox.ini.
- A flake8 plugin is provided that supports the ability to use our
hacking check factory functions to enable a pre-existing check
by default.
- Our usage of hacking checks is updated to reflect our consumption
model for adopters.
- Unit tests are provided.
Change-Id: I88dad7f7cce4d4f5af679272f067c3bb4a73803a
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
neutron-lib/locale/neutron-lib.pot to
neutron_lib/locale/neutron_lib.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 file, the updated scripts work without them. So, we can just
delete the file and once there are translations, an updated pot file
together with translations can be imported automatically.
Change-Id: I73db7b37f5a44ae45c01ca16abccb41a5fbfbfe8
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: I4223ec5ffd3770ef90e23cd8f84341097c1fe84f
Ghanshyam Mann