Currently, inkscape-1.0_rc1 does enforce either Python 3.7 or 3.8, most probably due to the announced EOL of Python 3.6 in 12/2021. OTOH, inkscape compiles fine with that, and first checks seem to confirm it also is fine at runtime. So as there's still a long time to the EOL point, and as there are currently still a good couple of packages lacking >= Python-3.7 support, this would lead people to the need for 3 different Python interpreters (Python 2.7 is still needed for a few packages - see e.g. gnuradio, Python 3.6 as a lot of packages have that as its newest version, and 3.7 or 3.8 for packages like inkscape), what may seem a giant overkill, especially on somehow resource limited systems. So best would probably be to try to keep Python 3.6 support as long as it works and avoid political dodges enforcing the still impossible upgrade at least until by far the most packages support that. So, please re-add PYTHON_COMPAT=python3_6 to media-gfx/inkscape-1.0_rc1 and its upcoming successors.
Gentoo maintainers will not make the lifetime of python3_6 support dependent on upstream's EOL schedule, but for when the default in base/make.defaults is bumped. That hasn't happened yet, so omitting py36 from latest inkscape version is indeed a bit premature if there is no technical reason.
(In reply to Andreas Sturmlechner from comment #1) > Gentoo maintainers will not make the lifetime of python3_6 support dependent > on upstream's EOL schedule, but for when the default in base/make.defaults > is bumped. That hasn't happened yet, so omitting py36 from latest inkscape > version is indeed a bit premature if there is no technical reason. There is no point in re-adding it, pithon3.6 is on its way out, rhe global switch to python3.7 will be happenenig on the may 6th which is about 1.5 week from now.
(not to mention that py36 MUST be removed ASAP as upstream is switching to the yearly release cycle).
That is 1.5 weeks of a default conflict unless users have manually switched away from it.
(In reply to Andreas Sturmlechner from comment #4) > That is 1.5 weeks of a default conflict unless users have manually switched > away from it. I am not convinced, sorry. The amount of time you invest into turning py3.7 on inkscape is much less then the amount of time you invest into filing bugs about it, considering also that all the stable users must have python3.7 installed.
You and me will simply do that, if we aren't already running py38 globally. Standard users get a blocker and head to the forums, #gentoo, and here, because python blockers are of the worst kind.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f08c994742e2d31bb1b1916dc3fcb3ba17b59601 commit f08c994742e2d31bb1b1916dc3fcb3ba17b59601 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2020-04-25 13:45:36 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2020-04-25 13:45:57 +0000 media-gfx/inkscape: re-add py36 support Closes: https://bugs.gentoo.org/719386 Package-Manager: Portage-2.3.89, Repoman-2.3.20 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> media-gfx/inkscape/inkscape-1.0_rc1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 719416 has been marked as a duplicate of this bug. ***
Let's make global warming happy (for the believers only ...), as it's said some viruses don't like it.
Keep the offtopic to yourself or the forums please.
