From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8E336901-36C6-4A87-B957-AC839E0E7D02@corpus-callosum.com> <71A1FC5E-E3DF-4E7E-BB8F-3B99DD2F59C6@gmail.com> Date: Sat, 5 Jan 2013 01:17:04 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Mercurial and Plan 9 Topicbox-Message-UUID: feba823e-ead7-11e9-9d60-3106f5b1d025 The first Python port aimed at a so-called "native" port but as I worked on it to import a newer version of Python, it became clear that Python's standard libraries, certainly as used by most Python applications, are so closely bound up with POSIX interfaces (eg, the exact components of the stat structure) that large chunks of APE were simply being replicated in Python, which seemed a bit pointless (and actually quite hard, as when emulating select). On 4 January 2013 23:10, Steven Stallion wrote: > The existing Python port is sufficient for Mercurial, though having a native > Python port would be great.