public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Migrate away from python-2 or not
Date: Fri, 29 Nov 2019 16:40:16 +0100	[thread overview]
Message-ID: <20191129154016.GA837@cloudsdale.the-delta.net.eu.org> (raw)
In-Reply-To: <CA+v7wxJDgi5Mn7u+xNrmKYBOuHG6h53BfuMgzC=XLJ-H7-iNbg@mail.gmail.com>

[2019-11-29 14:49:12+0100] Mathy Vanvoorden:
> > I tried removing python2 on a handful of test systems over the last week
> > ... it's back everywhere.
> >
> >
> I attempted the same over the last couple of days as I was thinking "It's
> going anyway, why not get a head start?". I had to do the following:
> 
> * Remove metagen
> * Remove rr
> * Update kodi and related packages to 9999 (I know they are working on
> getting their 19.0 package out asap because of the 2.7 EOL)
> * Update clang and related packages to 9.0.0
> * Remove python dependency in libdbusmenu (it's not needed, PR here:
> https://github.com/gentoo/gentoo/pull/13790)
> * Port gnome-doc-utils to python3 (
> https://github.com/gentoo/gentoo/pull/13791)
> * Remove qt-creator as it depends on clang 8, changing USE to -clang would
> also work but not really using it anyway atm
> * Remove gconf dep from discord-bin (
> https://github.com/gentoo/gentoo/pull/13793)
> * Remove gconf dep from spotify (https://github.com/gentoo/gentoo/pull/13794
> )
> * Update gcr to 3.34.0 (https://github.com/gentoo/gentoo/pull/13798)
> * Unmask a number of other packages that luckily did have updated versions
> available: samba, talloc, javatoolkit, tdb, tevent, ldb, itstool,
> dropbox-cli, nodejs
> * Unmerge typing (now provided by python package)
> * Reinstall m2crypto, python-typing, scons
> * Reinstall crda with patch in https://bugs.gentoo.org/693728
> * Manually fix some packages that were not being selected for emerge by -N:
> m2crypto, virtual/python-typing, typing, scons
> 
> Unfortunately I was not able to completely purge python2.7 from my system.
> The base package is still installed as it is required to build qtwebkit,
> qtwebengine, zziplib, firefox and spidermonkey. At least however I am now
> running with -python_targets_python2_7 so there's that.

Been running my server without python2 since… 2019-11-16 I thought it 
was more than that but still quite a lot considering that I kept clang-8 
for a while before switching to clang-9 on it. (I use clang as main 
compiler, I'm also deprecating gcc so prefer to play it safe)

I still have a bunch of stuff on my desktop&laptop requiring python2,
like nodejs or renpy but it's getting quite better in the last months,
one I'm trully fearing about how it will go is dev-util/scons, I guess
a lot of patches will be required on the releases.

I think this kind of discussion might be better on the forums or
a user list btw.


  reply	other threads:[~2019-11-29 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 12:15 [gentoo-dev] Migrate away from python-2 or not Benda Xu
2019-11-24 13:31 ` Francesco Riosa
2019-11-24 18:13 ` Philip Webb
2019-11-25  7:41 ` Eddie Chapman
2019-11-25  8:39 ` Jaco Kroon
2019-11-29 13:49   ` Mathy Vanvoorden
2019-11-29 15:40     ` Haelwenn (lanodan) Monnier [this message]
2019-12-03 13:17   ` Benda Xu

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191129154016.GA837@cloudsdale.the-delta.net.eu.org \
    --to=contact@hacktivis.me \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox