From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 14 Mar 2012 09:19:02 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0015175cd5fe617fa304bb307727 Subject: Re: [9fans] Mercurial and Plan 9 Topicbox-Message-UUID: 689e0a5a-ead7-11e9-9d60-3106f5b1d025 --0015175cd5fe617fa304bb307727 Content-Type: text/plain; charset=UTF-8 The Python libraries expect an APE environment, and that assumption is deeply built in to it. The previous attempt to do a so-called "native" port ended up writing large chunks of APE in Python, which was a bit of a waste of time, or it couldn't run all the existing things, such as Mercurial. Using APE means that you don't need to re-write it in Python, and incorporating a new Python release can be made relatively straightforward (except for bugs in Python). On 14 March 2012 06:15, Steven Stallion wrote: > Ideally we could have a more complete port that wouldn't require APE, > but that may be approaching the point of diminishing returns. > --0015175cd5fe617fa304bb307727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The Python libraries expect an APE environment, and that assumption is deep= ly built in to it.
The previous attempt to do a so-called "native&q= uot; port ended up writing large chunks of APE in Python,
which was a b= it of a waste of time, or it couldn't run all the existing things, such= as Mercurial.
Using APE means that you don't need to re-write it in Python, and = incorporating a new Python
release can be made relatively straigh= tforward (except for bugs in Python).

On 14 March 2012 06:15, Steven Stallion <sstallion@gmail.com> wrote:
Ideally we could have a more complete port that wouldn'= ;t require APE,
but that may be approaching the point of diminishing returns.

--0015175cd5fe617fa304bb307727--