Deploy preview for pytorch-tutorials-preview ready!

Built with commit a701926

https://deploy-preview-1061--pytorch-tutorials-preview.netlify.app

It would be much better if the tutorial code was written in runnable fashion (either by writing the tutorial directly as a python file with sphinx-gallery, or keeping the Python code separate from the rst file) so that we can test the tutorial in the future. See #1057 for an example of how to do this.

cc @jlin27

IIRC, tutorials for v1.6 need to use release/1.6 as the target branch.

Don't we need to commit the tutorial in master first though?

@ezyang Thanks for the great suggestion! I used literalinclude and this approach is much better.

@mrshenli @jlin27 Do we still need to add examples in pytorch/examples#800 if we have a runnable example in the tutorials repo? It seems like we can keep the runnable example in the tutorials repo and just refer to it in our tutorial?

@pritamdamania87

IIRC, tutorials for v1.6 need to use release/1.6 as the target branch.

Don't we need to commit the tutorial in master first though?
The pytorch/tutorials branches are backwards from pytorch/pytorch. In pytorch/tutorials, master is live/stable (not sure the history but it is what it is rn :) ) For tutorials planned for 1.6, please submit them to the release/1.6 branch and I'll get them live on master for the release.

@mrshenli @jlin27 Do we still need to add examples in pytorch/examples#800 if we have a runnable example in the tutorials repo? It seems like we can keep the runnable example in the tutorials repo and just refer to it in our tutorial?

I think the pro of keeping it in the examples as well is that there are a number of other related examples there already and it would be advantageous for users to find this one there. Only downside is maintaining both.

Created a PR against release/1.6: #1071

@mrshenli @jlin27 Do we still need to add examples in pytorch/examples#800 if we have a runnable example in the tutorials repo? It seems like we can keep the runnable example in the tutorials repo and just refer to it in our tutorial?

I am not sure about the plan here. @ezyang do you know if we are going to completely get rid the pytorch/examples repo and stick all source code in the pytorch/tutorials repo (I assume all examples should have their associated tutorial)?

If this is the plan, then yes, let's move all distributed examples source code to tutorials repo.

If this is not the plan, then what is our guidelines to users regarding what to expect in pytorch/examples vs pytorch/tutorials? Looks like both repos will become some random subset of the example projects we have.

Another question for @jlin27 is we do plan to let tutorials CI to run the source code included in tutorials? Or will this be test be installed to the examples repo?

Another question for @jlin27 is we do plan to let tutorials CI to run the source code included in tutorials? Or will this be test be installed to the examples repo?

The plan is to have it on both examples and tutorials. I haven't heard anything about getting rid of pytorch/examples, but please do comment if that's been under discussion.

I don't think it's a good idea to have two copies of the code. Perhaps an easy compromise is to submodule examples inside tutorials. Then you can literalinclude the examples code directly.