From: zimoun <zimon.toutoune@gmail.com>
To: Bengt Richter <bokr@bokr.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Python 2 end-of-life?
Date: Fri, 29 Nov 2019 12:55:34 +0100 [thread overview]
Message-ID: <CAJ3okZ13JWW62ALKEHYj33aY6h8P6CzCLaYwunRcGM7E80zY8Q@mail.gmail.com> (raw)
In-Reply-To: <20191129065410.GB1094@PhantoNv4ArchGx.localdomain>
Hi Bengt,
On Fri, 29 Nov 2019 at 07:54, Bengt Richter <bokr@bokr.com> wrote:
> > For example, considering rust, it is about the bootstrappability. See [1].
> >
> > [1] http://guix.gnu.org/blog/2018/bootstrapping-rust/
> >
>
> That looks horrible to me :)
> Don't they have a "guild disasseble" kind of thing that they could use
> to recover a mungeable source of the final product, and then
> make a self-hoster from that (even if it takes serious hacking)?
Do you have better to propose to bootstrap Rust? Does it work?
> > > It would be really interesting if you could tweak your py2-dependent-package
> > > lister to show for each how many lines of py2 code are causing the py2 dependency!
> >
> > It is really hard -- nor impossible. And I am not convinced that the
> > tough work will pay off.
>
> Why so hard? Is not all the information available in sources?
Again, go ahead if you evaluate that it deserves it.
My humble point of view is: it is an hard task and the work will not pay off.
It will not pay off because it is fully unclear what to do with this
information about "how many lines of py2".
My approach is: try to build and/or run with Python 3. If yes, cool!
update the package and remove from the list [1], else inspect why and
try to fix (patch) and report this patch upstream.
[1] http://issues.guix.gnu.org/issue/38420
> > To me, one path to remove unnecessary dependencies of Python2 is to
> > give a look package by package, try to replace the Python2 dependency
> > by the Python3 (if exist) and see what happens. If it does not build
> > because the package really uses Python2 features, figure out which
> > one, patch with the Python3 equivalent and submit the patch upstream.
>
> That will likely be the best thing to do for a number of packages,
> but I would rather plug in a guix/guile/bash equivalent that passes
> the same well-designed (! :) test suite, where that is possible.
What is the goal of such? What do we win? Larger than python 2 -> python 3.
All the best,
simon
next prev parent reply other threads:[~2019-11-29 11:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:39 Python 2 end-of-life? zimoun
2019-11-21 11:46 ` zimoun
2019-11-21 12:01 ` Konrad Hinsen
2019-11-26 16:51 ` Konrad Hinsen
2019-11-26 17:50 ` Hartmut Goebel
2019-11-26 18:55 ` ng0
2019-11-27 8:28 ` Konrad Hinsen
2019-11-27 17:41 ` zimoun
2019-11-26 21:51 ` Bengt Richter
2019-11-27 7:56 ` Konrad Hinsen
2019-11-27 17:35 ` zimoun
2019-11-29 6:07 ` Bengt Richter
2019-11-29 7:38 ` Konrad Hinsen
2019-11-29 12:12 ` zimoun
2019-11-29 11:41 ` zimoun
2019-11-29 13:42 ` Bengt Richter
2019-11-29 14:12 ` zimoun
2019-11-29 22:16 ` Bengt Richter
2019-11-27 17:28 ` zimoun
2019-11-27 17:43 ` Ricardo Wurmus
2019-11-29 6:54 ` Bengt Richter
2019-11-29 11:55 ` zimoun [this message]
2019-11-28 14:40 ` Konrad Hinsen
2019-11-28 15:50 ` Hartmut Goebel
2019-11-28 18:22 ` zimoun
2019-11-21 17:28 ` Alex Griffin
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=CAJ3okZ13JWW62ALKEHYj33aY6h8P6CzCLaYwunRcGM7E80zY8Q@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=bokr@bokr.com \
--cc=guix-devel@gnu.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.
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).