Skip to content

Dedupe no parsing __torch_function__ handler #75159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from

Conversation

ezyang
Copy link
Contributor

@ezyang ezyang commented Apr 3, 2022

Stack from ghstack (oldest at bottom):

Now there is truly only one way to call torch_function
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang [email protected]

Now there is truly only one way to call __torch_function__
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang <[email protected]>

[ghstack-poisoned]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 3, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 433f675 (more details on the Dr. CI page):


💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@ezyang ezyang requested review from peterbell10 and albanD April 3, 2022 15:37
ezyang added 2 commits April 3, 2022 08:42
Now there is truly only one way to call __torch_function__
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang <ezyangfb.com>

[ghstack-poisoned]
Now there is truly only one way to call __torch_function__
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang <ezyangfb.com>

[ghstack-poisoned]
Now there is truly only one way to call __torch_function__
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang <ezyangfb.com>

[ghstack-poisoned]
@albanD albanD removed their request for review April 4, 2022 14:19
@ezyang
Copy link
Contributor Author

ezyang commented Apr 4, 2022

@pytorchbot merge this

@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2022

Hey @ezyang.
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.

@ezyang ezyang added release notes: composability release notes category topic: not user facing topic category labels Apr 4, 2022
facebook-github-bot pushed a commit that referenced this pull request Apr 5, 2022
Summary:
Now there is truly only one way to call __torch_function__
and that is via handle_torch_function_no_python_arg_parser

Signed-off-by: Edward Z. Yang <ezyangfb.com>

Pull Request resolved: #75159

Approved by: https://github.com/zou3519

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/e3848d75dfd41909d1a2885bf272d2588b25150f

Reviewed By: atalman

Differential Revision: D35359959

Pulled By: ezyang

fbshipit-source-id: e9a4c01200d24a8ac486b1738b30cbdd6c1e91bf
@facebook-github-bot facebook-github-bot deleted the gh/ezyang/1117/head branch April 8, 2022 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants