This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.

(Upstream VTE developer here, not affiliated with Red Hat or Fedora)

- What is the reason for the Python2 dependency?

It provides Python bindings.

- What are the upstream/community plans/timelines regarding Python 3?

Upstream: This gtk2-based vte has long been superseded by gtk3-based vte2.91, hasn't been maintained for 8+ years, and won't receive updates.

- What is the guidance for porting to Python 3?

In my opinion, the Python2 binding should be dropped. Any package depending on it should be switched to using vte2.91, or if not possible then have its vte support dropped, or if that's still possible then that package should be dropped.

Furthermore, in my opinion this ancient vte package should entirely be dropped, not just its Python binding. But it might be out of the scope of this bug.

typo: ...or if that's still *not* possible then...

Then, I think that the best of we can do is to send an email to maintainers of dependent packages with warning that this package might be removed in the near future. There is vte291 which all dependent packages should switch to.

What do you think about it? How hard is to switch to the newest version of vte from this ancient one?

> How hard is to switch to the newest version of vte from this ancient one?

It is a significant amount of work, not because of VTE per se (although that has also changed quite a bit), but because the older one goes with GTK2 only and the newer one goes with GTK3 only. So the entire application has to be ported from GTK2 to GTK3. It's easily possible that upstream has already done this work, whereas RH/Fedora hasn't switched to compiling against GTK3 and thus new VTE.

You should look around to see how many packages are affected, I don't expect too many. For some, you can just switch to use GTK3. For some others, it's possible that VTE is an optional dependency that you can just remove. Chances are that there isn't any single package where removing the Python binding of this ancient VTE causes any noticeable trouble.

Could you please collect the list of packages that depend on old VTE's python binding? That is, depend on old VTE and seems to use python2? (It's a pity that the python binding isn't split into its own package, it would be easier that way.) I think we should look at them one by one.

On a side note, not related to the Python binding: some apps (lxterminal that suddenly occurs to me) are still compiled against GTK2 + old VTE in Fedora, whereas against GTK3 + new VTE in Debian/Ubuntu. Maybe it's time for RH/Fedora to move forward here as well.

> Could you please collect the list of packages that depend on old VTE's python binding? That is, depend on old VTE and seems to use python2?

We run a query for that :)  https://fedora.portingdb.xyz/pkg/vte/

I can only see icairo.

Thanks! (I'm not aware of these magical tools that you have.)

That's icaro, not icairo. Never heard of this project. Homepage in Spanish only. Has a gtk3_devel branch in git, I have no idea how mature that is. It's for you guys to evaluate :)

It uses much more python2 stuff than just the VTE binding, so you'll have to evaluate anyways what to do with this package (keeping in mind that the original initiative is to completely get rid of python2, unrelated to vte).

Happy to see that there's no other affected package.

And of course let's link to bug 1737939: icaro depends on Python 2

Hi there. I have been the one 'maintaining' vte for the last N years. I took it on when I needed it for xfce4-terminal. That has long since not been the case. 

I'd really like to retire this package, or at least hand it off to someone else who needs it. 

Packages still needing this I see are:

Here I get: 

% sudo dnf repoquery --whatrequires vte                  
gnome-desktop-sharp-0:2.26.0-36.fc31.x86_64
gnome-mud-0:0.11.2-25.fc31.x86_64
gnurobots-0:1.2.0-26.fc31.x86_64
grip-1:3.10.0-3.fc31.x86_64
gtkdialog-0:0.8.3-18.fc31.x86_64
icaro-0:1.0.9-4.fc31.noarch
libvtemm-0:0.25.0-18.fc31.x86_64
lilyterm-0:0.9.9.2-10.fc27.x86_64
lterm-0:1.5.1-3.fc31.x86_64
lxterminal-0:0.3.2-3.fc31.x86_64
pacmanager-0:4.5.5.7-14.fc31.noarch
perl-Gnome2-Vte-0:0.11-14.fc31.x86_64
rubygem-vte-0:3.3.7-1.fc32.x86_64
vte-devel-0:0.28.2-29.fc31.x86_64

So, perhaps we drop python2 bindings now, and then mail the rest of the above packages maintainers and see if anyone wants to keep it alive or we can retire it.

FTR: icaro package was orphaned last week and will be retired in 6 weeks if nobody takes it.

Given the fact that icaro is the only one dependent Python package, I think that once it'll be retired, we can remove vte Python bindings and that's all from Python point of view.

Am I right?

SGTM

FYI: Debian probably already dropped it, which I assume from a user complaint at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930972, referring to the package medit (http://mooedit.sourceforge.net/) which apparently isn't shipped by Fedora.

(In reply to Lumír Balhar from comment #14)
> FTR: icaro package was orphaned last week and will be retired in 6 weeks if
> nobody takes it.
> 
> Given the fact that icaro is the only one dependent Python package, I think
> that once it'll be retired, we can remove vte Python bindings and that's all
> from Python point of view.
> 
> Am I right?

I suppose, but I dont really care to maintain it moving forward. 

So, how about I orphan it now and tell the devel list and if someone wants to keep it alive they can take it over and drop the python bindings. Otherwise, it can just go into the night... ;)

> So, how about I orphan it now and tell the devel list and if someone wants
> to keep it alive they can take it over and drop the python bindings.
> Otherwise, it can just go into the night... ;)

Yes, feel free to do it.

Could you please do it rather sooner than later?

No one wanted it. Should I just orhpan or retire?

If there are packages depending on it, please don't retire it.
If you don't want to maintain it any more, orphan it.

I have orphaned it now.

This is not fixed; vte still depends on pygtk2.

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.