We have been running tests on Python 3.10 for some time and it is the
default deployment platform for Neutron.
Change-Id: Ic5f2086c958ceb5763c48d5c71ed2d99f757f7dd
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: I46da9a7a84a2f628030206d3ac3f75beeeff46b4
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: I9ff2cdf3d1e2d262c53933d8151b982f87f1122c
These translation sections are not needed anymore, Babel can
generate translation files without them.
Remove babel.cfg as well, this is the default role and not needed
anymore.
also remove Babel from requirements[1]
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014227.html
Change-Id: I073d3d7e2f2e8a4f06c17541a0f4d4fedcaed2dc
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: I7eafe056d570417d49e26de61b5c0316d0bf09a6
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Instead of keeping hardcoded files in bin/ directory it is
more flexible to install such files using setup.cfg file.
It will for example install files with correct shebang for
python2 and python3.
This patch also removes tools/osken-manager.spec file
as it was used by PyInstaller in Ryu and it isn't used
in os-ken.
Change-Id: Ie85c64d81c86f0059528ad4d8e238a4124d4e5b4
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: Ifd8c3bc2621cfeb5bab0494db13e9a8023dda486
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The Python core team[*1] stopped supporting python 2.6. Some Python
libraries started following the same path and trying to support 2.6
becomes painful...
For example, most of you already noticed, oslo.config dropped 2.6
support. I tried to work around it with the following commit:
2250171098
But this forces users of decent distributions (e.g Ubuntu 14.04) to
upgrade pip (old pip versions can't understand version conditions).
[*1]
http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
SubmittingPatches.rst was renamed to CONTRIBUTING.rst.
setup.py sdist will check this dependency.
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
this new command takes a sub-command name as its first positional argument
and passes the rest of arguments to the corresponding sub-module.
for example, 'run' sub-command is an equivalent to bin/ryu-manager.
this commit does not replace the existing commands like ryu-manager.
this merely adds new ways to invoke the functionalities.
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
suggested by some openstack folks.
see https://review.openstack.org/#/c/71791
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
will be used for OF-Config stuff.
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
revert the following commit because it doesn't work with
the latest oslo.config which requires newer pbr.
|commit 205485e052
|Author: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
|Date: Fri Aug 30 14:08:49 2013 +0900
|
| stick with pbr 0.5.19
|
| the latest versions of pbr generate scripts which don't support
| multiversion. to avoid importing modules from older multiversion-aware
| installations of ryu, we prefer multiversion-aware scripts.
|
| Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
| Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
the problem reported by Satoshi Kobayashi on ryu-devel.
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
the latest versions of pbr generate scripts which don't support
multiversion. to avoid importing modules from older multiversion-aware
installations of ryu, we prefer multiversion-aware scripts.
Signed-off-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Note that now ryu uses /etc/ryu/ryu.conf. The previous install path
(/usr/etc/ryu/ryu.conf) doesn't fit to FHS.
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Dr. Jens Harbott