Problemsby IbisPyTorch deprecations force unplanned migrations
Outages and change4 posts from 3 people4d active+22 posts in the last 7 days, 1 the 7 days before (steady)
Posts per day
The posts behind it
4, newest first[deprecation] `torch.testing.make_tensor` with `low == high` for floating/complex dtypes### API or component `torch.testing.make_tensor` with `low == high` for floating/complex dtypes ### Kind Behavior change ### Deprecated in 2.1 ### Removal target 2.3 ### Next step error in 2.16 ### Replacement and migration Use `torch.full(...)`. ### Owner TBD ### PRs Deprecated...pytorch/pytorch · drisspgOpen ↗☂️ Deprecations and frozen components: when they started, and when the code is removed...removal target `none` until a removal is planned. ### Adding an entry 1. File a tracking issue with the [Deprecation tracking](https://github.com/pytorch/pytorch/issues/new?template=deprecation.yml) form. It is labeled `module: deprecation`. 2. Attach it as a sub-issue of this...pytorch/pytorch · drisspg1 reactionsOpen ↗Decouple RPC server profiler from the legacy (deprecated) profiler...1. **CUDA-only.** The legacy API only exposes a `use_cuda` bool - no way to profile `xpu`/`mtia`/`privateuseone` RPC work, which Kineto already supports. 2. **Deprecated path.** It relies on the legacy C++ per-thread enablement (`enableProfilerLegacy` in the RPC request...pytorch/pytorch · wanglulu82-jpgOpen ↗[RFC] Remove Python 3.10 support in CI/CDSimilar to https://github.com/pytorch/pytorch/issues/161167 PyTorch 2.14 is the last release with Python 3.10 wheels. PyTorch 2.15 will be our first release without Python 3.10 binaries. We want to start the process for removal of Python 3.10 from PyTorch CI and nightly builds....pytorch/pytorch · atalman3 reactionsOpen ↗
Companies and products named
About this problem
Evidence
4 posts from 3 people in 1 place, about 1 a week over 34 days. Mostly on pytorch/pytorch. Tools named alongside: GitHub, NVIDIA.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts that state a pain and match the "deprecation" rule about PyTorch. First post Sep 16, 2026, latest Oct 19, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
The same problem elsewhere
Deprecations force unplanned migrationsGitHub deprecations force unplanned migrationsClaude Code deprecations force unplanned migrationspandas deprecations force unplanned migrationsTerraform deprecations force unplanned migrationsGemini deprecations force unplanned migrationsHugging Face deprecations force unplanned migrationsApache Iceberg deprecations force unplanned migrationsKubernetes deprecations force unplanned migrationsnpm deprecations force unplanned migrationsClaude deprecations force unplanned migrations
Other PyTorch problems
PyTorch users keep filing bugsTrouble with PyTorch inputTrouble with PyTorch truePyTorch upgrades break working setupsTrouble with PyTorch workerPyTorch builds are slow or flakyTrouble with PyTorch inductorPyTorch GPU access and drivers are painfulTrouble with PyTorch testPyTorch vulnerabilities are hard to triage and patchRunning PyTorch locally hits memory and speed limitsPyTorch error messages are cryptic
History
unverified to corroborated
fading to steady
steady to fading
PyTorch deprecations force unplanned migrations (2 posts)