The Python libraries expect an APE environment, and that assumption is deeply built in to it.<br>The previous attempt to do a so-called &quot;native&quot; port ended up writing large chunks of APE in Python,<div>which was a bit of a waste of time, or it couldn&#39;t run all the existing things, such as Mercurial.</div>
<div>Using APE means that you don&#39;t need to re-write it in Python, and incorporating a new Python</div><div>release can be made relatively straightforward (except for bugs in Python).</div><div><br></div><div><div class="gmail_quote">
On 14 March 2012 06:15, Steven Stallion <span dir="ltr">&lt;<a href="mailto:sstallion@gmail.com">sstallion@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":1in">Ideally we could have a more complete port that wouldn&#39;t require APE,<br>
but that may be approaching the point of diminishing returns.</div></blockquote></div><br></div>