Re: Python extension commands in git - request for policy change
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Nov 25, 2012, 08:57 UTC
- Message-ID
- <50B1DD78.5040907@kdbg.org>
- In-Reply-To
- <20121125024451.1ADD14065F@snark.thyrsus.com>
Am 25.11.2012 03:44, schrieb Eric S. Raymond:
> That, among other things, means up-to-date versions of Python are > ubiquitous unless we're looking at Windows - in which case Perl and > shell actually become much bigger portability problems.
You seem to ignore that more than a quater of users are on Windows[1]. This is not negligible.
Therefore, we *are* looking at Windows. But where is there a portability problem? There is a POSIX shell available in all git installations on Windows. So is Perl. Python is not.
[1] https://git.wiki.kernel.org/index.php/GitSurvey2011#10._On_which_operating_system.28s.29_do_you_use_Git.3F
> 4) We should be encouraging C code to move to Python, too.
Absolutely not. To achieve best portability, all code should move to C instead.
-- Hannes