-
Notifications
You must be signed in to change notification settings - Fork 607
Update how we input kwargs #314
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D49218534 |
Summary: X-link: pytorch/executorch#314 Previously, the code for passing inputs to exported program was: ``` if kwargs: return (args, kwargs) else: return args ``` However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments. So I updated the code to just always keep the kwargs around cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng Differential Revision: D49218534 Pulled By: angelayi
38f1aab
to
c649912
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
Summary: X-link: pytorch/executorch#314 Previously, the code for passing inputs to exported program was: ``` if kwargs: return (args, kwargs) else: return args ``` However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments. So I updated the code to just always keep the kwargs around cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng Reviewed By: zhxchen17 Differential Revision: D49218534 Pulled By: angelayi
c649912
to
2abf1fa
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
2c8dc34
to
02b0b9e
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D49218534 |
Summary: X-link: pytorch/executorch#314 Previously, the code for passing inputs to exported program was: ``` if kwargs: return (args, kwargs) else: return args ``` However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments. So I updated the code to just always keep the kwargs around cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng Reviewed By: zhxchen17 Differential Revision: D49218534 Pulled By: angelayi
02b0b9e
to
4e11669
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
4e11669
to
89b8d84
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
89b8d84
to
8fdc23a
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
Summary: X-link: pytorch/executorch#314 Previously, the code for passing inputs to exported program was: ``` if kwargs: return (args, kwargs) else: return args ``` However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments. So I updated the code to just always keep the kwargs around cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng Reviewed By: zhxchen17 Differential Revision: D49218534 Pulled By: angelayi
8fdc23a
to
49468c3
Compare
Summary: Previously, the code for passing inputs to exported program was: ``` if kwargs: return (args, kwargs) else: return args ``` However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments. So I updated the code to just always keep the kwargs around cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng X-link: pytorch/pytorch#109160 Reviewed By: zhxchen17 Differential Revision: D49218534 Pulled By: angelayi
This pull request was exported from Phabricator. Differential Revision: D49218534 |
49468c3
to
e4f738a
Compare
This pull request was exported from Phabricator. Differential Revision: D49218534 |
Summary:
Previously, the code for passing inputs to exported program was:
However, this causes some inconsistency where if the original input contains args and kwargs, the treespec would be a tuple containing a tuple of arguments, and a dictionary of keyword arguments. But if the original input only contained args, the treespec would just be a tuple of arguments.
So I updated the code to just always keep the kwargs around
cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx chenyang78 aakhundov kadeng
X-link: pytorch/pytorch#109160
Differential Revision: D49218534
Pulled By: angelayi