From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] removing python
Date: Tue, 15 Jun 2021 01:55:43 +0930 [thread overview]
Message-ID: <260216E1A2B95EB9D2D9485E56A79F7D@musolino.id.au> (raw)
In-Reply-To: <CAKeBiN7XkaSSdin0n-qq2nHxRt4+Lmiyi3e19Ex+nbwigOx7XQ@mail.gmail.com>
> I probably missed the memo but what’s the back story behind removing
> Python and migrating away from hg?
>
> I’m a newcomer so I don’t yet know what’s problematic about using hg
> or Python on Plan9.
9front ships an ancient version of python purely to support hg. It's
big and it's slow. A pile of non-plan9 code that can now be done
without.
I don't know that there was any real desire to move away from hg as
the repo format, per se, but Ori wrote git9, not hg9.
next prev parent reply other threads:[~2021-06-14 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 0:09 ori
2021-06-14 0:19 ` Stephen M. Jones
2021-06-14 1:16 ` Stanley Lieber
2021-06-14 1:52 ` ori
2021-06-14 2:37 ` Stanley Lieber
2021-06-14 15:16 ` Alexander McLin
2021-06-14 16:25 ` Alex Musolino [this message]
2021-06-14 16:34 ` ori
2021-06-14 20:06 ` Daniel C.
2021-06-14 20:34 ` ori
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=260216E1A2B95EB9D2D9485E56A79F7D@musolino.id.au \
--to=alex@musolino.id.au \
--cc=9front@9front.org \
/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).