- 04 3月, 2025 2 次提交
-
-
由 Ricardo Vieira 提交于
-
由 dependabot[bot] 提交于
Bumps [pypa/cibuildwheel](https://github.com/pypa/cibuildwheel) from 2.22.0 to 2.23.0. - [Release notes](https://github.com/pypa/cibuildwheel/releases) - [Changelog](https://github.com/pypa/cibuildwheel/blob/main/docs/changelog.md) - [Commits](https://github.com/pypa/cibuildwheel/compare/v2.22.0...v2.23.0) --- updated-dependencies: - dependency-name: pypa/cibuildwheel dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by:
dependabot[bot] <support@github.com>
-
- 28 2月, 2025 2 次提交
-
-
由 Chris Fonnesbeck 提交于
-
由 Aarsh Wankar 提交于
-
- 27 2月, 2025 5 次提交
-
-
由 Ricardo Vieira 提交于
JAX needs no special handling because it excludes inplace rewrites.
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
- 25 2月, 2025 7 次提交
-
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
Introduced in e593b0ac due to a bug when inputs had zero-strides. The bug can be fixed just by removing a block that assumed some `full`/`broadcasting` behavior by the operation, but this is not happening with DimShuffle.
-
由 ricardoV94 提交于
This was caused by 223ee154, which used the generic `PyArray_IntpConverter` to convert the shape numpy vector into a simple C-array for the Reshape operation. There seems to be no need for this change as the strides were correctly used Profiling suggests the previous changes caused a 7.5x slowdown. The benchmark detects only a 2.3x slowdown due to the PyTensor call overhead.
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
- 24 2月, 2025 5 次提交
-
-
由 Aarsh Wankar 提交于
* Added print_shape option to debugprint and simplify __str__ logic in TensorType * Add print_memory_map option to debugprint to enable destroy and view maps
-
由 Will Dean 提交于
-
由 Ricardo Vieira 提交于
-
由 Ben Mares 提交于
For more context, see the discussion in: https://github.com/conda-forge/pytensor-suite-feedstock/pull/133#issuecomment-2673831166
-
由 Jesse Grabowski 提交于
* Fix bug in solve_triangular when `overwrite_b = True` * Add regression test
-
- 20 2月, 2025 7 次提交
-
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
pytest-sphinx is not compatible with Python 3.13: https://github.com/twmr/pytest-sphinx/issues/67
-
由 Ricardo Vieira 提交于
We want to test numpy 1.26.x on `test_math.py` but test_math.py was being excluded in python 3.10, and numpy 1.26.x was being excluded in the non python3.10 job.
-
-
由 Ben Mares 提交于
-
由 Ricardo Vieira 提交于
Notably changes the behavior of `__bool__` to always raise. Before there was a hack based on whether a variable had been compared to something before.
-
由 Ricardo Vieira 提交于
-
- 19 2月, 2025 4 次提交
-
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
由 Ricardo Vieira 提交于
-
- 18 2月, 2025 8 次提交
-
-
由 Ricardo Vieira 提交于
-
由 Adv 提交于
Co-authored-by:Adv <adhvaithhundi.221ds003@nitk.edu.in>
-
由 Brendan Murphy 提交于
Remaining tests now run on latest numpy, except for Numba jobs, which need numpy 2.1.0
-
由 Brendan Murphy 提交于
Also added ruff numpy2 transition rule.
-
由 Brendan Murphy 提交于
I split this test up to test uint64 separately, since this is the case discussed in Issue #770. I also added a test for the exact example used in that issue. The uint dtypes with lower precision should pass. The uint64 case started passing for me locally on Mac OSX, but still fails on CI. I'm not sure why this is, but at least the test will be more specific now if it fails in the future.
-
由 Brendan Murphy 提交于
Due to changes in numpy conversion rules (NEP 50), overflows are not ignored; in particular, negating a unsigned int causes an overflow error. The test for `neg` has been changed to check that this error is raised.
-
由 Brendan Murphy 提交于
In numpy 2.0, if axis=None, then np.unique does not flatten the inverse indices returned if return_inverse=True A helper function has been added to npy_2_compat.py to mimic the output of `np.unique` from version of numpy before 2.0
-
由 Brendan Murphy 提交于
From numpy PR https://github.com/numpy/numpy/pull/22449, the repr of scalar values has changed, e.g. from "1" to "np.int64(1)", which caused two doctests to fail.
-