New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webbrowser to support "gio open <URL>" #87303
Comments
[forwarded from https://bugs.debian.org/969776] """ The gvfs-open tool was superseded by gio(1) in 2015, and removed from The gnome-open tool was superseded by gvfs-open in 2008, ceased to be The current list of browser could need some cleanup, e.g.:
|
gio is not available on older distros. For example I could not find it in Xenial with libglib2.0-bin 2.48.2-0ubuntu4.8. I suggest that you keep the fallbacks or seek agreement that we no longer support old distros without gio. |
The next 3.10 and 3.11 releases are very soon so unfortunately if this is not fixed by then I will need to revert PR29154 |
Christian, this is going into 3.11.0a3 unfortunately. I will make this a blocker for future alphas, so please, take any action that you think is required. |
If this is not fixed by this week, I will be forced to revert the PR |
I've opened #30417, is that what you want? I am not a regular CPython developer, so I don't have a good way to assess which reviewers speak for the project and which reviewers are only offering a personal opinion. |
In this webpage (bpo) core developers have a little python logo close to their name (as myself). In GitHub, you can sometimes tell by hovering over the profile or checking the core dev log in the devguide: https://devguide.python.org/developers/ |
I am removing the "release blocker" tag. Simon, thanks a lot for both PRs. I am sorry that we needed to revert your original work, but unfortunately it was blocking a release and we are forced to act in this case. PLease, work together with Christian and Matthias to make a version of the patch that works in all supported platforms. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: