| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
On platforms with only bitmap fonts Tk substitutes the nearest available size, so query the resolved size instead of assuming it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Hi, I also noticed this issue shown on the Alpine buildbot, and reproduced it locally. I've verified your fix works as well — using self.actual_size instead of the hardcoded 20 makes the test more robust. Just one thing to add: I found that if you install scalable font (via apk add font-liberation font-dejavu), then the test actually passes as-is too. |
Sorry, something went wrong.
|
Thank you for verification. The test was incorrect from the beginning, it should not have such assumption. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
On platforms that provide only bitmap fonts (for example the AMD64 Alpine Linux buildbot) a font created from a description such as ('Times', 20, 'bold') does not keep the requested size: Tk substitutes the nearest available size. The test_create and test_existing tests added in GH-152025 asserted the exact requested size (20) and therefore failed there.
This asks Tk for the size it actually resolves for the description (via font actual) instead of assuming the requested value. The keyword/explicit-size assertions are unchanged, since those set the size directly.
🤖 Generated with Claude Code