On 2024/02/21 12:52, Daniel Dickman wrote:
> 
> 
> On Tue, 20 Feb 2024, Marc Espie wrote:
> 
> > > 
> > As far as I'm concerned, the only port where python2 support still matters
> > is gimp, until they release -stable with gtk+3 and the most important plugins
> > are ported (resynthesizer and friends)
> > 
> 
> Thanks.
> 
> I think there are a few more things than just gimp left though.
> 
> On my end I'm seeing the harder ones are:
> - print/fontforge and consumers (solfege, lilypond and mftrace)
> - gimp and plugins, as you say
> - lang/pypy (edd@ might have a plan)

this has been marked broken for a while now.

> - lang/flang and lang/cparser (bcallah@ may have a plan)

flang seems to be out of sync with LLVM versions anyway.
cparser doesn't use python at all?

> - a few pygame games I happen to like and have been slowly porting to 
>   python3

btw fretsonfire (py2) doesn't seem to work at all. that's the only user
of py2 graphics/py-opengl and py2-Pillow.

> - a few source control things (cvs2svn and py-rcparse consumers)

devel/git-cvs has problems anyway and I would be ok with removing it.
- this from my sent mail from 2015 when I reported it:

---
               [...]           When an update is committed to a file
that was previously imported, the import is shown again in "git log". It
looks like it happens for the first commit after import. [...]

Strangely if I use "git log ." instead of "git log", the extra commit isn't
shown.
---

i'd be ok with removing this and cvs20hg and making py-rcsparse py3-only.

> - sysutils/conky

doesn't use python?

> - net/mininet, our version seems to be based on an openbsd-specific fork 
>   of 2.2.0, but upstream 2.3.0 has python3 support now.
> - 2 emulators (dynagen, gambatte)

i think retiring dynamips + dynagen would be reasonable at this point.
> 
> Apart from these there a few easy updates to py3 left and the rest may 
> just need to be retired at this point.
> 
> After that we can retire python2, py2-pip, and py2-setuptools (or we'd be 
> very close).
>