https://bugzilla.redhat.com/show_bug.cgi?id=1916480 --- Comment #4 from Josef Ridky <jridky@xxxxxxxxxx> --- Hi, GIMP3 will use Python 3 binding, but right now, no one know, when the release of this version become generally available. It could be weeks/months/year .... but we all expect to be it in upcoming weeks/months. So from this point of view, it doesn't have so much sense to have this as Python 2 plugin, due of it become obsolete quite soon. I would recommend to create python2 and python3 sub-packages of this plugin, so you'll be ready for the transition, once become available. Take a look at https://wiki.gimp.org/wiki/Hacking:Plugins_v3 for basic info about Python3 plugins for GIMP3 and https://wiki.gimp.org/wiki/Roadmap#GIMP_3.0 for GIMP3 roadmap. For shebangs, during GIMP build (install phase), we're substituting all shebangs in shipped python plugins that are part of GIMP itself with our own just to avoid false alarms: # Hardcode python interpreter in shipped python plug-ins. This actually has no # effect because gimp maps hashbangs with and without the /usr/bin/env detour # to the system python interpreter, but this will avoid false alarms. grep -E -rl '^#!\s*/usr/bin/env\s+python' --include=\*.py "%{buildroot}" | while read file; do sed -r '1s,^#!\s*/usr/bin/env\s+python$,#!%{__python2},' -i "$file" sed -r '1s,^#!\s*/usr/bin/env\s+python2$,#!%{__python2},' -i "$file" done -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
