This should get support for python 3.8 (and ideally directly 3.9) and a bump to 2.0. No changes to the ebuild necessary appart from changing the PYTHON_COMPAT variable.
Ok this is getting a bit more complicated.
This requires the "typing-extensions" python package which we don't have yet, however only for <python-3.8.
Instead of packaging another package we will not need in the future we may consider doing the following:
* Add python 3.8 support to the atpublic 1.0 ebuild.
* Wait with atpublic 2.0 until we have python 3.8 by default.
* Commit atpublic-2.0 without python 3.7/3.6 after that.
The bug has been referenced in the following commit(s):
Author: Hanno Böck <email@example.com>
AuthorDate: 2020-09-27 15:08:08 +0000
Commit: Hanno Böck <firstname.lastname@example.org>
CommitDate: 2020-09-27 15:08:08 +0000
dev-python/atpublic: Support python 3.8
Signed-off-by: Hanno Böck <email@example.com>
Package-Manager: Portage-3.0.8, Repoman-3.0.1
dev-python/atpublic/atpublic-1.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
I committed python 3.8 support now and will leave this open for the bump which should happen once we can deprecate 3.6/3.7 support.