From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mercurial and Plan 9
Date: Wed, 14 Mar 2012 09:19:02 +0000 [thread overview]
Message-ID: <CAOw7k5hg=_FQ5OczQka7H0HdbkB2CkrR_79SXmWgf77AZ_CxWw@mail.gmail.com> (raw)
In-Reply-To: <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
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 <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.
>
[-- Attachment #2: Type: text/html, Size: 1000 bytes --]
next prev parent reply other threads:[~2012-03-14 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 6:15 Steven Stallion
2012-03-14 6:28 ` Jeff Sickel
2012-03-14 15:17 ` Steven Stallion
2012-03-14 15:22 ` Yaroslav
2012-03-20 22:11 ` Federico Benavento
2013-01-04 21:56 ` Jeff Sickel
2013-01-04 23:10 ` Steven Stallion
2013-01-05 1:17 ` Charles Forsyth
2013-01-05 2:35 ` Federico G. Benavento
2013-01-07 15:13 ` Yaroslav
2012-03-14 9:19 ` Charles Forsyth [this message]
[not found] <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.c>
2012-03-14 12:58 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOw7k5hg=_FQ5OczQka7H0HdbkB2CkrR_79SXmWgf77AZ_CxWw@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).