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: I3b36090f6d8e0d710803873951b5b5f0cae14af3
This resolves a warning in recent versions of pip.
Change-Id: I13314917c3f21d7752bdbc3cb869f3e022daa25f
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
As os-resource-classes is branchless which means same
master code is run on stable branches too, let's test it
with all the python version supported in those stable branches.
For that, we need to explicitly add the pythn jobs instead of using
the release specific job template. This way, we will explicitly know
that we are testing all supported python versions and do not remove the
older py version testing when the new release template bumps the min python
version like done in Yoga.
In Yoga testing, we are making py3.9 job to run as voting, so
adding py3.9 job as voting.
Change-Id: Ic93f1c77230d859713ea9bc86065880efa91de7c
This will prevent setuptools accidentally installing os-traits in a
Python 2 environment.
Change-Id: I9401637f4f3fe59abaaa05ecc72c6247826323ad
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
The openstack-dev mailing list has been replaced with
the openstack-discuss mailing list (*).
So replace the openstack-dev mailing list with
the openstack-discuss mailing list in setup.cfg.
In addition, update the home page URL in setup.cfg.
*: http://lists.openstack.org/pipermail/openstack-dev/2018-September/134911.html
Change-Id: If8dba8c7aee5e8161ac52dd2eeb0a7b2d82ca933
Ghanshyam Mann