From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Thibault Lestang <t.lestang@imperial.ac.uk>
Cc: guix-science <guix-science@gnu.org>,
Simon Tournier <zimon.toutoune@gmail.com>
Subject: Re: Conda environments and reproducibility
Date: Sat, 11 Mar 2023 12:05:04 +0100 [thread overview]
Message-ID: <87a60jy2e7.fsf@gnu.org> (raw)
In-Reply-To: <87fsdfejfv.fsf@imperial.ac.uk> (Thibault Lestang's message of "Fri, 16 Dec 2022 10:16:55 +0000")
Hi Thibault,
Thibault Lestang <t.lestang@imperial.ac.uk> skribis:
> Well let's see. I just set up a Gitlab repo with a weekly pipeline (re)creating
> a conda env from an environment.yml spec I generated earlier this morning.
>
> https://framagit.org/tlestang/conda-python-example
>
> Just Python for now but anyone feel free to contribute an R env as well.
Any findings so far? Looking at the pipelines, it seems to be all
green, right?
It’s an interesting experiment, great that you set it up!
Ludo’.
next prev parent reply other threads:[~2023-03-11 11:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:28 Conda environments and reproducibility Thibault Lestang
2022-11-28 19:45 ` Konrad Hinsen
2022-11-29 10:32 ` Thibault Lestang
2022-11-29 13:12 ` Hugo Buddelmeijer
2022-11-29 13:39 ` Konrad Hinsen
2022-12-01 14:01 ` Hugo Buddelmeijer
2022-12-02 13:01 ` Konrad Hinsen
2022-11-29 20:10 ` Simon Tournier
2022-12-16 10:16 ` Thibault Lestang
2023-03-11 11:05 ` Ludovic Courtès [this message]
2023-03-11 11:43 ` Simon Tournier
2023-03-13 10:26 ` Lestang, Thibault
2023-03-13 11:00 ` Ricardo Wurmus
2023-03-13 12:38 ` Simon Tournier
2023-03-16 10:26 ` Ludovic Courtès
2023-03-16 13:40 ` Thibault Lestang
2023-04-03 15:22 ` Simon Tournier
2023-04-04 12:19 ` Thibault Lestang
2022-12-02 10:52 ` Ludovic Courtès
2022-12-02 11:05 ` Ludovic Courtès
2022-12-02 13:59 ` Simon Tournier
2022-12-02 14:06 ` Hugo Buddelmeijer
2022-11-28 20:46 ` Simon Tournier
2022-11-29 10:41 ` Thibault Lestang
2022-11-29 14:25 ` Simon Tournier
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=87a60jy2e7.fsf@gnu.org \
--to=ludovic.courtes@inria.fr \
--cc=guix-science@gnu.org \
--cc=t.lestang@imperial.ac.uk \
--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).