texlive has python2 build dependencies. It is unclear if/when they will ever be resolved. Some of it has been ported to python3, and I have other changes that I am working on to enable improved Python 3 support.
An exception is necessary though.
To clarify, this is texlive-base and it is a runtime dependency, not a build dependency, correct? Only python2 interpreter seems to be needed:
texlive-dviasm-7:20190410-2.fc31 /usr/bin/python2.7
texlive-pygmentex-7:20190410-2.fc31 /usr/bin/python2
texlive-pythontex-7:20190410-2.fc31 /usr/bin/python2 /usr/bin/python3
note that texlive-pygmentex has an undeclared dependency on python2-pygments , do you also want an exception for that one and python2-setuptools that are needed for to build pygments?
dviasm python3 upstream issue https://github.com/khaledhosny/dviasm/issues/7
pythontex allows people to run Python code. I'm not sure it deserves the hard dependency on Python 2 - i.e. if I want to use it to run Python 3 code, it drags Python 2 in.
Metadata Update from @churchyard: - Issue tagged with: python 2 exception
@spot Is this texlive or texlive-base, build time or runtime?
Sorry, this is texlive-base. Everything in texlive should be noarch, and if there are python dependencies, they're only runtime.
edited the title.
+1
Please downgrade to Suggests the dependency on python2 in texlive-pythontex. No reason to pull it in by default.
APPROVED (+2, 0, -0) Exception to use python2 at runtime for texlive-base (texlive-dviasm, texlive-pygmentex, texlive-pythontex (downgraded to suggests))
Metadata Update from @churchyard: - Issue tagged with: pending announcement
Metadata Update from @psabata: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.