Making dist.get_default_group private for PT1 release (#14767)
authorTeng Li <tengli@fb.com>
Wed, 5 Dec 2018 03:20:08 +0000 (19:20 -0800)
committerFacebook Github Bot <facebook-github-bot@users.noreply.github.com>
Wed, 5 Dec 2018 03:22:24 +0000 (19:22 -0800)
commit2d3cf98b49541b0ba4d9db3b2f86cbbf3c5c71a4
treea292119cd6b74580a77869592c3dbc82144d5ec4
parent33ea7eafefb6a74d4d87b4e02f8d182640051ffc
Making dist.get_default_group private for PT1 release (#14767)

Summary:
When I wrote the frontend API, it is designed on not letting users use the default_group directly on any functions.  It should really be private.

All collectives are supposed to either use group.WORLD, or anything that comes out of new_group. That was the initial design.

We need to make a TODO on removing group.WORLD one day. It exists for backward compatibility reasons and adds lots of complexity.
Pull Request resolved: https://github.com/pytorch/pytorch/pull/14767

Reviewed By: pietern

Differential Revision: D13330655

Pulled By: teng-li

fbshipit-source-id: ace107e1c3a9b3910a300b22815a9e8096fafb1c
docs/source/distributed.rst
test/test_distributed.py
torch/distributed/distributed_c10d.py
torch/nn/parallel/distributed.py