From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
Bernhard Voelker <mail@bernhard-voelker.de>
Subject: Re: future Python evolution
Date: Sun, 21 Apr 2024 16:50:47 +0200 [thread overview]
Message-ID: <21066443.Wb1LW67PtU@nimes> (raw)
In-Reply-To: <0d69dedd-f4d6-4ca1-9c1c-c127656fc37b@bernhard-voelker.de>
Bernhard Voelker wrote:
> The shell seems have to been more safe in that regard.
But the concepts of the shell are stuck in the 40-years-ago past.
That's why it is not recommendable as a programming language for real
programs [1].
> I'd guess most hosts have python installed nowadays ... the question is
> rather which version of it, and how compatible it is:
> now it's <3.7 which is incompatible (according to your mail),
> but in future there might come more incompatibilities with newer versions.
Good point. Yes, Python occasionally (rarely?) makes incompatible changes.
So, I've now created a continuous integration at [2]. If a Python release
is made that breaks gnulib-tool, this CI will notify me shortly afterwards,
and we will have time to adapt gnulib-tool, even before the new Python
release lands in the various distros.
Bruno
[1] https://lists.gnu.org/archive/html/bug-gnulib/2024-03/msg00160.html
[2] https://gitlab.com/gnulib/gnulib-tool-ci
next prev parent reply other threads:[~2024-04-21 14:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 0:22 beta-tester call draft Bruno Haible
2024-04-20 0:39 ` Bruno Haible
2024-04-20 0:56 ` Collin Funk
2024-04-20 1:49 ` Bruno Haible
2024-04-20 4:27 ` Paul Eggert
2024-04-20 22:31 ` gnulib-tool: In sh+py mode, don't fail because of dangling symlinks Bruno Haible
2024-04-20 22:46 ` beta-tester call draft Bruno Haible
2024-04-20 9:38 ` Simon Josefsson via Gnulib discussion list
2024-04-20 22:50 ` gnulib-tool.py speedup Bruno Haible
2024-04-20 23:01 ` Collin Funk
2024-04-20 23:50 ` Bruno Haible
2024-04-21 0:53 ` Collin Funk
2024-04-20 10:21 ` beta-tester call draft Pádraig Brady
2024-04-20 13:05 ` Bernhard Voelker
2024-04-20 22:54 ` Bruno Haible
2024-04-20 22:57 ` Paul Eggert
2024-04-20 23:14 ` Bruno Haible
2024-04-21 10:53 ` Bernhard Voelker
2024-04-21 14:50 ` Bruno Haible [this message]
2024-04-21 15:14 ` future Python evolution Paul Eggert
2024-04-21 22:38 ` Bruno Haible
2024-04-22 7:05 ` Paul Eggert
2024-04-21 15:26 ` Bernhard Voelker
2024-04-28 14:14 ` Bernhard Voelker
2024-04-21 15:15 ` beta-tester call draft Janneke Nieuwenhuizen
2024-04-21 16:07 ` full-source bootstrap and Python Bruno Haible
2024-04-22 7:29 ` Simon Josefsson via Gnulib discussion list
2024-04-22 10:07 ` Bruno Haible
2024-04-22 10:06 ` Janneke Nieuwenhuizen
2024-04-22 11:24 ` Simon Josefsson via Gnulib discussion list
2024-04-22 15:48 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21066443.Wb1LW67PtU@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=mail@bernhard-voelker.de \
/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).