Chore: Add 'mps' to the docs of tensor_attributes

[LukasM937]

Since PyTorch supports 'mps' (Apple metal) devices it should be reflected in the documentation.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/86585

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 448c503:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: LukasM937 / name: Lukas Mührke (9aa7288)

[soulitzer]

Hi @LukasM937, thanks for the update! I'm not sure we want to land this right now though because mps is still a prototype feature. cc @albanD

[albanD]

There are many other device available. I don't think this list is intended to be exhaustive.
cc @kulinseth

[kulinseth]

There are many other device available. I don't think this list is intended to be exhaustive.
cc @kulinseth
I think it makes sense to add it, still

[kulinseth]

Looks fine to me

[albanD]

@pytorchbot merge -g

[albanD]

@pytorchbot merge -g

[pytorchmergebot]

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[albanD]

Could you fix the lint please?

[pytorchmergebot]

Merge failed

Reason: The following mandatory check(s) failed (Rule superuser):

• Lint

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

[LukasM937]

Could you fix the lint please?

Should be solved now.

Also since you mention it, shouldn't an exhaustive list be linked? just as an idea though.

[LukasM937]

Could you fix the lint please?

Should be solved now.

Also since you mention it, shouldn't an exhaustive list be linked? just as an idea though.

But I understood the issues of maintaining such an list, In this case, I think it makes it more accessible for new users on an M1 machine.

[albanD]

@pytorchbot merge -g

[pytorchmergebot]

Merge started

Your change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @LukasM937.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

[LukasM937]

@albanD could you add the labels, it looks like I don't have permissions to add them.

'release notes: mps'
'topics: documentation'