Improved support for Python 3.14 by radarhere · Pull Request #8948 · python-pillow/Pillow
Navigation Menu
{{ message }}
python-pillow / Pillow Public
- Notifications You must be signed in to change notification settings
- Fork 2.4k
Merged
Improved support for Python 3.14#8948
hugovk merged 3 commits intopython-pillow:mainfrom
Improved support for Python 3.14#8948
hugovk merged 3 commits intopython-pillow:mainfrom
Conversation
Copy link Copy Markdown
Member
- A test has started failing now that an error message has changed in Python 3.14
https://github.com/python-pillow/Pillow/actions/runs/14903027962/job/41859109942#step:11:3834
E AssertionError: Regex pattern did not match.
E Regex: 'must be sequence of length 4'
E Input: 'argument 3 must be tuple of length 4, not 2'
- An error has started occurring when building PyQt6 on Python 3.14 - https://github.com/python-pillow/Pillow/actions/runs/14903027971/job/41859749652#step:8:12
Let's skip it for now.
- Those changes then triggers our Windows message about unsupported Python versions - https://github.com/python-pillow/Pillow/actions/runs/14906195788/job/41869036883?pr=8948#step:28:779. Since Python 3.14 has now reached beta, we would like users to be able to install and it, so let's increment the version check.
...this then leads to the same error from building PyQt6 occurring when building Pillow - https://github.com/python-pillow/Pillow/actions/runs/14906674076/job/41870606277?pr=8948#step:28:769
LINK : fatal error LNK1104: cannot open file 'python314t.lib'
radarhere
added
the
Testing
label
radarhere
changed the title
Updated error message for Python 3.14
Improved support for Python 3.14
radarhere
removed
the
Testing
label
radarhere
deleted the
error
branch
radarhere
mentioned this pull request
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment