On Thu, Apr 2, 2026 at 12:04 PM Johan Corveleyn <[email protected]> wrote: > > >>>> On Tue, Mar 31, 2026 at 7:12 PM Daniel Sahlberg > >>>> <[email protected]> wrote: > >>>>> > >>>>> Den tis 31 mars 2026 kl 18:03 skrev Timofei Zhakov <[email protected]>: > ... > >>>>>> I personally think that using anything besides C could potentially be > >>>>>> bad for cross-platformability (is this a word?). It's not guaranteed > >>>>>> that the platform that we are being run on has a Python interpreter > >>>>>> which is especially common on Windows. > >>>>> > >>>>> > >>>>> Cross-platformability works for me! > >>>>> > >>>>> I can't remember if I added Python manually on my main computer but at > >>>>> least it wasn't a big effort (possibly it is a Windows Store app). I > >>>>> don't think Python would be a major blocker for any reasonably modern > >>>>> Windows machine. > > Well, it being easily available is really not enough I'm afraid. > Python isn't present by default on Windows (and .py files are not > executable, you need a .bat wrapper or something). Requiring users to > install an extra tool / interpreter will be ignored by 99% of Windows > users ("nevermind, if this extra optional tool requires an extra > package, I'll just ignore it; don't care"). > > Ask some of your colleagues that work on Windows as their main > platform (if any) whether they have Python installed. Unless they > already have it for some specific dev tooling (or if it's the stack > they develop in), I'm betting most won't have it. > > -- > Johan
Yes, that is true. For example, I have a VM that I host my personal Subversion server on (it runs Windows), and I don't have Python installed on it. There is Perl for gitsvn, but it's a different story. It's also bundled into git's package. I wouldn't say it's the best example as it's not the place where svnbrowse is helpful anyway... -- Timofei Zhakov
