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: Wed, 22 Feb 2023 04:23:29 +0000 [thread overview]
Message-ID: <87zg96ntjg.fsf@posteo.net> (raw)
In-Reply-To: <87sfeyekcr.fsf@posteo.net>
Kyle Andrews <kyle@posteo.net> writes:
> 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.
Reading a few hours later I apologize that I came off a bit harshly. I
am grateful to guile writers for sharing their work. I appreciate that
it is a challenging task making a computing system which is approachable
while also being fast when it needs to be. There will always be some
room left for additional improvement.
I am starting to feel intense pressure to move on to my next project. My
colleagues just don't get it. I do, and I really really want to show
them that reproducible research can be done without much trouble even
for scientific workflows mixing R and python packages and scripts, which
are probably the most complex workflows "in the wild" in my neck of the
woods. So, even if they don't get it yet, they might in a few months
when their projects break as the software ecosystem moves on to the next
fad. It always does.
From a broader perspective, sometimes the only way for people to get
things is if they see a lot of pressure from other peers in their field
to do it. If it is perceived as a "go do" and not as an arduous journey
with a realistic prospect of failure, then it will get done. I want to
make sure it's the former. To that end, I want there to be an entry in
the cookbook for this. I just sent a patch outlining my ideas for what
the scope should be.
Of course, since I can't actually figure it out yet, it's more of a
draft at present. Honestly, I couldn't get my poor ancient laptop to
even finish compiling the inferior - much less try using that inferior
with your package-with-explicit-python. I'm just wishing that this
approach will work in the near future. So, please don't let anyone
include it yet :)
next prev parent reply other threads:[~2023-02-22 5:44 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
2023-02-22 4:23 ` Kyle Andrews [this message]
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=87zg96ntjg.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).