• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

qtile / qtile / 24609024951 / 2
83%
master: 83%

Build:
DEFAULT BRANCH: master
Ran 18 Apr 2026 04:58PM UTC
Files 156
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Apr 2026 04:33PM UTC coverage: 73.165% (+0.04%) from 73.123%
24609024951.2

push

github

tych0
*: drop some __future__ and TYPE_CHECKING imports

Move imports out of `if TYPE_CHECKING:` blocks to real module-level imports
where it doesn't cause circular imports, and drop the accompanying
`from __future__ import annotations` where possible. Forward references to
still-needed TYPE_CHECKING-only imports are preserved, and the few files
that still require them (e.g. for self-referential annotations or known
circular dependencies between backend, config, manager, etc.) keep both
the guard and the future import.

We can remove all of these __future__ and imports and TYPE_CHECKING guards
once our lowest supported python version is 3.14, which imports PEP 649,
deferred evaluation of annotations: https://peps.python.org/pep-0649/

This gets rid of ~300 lines of boilerplate that I often find inscrutable:
"when should I put this in TYPE_CHECKING? when should I not? why the
difference?".

Co-authored-by: Claude <noreply@anthropic.com>

15135 of 20686 relevant lines covered (73.17%)

0.73 hits per line

Source Files on job 3.12-wayland - 24609024951.2
  • Tree
  • List 156
  • Changed 61
  • Source Changed 0
  • Coverage Changed 61
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 24609024951
  • 0c5e1285 on github
  • Prev Job for on master (#24606374281.5)
  • Next Job for on master (#24609891633.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc