Forwarding the rest of the conversation to the bug:
-------- Forwarded Message --------
Subject: Re: Bug#1077793: pandoc: Pandoc trying to use python2 for filter
Date: Sat, 3 Aug 2024 11:08:42 +0900
From: Kyle Robbertze <paddatrap...@debian.org>
To: John G Macfarlane <j...@berkeley.edu>
On 03/08/2024 11:05, John G Macfarlane wrote:
On Aug 2, 2024, at 6:43 PM, Kyle Robbertze <paddatrap...@debian.org> wrote:
On 03/08/2024 01:39, John G Macfarlane wrote:
On Aug 2, 2024, at 2:19 AM, Kyle Robbertze <paddatrap...@debian.org> wrote:
It appears that pandoc will try execute the binary 'python' when running
a .py filter, when it should be using 'python3'.
Why should it be using python3? Pandoc filters can be written in any version
of pandoc.
I assume you mean any version of Python? Python 2 is dead and no longer shipped
in Debian (#1027107). The default behaviour should be to use Python 3, because
that is the only available Python version in the Debian archive.
Yes, I meant python. So, is this the situation in Debian? Python 2 is no longer
shipped, but 'python' is not linked to 'python3'?
Yup, I'm not sure if 'python' will ever be linked to 'python3', but it
isn't at the moment.
If so, I'd have no objections to a patch that uses 'python3' on Debian. I'd
hesitate a bit before making this change upstream, though -- I'd want to know
about the situation outside Debian, on all the platforms where pandoc might be
used. (Not a python user myself.)
Sure, that makes sense - I think other distros have linked them and
Windows/Macs almost definitely have.
Cheers
Kyle
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
⢿⡄⠘⠷⠚⠋⠀ Debian Developer
⠈⠳⣄⠀⠀⠀⠀ https://wiki.debian.org/KyleRobbertze
