From: zimoun <zimon.toutoune@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 49329@debbugs.gnu.org
Subject: [bug#49329] [PATCH 1/4] gnu: python2-renpy: Drop unused Ren'py sources.
Date: Sun, 11 Jul 2021 10:28:05 +0200 [thread overview]
Message-ID: <86r1g5i7ai.fsf@gmail.com> (raw)
In-Reply-To: <68f5b3c4ac813caef41da4062179eb2d07ae2575.camel@student.tugraz.at>
Hi Leo,
On Sat, 03 Jul 2021 at 10:35, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
> I must admit, I haven't been following the Python 2 removal plan too
> closely. Is it already time to move working leaf packages?
The Python EOL is January, 1rst 2020 [1]. So now, we are 1.5 years
ahead, so yes it seems already time to cook a plan. :-)
However, there is no consensus about such plan. ;-) Some related
discussions:
2018-12: <https://yhetil.org/guix/20181226093812.GR2581@macbook41/>
2019-10: <https://yhetil.org/guix/CAJ3okZ33HsXxgVgK3XyVHvYUfDUrbcwBnOn7FC6=3AG_YvAUbQ@mail.gmail.com/>
2019-11: <http://issues.guix.gnu.org/issue/38420> Failed attempt to cook something
2021-01: <https://yhetil.org/guix/86pn1pgf7z.fsf@gmail.com/>
From my understanding, the “implemented” plan is described by Maxim
here:
<https://yhetil.org/guix/87pn1oxv0m.fsf@gmail.com/>
I just want to point that it is less work to transfer a functional and
supported by upstream package than to transfer a package starting to
have issues. Other said, I think it is easier to find motivation to do
the transfer for this previous case than to do some “janitor” work
later. For what my opinion is worth. :-)
About Ren’Py 7, I do not have an opinion. Yeah, waiting Ren’Py 8 seems
The Right Thing™ to do. :-)
Hope that helps,
simon
1: <https://www.python.org/doc/sunset-python-2/>
next prev parent reply other threads:[~2021-07-11 8:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 12:39 [bug#49329] [PATCH 00/??] Improve Ren'py package Leo Prikler
2021-07-02 13:58 ` [bug#49329] [PATCH 1/4] gnu: python2-renpy: Drop unused Ren'py sources Leo Prikler
2021-07-02 13:58 ` [bug#49329] [PATCH 2/4] gnu: python2-renpy: Update description Leo Prikler
2021-07-02 13:58 ` [bug#49329] [PATCH 3/4] gnu: python2-renpy: Correct inputs Leo Prikler
2021-07-02 13:58 ` [bug#49329] [PATCH 4/4] gnu: renpy: " Leo Prikler
2021-07-03 7:50 ` [bug#49329] [PATCH 1/4] gnu: python2-renpy: Drop unused Ren'py sources zimoun
2021-07-03 8:35 ` Leo Prikler
2021-07-11 3:50 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-11 8:28 ` zimoun [this message]
2021-07-11 9:53 ` [bug#49329] [PATCH 1/4] gnu: python2-renpy: Drop unused Ren'py sources Leo Prikler
2021-07-15 6:47 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-03 9:28 ` [bug#49329] [PATCH v2 1/5] gnu: python2-renpy: Drop unused Ren'py sources Leo Prikler
2021-07-03 9:28 ` [bug#49329] [PATCH v2 2/5] gnu: python2-renpy: Update description Leo Prikler
2021-07-11 4:53 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-11 7:09 ` Leo Prikler
2021-07-15 6:48 ` Chris Marusich
2021-07-03 9:28 ` [bug#49329] [PATCH v2 3/5] gnu: python2-renpy: Correct inputs Leo Prikler
2021-07-11 4:55 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-03 9:28 ` [bug#49329] [PATCH v2 4/5] gnu: renpy: Correct inputs Leo Prikler
2021-07-11 4:37 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-11 6:58 ` Leo Prikler
2021-07-03 9:28 ` [bug#49329] [PATCH v2 5/5] gnu: Add python-pygame-sdl2 Leo Prikler
2021-07-11 4:44 ` [bug#49329] [PATCH 00/??] Improve Ren'py package Chris Marusich
2021-07-11 7:00 ` Leo Prikler
2021-07-15 7:21 ` Chris Marusich
2021-07-15 11:46 ` bug#49329: " Leo Prikler
2021-07-11 4:52 ` [bug#49329] " Chris Marusich
2021-07-11 7:03 ` Leo Prikler
2021-07-15 7:22 ` Chris Marusich
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=86r1g5i7ai.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=49329@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).