# documentation **URL:** https://dev-discuss.pytorch.org/c/documentation/12.md [Latest](https://dev-discuss.pytorch.org/latest.md) · [Categories](https://dev-discuss.pytorch.org/categories.md) --- ## [About the documentation category](https://dev-discuss.pytorch.org/t/about-the-documentation-category/21)
**Author:** [@smth](https://dev-discuss.pytorch.org/u/smth)\ **Replies:** 0
docstrings, linting, sphinx, etc. --- ## [Workflows never approved — pytorch/pytorch PR #194438 (docs only)](https://dev-discuss.pytorch.org/t/workflows-never-approved-pytorch-pytorch-pr-194438-docs-only/3435)
**Author:** [@pandeylakshya207-max](https://dev-discuss.pytorch.org/u/pandeylakshya207-max)\ **Replies:** 2\ **Last updated:** [September 23, 2026, 8:30pm UTC](https://dev-discuss.pytorch.org/t/workflows-never-approved-pytorch-pytorch-pr-194438-docs-only/3435 "2026-09-23T20:30:21Z")
Hi all, I opened PR #194438 two weeks ago — a docs-only change adding an explanation of the adaptive pooling bin-boundary algorithm (addressing a long-standing FIXME in torch/nn/modules/pooling.py). No source code is mo… --- ## [Review request: enable flake8-bugbear B007 repo-wide (PR #189319, tracking issue #106571)](https://dev-discuss.pytorch.org/t/review-request-enable-flake8-bugbear-b007-repo-wide-pr-189319-tracking-issue-106571/3418)
**Author:** [@HumphreySun98](https://dev-discuss.pytorch.org/u/HumphreySun98)\ **Replies:** 0\ **Last updated:** [July 31, 2026, 5:31am UTC](https://dev-discuss.pytorch.org/t/review-request-enable-flake8-bugbear-b007-repo-wide-pr-189319-tracking-issue-106571/3418 "2026-07-31T05:31:12Z")
Hi all, I have a lint-enablement PR that has been merge-ready for ~3 weeks but can’t find a reviewer, likely because it crosses many module boundaries. Posting here as suggested escalation before considering splitting i… --- ## [Torch Documentation O3KR1 2026 H1](https://dev-discuss.pytorch.org/t/torch-documentation-o3kr1-2026-h1/3372)
**Author:** [@j4orz](https://dev-discuss.pytorch.org/u/j4orz)\ **Replies:** 0\ **Last updated:** [May 3, 2026, 7:08pm UTC](https://dev-discuss.pytorch.org/t/torch-documentation-o3kr1-2026-h1/3372 "2026-05-03T19:08:43Z")
Hi Torch Team, I’m excited for the Documentation team’s O3KR1 for H1 2026. That is, O3: “Improve PyTorch documentation metrics to understand how users interact with the docs and where the gaps are” KR1:“Conduct a P… --- ## [What should we do about developer documentation?](https://dev-discuss.pytorch.org/t/what-should-we-do-about-developer-documentation/491)
**Author:** [@suo](https://dev-discuss.pytorch.org/u/suo)\ **Replies:** 16\ **Last updated:** [February 21, 2024, 8:35am UTC](https://dev-discuss.pytorch.org/t/what-should-we-do-about-developer-documentation/491 "2024-02-21T08:35:12Z")
We are pretty disorganized with regard to our developer docs (where dev docs are defined as documents covering our workflow or internal technical information—user-facing docs are a separate matter). Surveys of our develo… --- ## [Contributing to Pytorch Documentation](https://dev-discuss.pytorch.org/t/contributing-to-pytorch-documentation/1866)
**Author:** [@maajidkhann](https://dev-discuss.pytorch.org/u/maajidkhann)\ **Replies:** 2\ **Last updated:** [February 8, 2024, 3:46am UTC](https://dev-discuss.pytorch.org/t/contributing-to-pytorch-documentation/1866 "2024-02-08T03:46:23Z")
Hello Community, we have recently merged our code to Pytorch (Disables denormal floating numbers on ARM CPU by maajidkhann · Pull Request #115184 · pytorch/pytorch · GitHub ) and we are yet to update the documentation. J… --- ## [Join the PyTorch Fall Docathon!](https://dev-discuss.pytorch.org/t/join-the-pytorch-fall-docathon/1585)
**Author:** [@svekars](https://dev-discuss.pytorch.org/u/svekars)\ **Replies:** 0\ **Last updated:** [October 18, 2023, 6:02pm UTC](https://dev-discuss.pytorch.org/t/join-the-pytorch-fall-docathon/1585 "2023-10-18T18:02:16Z")
Come join us for the PyTorch Fall Docathon: Nov 1 - 15, 2023! Whether you’re a seasoned PyTorch developer or just starting out, the docathon is a fantastic way to contribute to the project and make a real impact. We’… --- ## [Summation bfloat16](https://dev-discuss.pytorch.org/t/summation-bfloat16/390)
**Author:** [@dwidemann-lm](https://dev-discuss.pytorch.org/u/dwidemann-lm)\ **Replies:** 4\ **Last updated:** [November 4, 2021, 6:07pm UTC](https://dev-discuss.pytorch.org/t/summation-bfloat16/390 "2021-11-04T18:07:41Z")
Hi, I’m seeing that torch’s summation of a bfloat16 tensor is more accurate than my naive summation, e.g. x.sum() is better than x\[0\] +…+ x\[n-1\]. Could somebody please point me towards where in the repo is the code for …