-
Notifications
You must be signed in to change notification settings - Fork 36
Use multipy.package in multipy/runtime
#111
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
@PaliC has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Codecov Report
@@ Coverage Diff @@
## main #111 +/- ##
=======================================
Coverage 88.86% 88.86%
=======================================
Files 65 65
Lines 3869 3869
=======================================
Hits 3438 3438
Misses 431 431
Help us with your feedback. Take ten seconds to tell us how you rate us. |
@PaliC has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Summary: This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. Pull Request resolved: #111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: 0ca53ea57c3cb46fba70465cb671ffe7e9e68785
This pull request was exported from Phabricator. Differential Revision: D38337551 |
Summary: This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. Pull Request resolved: #111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: 8ec7316225284bd0adc2a9c9bdbe82c5d15bb295
Summary: This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. X-link: meta-pytorch/multipy#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: 44faa10a8b995b47f257d6fe20d9caa335237c9e
This pull request was exported from Phabricator. Differential Revision: D38337551 |
Summary: This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. X-link: meta-pytorch/multipy#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC Pull Request resolved: #82690 Approved by: https://github.com/d4l3k
Summary: Pull Request resolved: #82690 This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. X-link: meta-pytorch/multipy#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: dec35e0f07efa1c989f6356dd073dfddd12a186e
Summary: X-link: pytorch/pytorch#82690 This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. Pull Request resolved: meta-pytorch#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: dec35e0f07efa1c989f6356dd073dfddd12a186e
Use multipy.package in `multipy/runtime` (#82690) Summary: X-link: pytorch/pytorch#82690 This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. Pull Request resolved: meta-pytorch#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: dec35e0f07efa1c989f6356dd073dfddd12a186e
Use multipy.package in `multipy/runtime` (#82690) Summary: X-link: pytorch/pytorch#82690 This change points multipy::runtime to use multipy.package instead of torch.package by copying `_deploy.py` (which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allow `multipy::runtime` to access `multipy.package` and `_deploy.py`. Pull Request resolved: meta-pytorch#111 Reviewed By: d4l3k Differential Revision: D38337551 Pulled By: PaliC fbshipit-source-id: dec35e0f07efa1c989f6356dd073dfddd12a186e
This change points multipy::runtime to use multipy.package instead of torch.package by copying
_deploy.py
(which is used in order to pass objects in and out of interpreters) into multipy as well as making the neccessary changes to allowmultipy::runtime
to accessmultipy.package
and_deploy.py
.