Skip to content

[ci] Start testing on python 3.14-beta #2731

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
✨ New feature

@Pierre-Sassoulas Pierre-Sassoulas added this to the 4.0.0 milestone May 8, 2025
@Pierre-Sassoulas Pierre-Sassoulas added Maintenance Discussion or action around maintaining astroid or the dev workflow python 3.14 labels May 8, 2025
@cdce8p
Copy link
Member

cdce8p commented May 15, 2025

I've been looking into the brain errors. Will open a PR to fix them later today.

@cdce8p cdce8p force-pushed the python3.14 branch 5 times, most recently from f9b8e04 to adaabd4 Compare May 16, 2025 15:50
@cdce8p
Copy link
Member

cdce8p commented May 16, 2025

Rebased the PR and fixed the remaining two test cases. Just wondering if we need to split the as_string case.
On my machine (macOS ARM) I'm also seeing outright Python crashes for two test cases. The CI run seems to be fine though.?

Both are already ignored for PyPy. When I run them locally, Python crashes with Abort trap: 6

  • tests/test_inference.py::InferenceTest::test_no_infinite_ancestor_loop
  • tests/test_inference.py::test_recursion_on_inference_tip

--
Also seeing a crash for one pylint test

  • tests/test_functional.py::test_functional[regression_5408]

@Pierre-Sassoulas
Copy link
Member Author

Just wondering if we need to split the as_string case.

I was trying to keep the return in finally for python < 3.14 but it's near impossible (very hard as we have 188 tests using it, we can't remove them all for python 3.14). Probably not something we're going to break by mistake, so probably safe to skip.

@Pierre-Sassoulas
Copy link
Member Author

My current guess with the last issue is either a fail of pytest under windows and python 3.14 or a cache issue on our side.

@Pierre-Sassoulas
Copy link
Member Author

Added backport label because we'll need 3.14 compat for pylint faster than we can properly release 4.0.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport maintenance/3.3.x Maintenance Discussion or action around maintaining astroid or the dev workflow python 3.14
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants