This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.


[ghstack-poisoned]

This added the numpy typing plugin to mypy config so that we could
use it for DeviceMesh typing annotations

Please see #92931 about why we need this. For example, we are currently saving the DeviceMesh's mesh field as torch.Tensor, where when we do sth like:
```python
with FakeTensorMode():
    device_mesh = DeviceMesh("cuda", torch.arange(4))
```
It would throw error because FakeTensorMode or any TorchDispatchMode tracks every tensor creation and interactions. While DeviceMesh just want to save a nd-array to record the mesh topology, and would like to avoid the interaction with subsystems like FakeTensor, so we want to support saving `mesh` as numpy array instead.

Pull Request resolved: #92930
Approved by: https://github.com/ezyang, https://github.com/malfet

This removes the typing hack, part of #92931

[ghstack-poisoned]

This removes the typing hack, part of #92931

[ghstack-poisoned]

This removes the typing hack, part of #92931

[ghstack-poisoned]

This removes the typing hack, part of #92931

ghstack-source-id: fdb52c7
Pull Request resolved: #94526

This removes the typing hack, part of #92931

ghstack-source-id: e5890ae
Pull Request resolved: #94526

This removes the typing hack, part of #92931

[ghstack-poisoned]

This removes the typing hack, part of #92931

[ghstack-poisoned]

This removes the typing hack, part of #92931
Pull Request resolved: #94526
Approved by: https://github.com/XilunWu