Skip to content
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

Release the PyGobject pin, documenting the consequences of that change. #3256

Merged
merged 3 commits into from
Mar 11, 2025

Conversation

freakboy3742
Copy link
Member

@freakboy3742 freakboy3742 commented Mar 10, 2025

PyGObject 3.52.1 introduced a dependency on girepository-2.0. This isn't a problem on most Linux distributions, but it's not available on older Debian-based releases.

As there's no way to specify a requirement based on Linux system packages, we've only got 2 options:

  1. Permanently pin PyGObject to 3.50.0 until we're able to drop support for Ubuntu 22.04, Debian 11 and Debian 12. That couldn't happen until at least October 2027, when Python 3.11 (the version of Python that ships with Debian 12) is deprecated.
  2. Allow newer versions, and document the issue for older Ubuntu/Debian releases.

This PR implements the second approach.

Fixes #3143

PR Checklist:

  • All new features have been tested
  • All new features have been documented
  • I have read the CONTRIBUTING.md file
  • I will abide by the code of conduct

@freakboy3742 freakboy3742 requested a review from mhsmith March 10, 2025 05:11
@mhsmith mhsmith merged commit 3156192 into beeware:main Mar 11, 2025
14 of 15 checks passed
@freakboy3742 freakboy3742 deleted the pygobject-pin branch March 11, 2025 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PyGObject>=3.51.0 depends on libgirepository 2.0
2 participants