As a user, when I install Gimp, I get the '2.10' module. And if they do conflict, I don't know what will happen and how things will be coordinated.Ģ. As far as I know, there is no mechanism to check if they will conflict with any other modules, or (if there's a single Gimp stream for all Fedoras), with non-modular RPMs in older Fedora releases. If we, for example, drop python2-numpy in F31, pycairo in F32, and pygtk2 in F33, these will need to be added to the Gimp module. It's possible that we won't remove all dependencies at once. I can think of tho things that will not be smooth:ġ. > Can you help me with necessary steps to make as smooth as possible? If you need anything from us, or something is unclear, please mention it here. This bug is filed semi-automatically, and might not have all the context specific to gimp. What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) What are the upstream/community plans/timelines regarding Python 3? What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) To help planning, we'd like to know the plans for gimp's future.

Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: This falls within the Fedora 31 lifetime. Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released.

Gimp2 2