Enable Ruff SIM rules #827
Annotations
72 warnings
Typos
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ruff
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ruff
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
|
Mypy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Pytest on Py3.10
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Pytest on Py3.10:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Pytest on Py3.10:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/mapper/__init__.py#L203
List found in expression graph. This is deprecated and will stop working in 2025. Use tuples instead.
|
Pytest on Py3.10:
pymbolic/interop/ast.py#L204
CallWithKwargs created with non-hashable kw_parameters. This is deprecated and will stop working in 2025. If you need an immutable mapping, try the :mod:`immutabledict` package.
|
Pytest on Py3.10:
pymbolic/interop/ast.py#L204
CallWithKwargs created with non-hashable kw_parameters. This is deprecated and will stop working in 2025. If you need an immutable mapping, try the :mod:`immutabledict` package.
|
Pytest on Py3.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2187) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2184) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2187) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2184) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2181) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2181) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2178) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2178) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.x:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Pytest on Py3.x:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Pytest on Py3.12
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2204) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2204) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2210) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2210) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2207) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2207) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2213) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
opt/hostedtoolcache/Python/3.12.8/x64/lib/python3.12/pty.py#L95
This process (pid=2213) is multi-threaded, use of forkpty() may lead to deadlocks in the child.
|
Pytest on Py3.12:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Pytest on Py3.12:
test/test_persistent_hash.py#L38
PersistentHashWalkMapper is deprecated. Since they are dataclasses, expression objects should now support persistent hashing natively without any help. It will be removed in 2026.
|
Documentation
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Pylint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Tests for downstream project loopy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Tests for downstream project loopy:
loopy/test/test_callables.py#L406
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project loopy:
loopy/test/test_callables.py#L1258
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project loopy:
loopy/test/test_expression.py#L348
Using default C compiler because gcc-10 was not found. These tests may take a long time, because of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127.
|
Tests for downstream project loopy:
loopy/loopy/target/c/c_execution.py#L319
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
|
Tests for downstream project loopy:
loopy/test/test_expression.py#L376
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project loopy:
loopy/loopy/target/c/c_execution.py#L336
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
|
Tests for downstream project loopy:
loopy/test/test_expression.py#L348
Using default C compiler because gcc-10 was not found. These tests may take a long time, because of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107127.
|
Tests for downstream project loopy:
loopy/loopy/target/c/c_execution.py#L319
'GCCToolchain.copy' is deprecated. This is now a dataclass and should be used with the standard 'replace'.
|
Tests for downstream project loopy:
loopy/test/test_callables.py#L406
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project loopy:
loopy/test/test_callables.py#L1258
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytato:
pytato/pytato/target/loopy/__init__.py#L246
TranslationUnit.__call__ will become uncached in 2024, meaning it will incur possibly substantial compilation cost with every invocation. Use TranslationUnit.executor to obtain an object that holds longer-lived caches.
|
Tests for downstream project pytential
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_obj_array' is deprecated and will be unsupported from 2025. Use 'bcasts_across_obj_array', with equivalent meaning.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_numpy_array=True' is deprecated and will be unsupported from 2025.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
Broadcasting array context array types across <class 'meshmode.dof_array.DOFArray'> has been implicitly enabled. As of 2025, this will no longer work. There is no replacement as of right now. See the discussion in https://github.com/inducer/arraycontext/pull/190. To opt out now (and avoid this warning), pass _bcast_actx_array_type=False.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_obj_array' is deprecated and will be unsupported from 2025. Use 'bcasts_across_obj_array', with equivalent meaning.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_obj_array' is deprecated and will be unsupported from 2025. Use 'bcasts_across_obj_array', with equivalent meaning.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_numpy_array=True' is deprecated and will be unsupported from 2025.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_numpy_array=True' is deprecated and will be unsupported from 2025.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
Broadcasting array context array types across <class 'meshmode.dof_array.DOFArray'> has been implicitly enabled. As of 2025, this will no longer work. There is no replacement as of right now. See the discussion in https://github.com/inducer/arraycontext/pull/190. To opt out now (and avoid this warning), pass _bcast_actx_array_type=False.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
Broadcasting array context array types across <class 'meshmode.dof_array.DOFArray'> has been implicitly enabled. As of 2025, this will no longer work. There is no replacement as of right now. See the discussion in https://github.com/inducer/arraycontext/pull/190. To opt out now (and avoid this warning), pass _bcast_actx_array_type=False.
|
Tests for downstream project pytential:
pytential/.conda-root/envs/testing/lib/python3.13/site-packages/meshmode/dof_array.py#L75
'bcast_obj_array' is deprecated and will be unsupported from 2025. Use 'bcasts_across_obj_array', with equivalent meaning.
|