From: Leo Famulari <leo@famulari.name>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: What’s next?
Date: Tue, 18 May 2021 15:30:24 -0400 [thread overview]
Message-ID: <YKQV0ERr3T5mqxVO@jasmine.lan> (raw)
In-Reply-To: <64E57C83-83A7-4ECE-80C0-8CCAD978CC24@lepiller.eu>
On Sat, May 15, 2021 at 02:08:50PM -0400, Julien Lepiller wrote:
> In the short term I'd like to merge the python optimisations. We discussed it before release and thought it might be nice to merge them before c-u, from a separate branch.
+1
Have you tested them at all yet? If so, and they don't seem to break
anything, maybe they could be squeezed onto the wip-ungrafting branch.
The 'ungrafting' jobset (based on the wip-ungrafting branch) entails a
complete rebuild of Python 2 and 3. If that branch requires another
iteration due to broken builds, and we are confident that the Python
optimisations won't break things, I'd say we could include them.
Otherwise, we could do a python-updates branch that includes these
optimizations, and updates to Python 3.8.10, along with any existing bug
fixes for Python 2. It would be completed more quickly than
core-updates.
next prev parent reply other threads:[~2021-05-18 19:31 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 17:47 What’s next? Ludovic Courtès
2021-05-15 18:08 ` Julien Lepiller
2021-05-18 19:30 ` Leo Famulari [this message]
2021-05-18 21:19 ` Julien Lepiller
2021-05-18 20:25 ` Ludovic Courtès
2021-05-19 15:39 ` Katherine Cox-Buday
2021-05-19 16:22 ` Ricardo Wurmus
2021-05-15 20:24 ` Efraim Flashner
2021-05-16 18:25 ` raingloom
2021-05-16 22:06 ` Joshua Branson
2021-05-17 20:13 ` Ludovic Courtès
2021-05-21 11:07 ` Efraim Flashner
2021-05-26 13:26 ` Ludovic Courtès
2021-05-16 4:09 ` Maxim Cournoyer
2021-05-16 8:57 ` Pierre Neidhardt
2021-05-16 18:18 ` Christopher Lemmer Webber
2021-05-17 5:43 ` Pierre Neidhardt
2021-05-16 13:38 ` Maxime Devos
2021-05-16 16:08 ` Vagrant Cascadian
2021-05-16 16:26 ` Svante Signell
2021-05-17 14:45 ` Leo Famulari
2021-05-18 2:35 ` Joshua Branson
2021-05-18 14:05 ` Leo Famulari
2021-05-22 23:11 ` raingloom
2021-05-24 22:32 ` Joshua Branson
2021-05-17 12:36 ` zimoun
2021-05-18 3:37 ` Bone Baboon
2021-05-18 13:08 ` Bone Baboon
2021-05-18 20:24 ` Ludovic Courtès
2021-05-18 16:44 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2021-05-16 12:24 Brendan Tildesley
2021-05-17 20:25 ` Ludovic Courtès
2017-05-24 13:11 Ludovic Courtès
2017-05-24 13:23 ` Ricardo Wurmus
2017-05-27 10:01 ` Ludovic Courtès
2017-05-27 21:44 ` Ricardo Wurmus
2017-05-28 20:44 ` Ludovic Courtès
2017-05-28 21:36 ` Ricardo Wurmus
2017-05-30 15:55 ` Ludovic Courtès
2017-05-24 15:52 ` Brendan Tildesley
2017-05-27 10:04 ` Ludovic Courtès
2017-05-28 20:41 ` Maxim Cournoyer
2017-05-30 15:17 ` Ludovic Courtès
2017-06-03 21:16 ` Maxim Cournoyer
2017-05-24 16:09 ` Catonano
2017-05-24 16:25 ` Jan Nieuwenhuizen
2017-05-24 18:40 ` Adonay Felipe Nogueira
2017-05-24 19:34 ` Catonano
2017-05-24 19:56 ` Ricardo Wurmus
2017-05-30 0:09 ` myglc2
2017-05-24 21:47 ` Leo Famulari
2017-05-24 21:45 ` Leo Famulari
2017-05-25 8:11 ` What???s next? Pjotr Prins
2017-05-27 10:16 ` Ludovic Courtès
2017-05-28 7:30 ` What's next? Pjotr Prins
2017-05-28 20:48 ` Ludovic Courtès
2017-05-28 22:05 ` Roel Janssen
2017-05-30 15:19 ` Ludovic Courtès
2017-05-30 20:15 ` Pjotr Prins
2017-05-29 2:31 ` Maxim Cournoyer
2017-05-28 20:37 ` What???s next? Maxim Cournoyer
2017-05-28 21:34 ` Ricardo Wurmus
2017-05-30 15:14 ` Ludovic Courtès
2017-05-25 14:57 ` What’s next? Chris Marusich
2017-05-25 18:32 ` Leo Famulari
2017-05-25 20:01 ` Ricardo Wurmus
2017-05-25 20:41 ` Adonay Felipe Nogueira
2017-05-27 10:13 ` Ludovic Courtès
2017-05-29 23:28 ` myglc2
2017-06-08 14:35 ` Ricardo Wurmus
2017-05-27 10:09 ` Ludovic Courtès
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=YKQV0ERr3T5mqxVO@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).