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: I5581aaba3bbb214b906e9743ddc7085632a94787
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: Ie4e3366ad01e219971595464122a6b262e55cb91
These translation sections are not needed anymore, Babel can
generate translation files without them.
Change-Id: I6478639b17968e5eb5e44ffcbca2ca65cbc995f7
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:
* Wheel is not needed for python 3 only repo
* Some other sections are obsolete
- Update classifiers
- Update requirements, no need for python_version anymore
Change-Id: I0dbb13d555eb473916ba585c62a0f7433d15afed
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: If0b076ecd9b6c82186e8d6e504da3aa9d11a7dd3
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: Ia91c276327b09f0448384b1adfcf001b698d87c8
In OpenStack projects, where pbr is used, this tool generates the
versioning information from the tags. This patch moves us to use it
too.
Change-Id: Idf617e65a5970bb4e4a88a6496f06bf4be47ab5b
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
It is nicer, since we support python2 and python3 to generate wheels
that are compatible with both.
Change-Id: Idea197cc24887993425f40034acc71278efaf421
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
In order for Kuryr's libnetwork driver to function, it is essential
that /usr/libexec, the driver specfile and /etc/kuryr get installed.
Up until now, this was manual. This change fixes it.
Change-Id: Ifdb6048a154aa811a0369cbcdb848b19798bc51f
Signed-off-by: Antoni Segura Puimedon <toni@midokura.com>
py33/Python 3.3 is not supported from Mitaka
onwards, as per the Infra Team.
The following patch removes this support from
kuryr's setup.cfg as well.
Change-Id: I23d82bdd8f47f2c259fc14ffc5a5cef9f7f336f7
Closes-Bug: #1526170
OpenStack projects are no longer being tested under Python 2.6, so
remove the trove classifier implying that this project supports 2.6.
Change-Id: I3513466e6f17865ddc0cb748ed0694b4a492ca65
The Openstack project should follow this style, which forces all
version information being read from the setup.cfg. This helps
keep the version information unique.
Ref can be found at: http://docs.openstack.org/developer/pbr/
Change-Id: Ied7043863b6677487f96fc8f1600ecef0e10818d
Closes-Bug: #1526130
Now after running: $ sudo python setup.py develop one can start
kury-server by invoking: $ kuryr-server
Change-Id: I992967400b1b128707df7e79cd594eed5688b90f