Allow pytensor 3.3 - #8400
Merged
Merged
Conversation
No code changes were needed for compatibility, so the lower bound stays at 3.2.2.
ricardoV94
approved these changes
Aug 16, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8400 +/- ##
=======================================
Coverage 91.87% 91.87%
=======================================
Files 128 128
Lines 21256 21256
=======================================
Hits 19530 19530
Misses 1726 1726 🚀 New features to boost your workflow:
|
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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Raises the PyTensor upper bound from
<3.3to<3.4so that the current PyTensor 3.3.x releases can be used with PyMC. The pin is updated inrequirements.txt,requirements-dev.txtand the sixconda-envs/*.ymlfiles.No source changes were needed: PyTensor 3.3.0 documents no breaking changes (free-threaded build support, MLX dispatches, and bugfixes), so the lower bound stays at
>=3.2.2and both 3.2.x and 3.3.x remain supported.Testing
Ran the full test suite locally on Python 3.12 against PyTensor 3.3.0 and 3.2.4 with everything else held fixed. The two runs produce identical results — same 3444 passed, same 42 failed, and a byte-identical list of failing test ids:
The 42 failures are unrelated to this change and reproduce on the currently-supported 3.2.4: 36 are
Multinomialtests that only fail underxdist(they pass when the selection is run on its own, so they look like local test-pollution), and the rest are missing optional dependencies in my environment (nutpie,h5py).tests/step_methodswas run separately because unrelated lambda-id()-based parametrization ids break xdist collection matching; it passes:133 passed, 6 skipped.Related Issue
Checklist
Type of change