Skip to content

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Sep 15, 2022

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 15, 2022

🔗 Helpful Links

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

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

✅ No Failures

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

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

ezyang added a commit that referenced this pull request Sep 15, 2022
Signed-off-by: Edward Z. Yang <ezyangfb.com>

ghstack-source-id: c8a3eca
Pull Request resolved: #85090
def __call__(self, *args, **kwargs):
return self._op(*args, **kwargs or {})

def __getattr__(self, key):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why does this work? is key also in the attrs of self, or are we now causing an AttributeError and that's desirable for some reason?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed this mostly because I didn't know why we have it, and because in a subsequent PR I am going to redefine getattr for other reasons

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok.

@ezyang
Copy link
Contributor Author

ezyang commented Sep 16, 2022

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

@github-actions
Copy link
Contributor

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.

@facebook-github-bot facebook-github-bot deleted the gh/ezyang/1384/head branch September 19, 2022 14:19
mehtanirav pushed a commit that referenced this pull request Oct 4, 2022
Signed-off-by: Edward Z. Yang <ezyang@fb.com>
Pull Request resolved: #85090
Approved by: https://github.com/wconstab
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