From: Kyle Andrews <kyle@posteo.net>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Using an alternative python to build python modules
Date: Tue, 21 Feb 2023 21:28:29 +0000 [thread overview]
Message-ID: <87sfeyekcr.fsf@posteo.net> (raw)
In-Reply-To: <871qmig3c9.fsf@posteo.net>
Kyle Andrews <kyle@posteo.net> writes:
> There seems to be some secret Guile incantation I am overlooking. Could
> you give me a hint of what this could be?
Tobias pointed out to me that the Guile developers could be to blame
here. They appear a bit too preoccupied with prematurely optimizing the
speed of code with the result that it has already been made inaccessible
before users have a fighting chance to interactively study it to
understand how it works.
The workflow described in the Guile manual seems like it would be
perfect. It suggests I should be able to just modify the source code and
reload it into the running environment. Unfortunately, I don't know how
to associate my running environment via the Guix REPL with my git
checkout.
next prev parent reply other threads:[~2023-02-21 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 21:27 Using an alternative python to build python modules Kyle Andrews
2023-02-18 9:57 ` Wojtek Kosior via
2023-02-18 17:53 ` Edouard Klein
2023-02-20 22:29 ` Kyle Andrews
2023-02-21 16:50 ` Edouard Klein
2023-02-21 12:52 ` Simon Tournier
2023-02-21 20:26 ` Kyle Andrews
2023-02-21 21:10 ` Simon Tournier
2023-02-22 9:23 ` Simon Tournier
2023-02-21 21:28 ` Kyle Andrews [this message]
2023-02-22 4:23 ` Kyle Andrews
2023-02-22 10:09 ` Simon Tournier
2023-02-24 0:16 ` Kyle Andrews
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfeyekcr.fsf@posteo.net \
--to=kyle@posteo.net \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).