Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[MNT]: CI: either remove, or separate cairocffi CI paths #29822

Open
@jayaddison

Description

@jayaddison

Summary

Thecairocffi dependency was added to (Travis) CI to support thepgi object bindings (0ed289c) that are no-longer-supported (3221c94).

However:cairocffi will still be used ifcairo (e.g.pycairo) is unavailable at runtime:

try:
importcairo
ifcairo.version_info< (1,14,0):# Introduced set_device_scale.
raiseImportError(f"Cairo backend requires cairo>=1.14.0, "
f"but only{cairo.version_info} is available")
exceptImportError:
try:
importcairocffiascairo
exceptImportErroraserr:
raiseImportError(
"cairo backend requires that pycairo>=1.14.0 or cairocffi "
"is installed")fromerr

We currently installcairocffi during GitHub Actions CI unit testing; so there is a possibility that it would mask failures to import and exercisepycairo-based test coverage.

NB: This is my current understanding as I explore#29732 - I'm not 100% confident about my findings.

Proposed fix

Ideally, I think we should extract a separatecairocffi-based GitHub Actions CI unit test matrix job, so that bothpycairo andcairocffi are exercised.

As a fallback if that proves infeasible, we could removecairocffi from the dependencies installed during CI workflows.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp