-
Notifications
You must be signed in to change notification settings - Fork 215
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
Removing the Python Native API #1153
Conversation
Signed-off-by: yes <[email protected]>
@teoparvanov @vrancurel I can still see pipelines and code related to interactive API. Will this be removed? |
Hi @tanwarsh, thanks for refreshing the PR. Could you please remove the failing Interactive API examples from the CI also? |
Signed-off-by: yes <[email protected]>
Signed-off-by: yes <[email protected]>
Signed-off-by: yes <[email protected]>
I have removed the dependency on python native API in openfl/openfl/interface/interactive_api. |
Signed-off-by: yes <[email protected]>
Thanks @tanwarsh ! Let's freeze this PR for the time of the 1.7 release (we now have a good understanding of the "blast radius" of removing the Python Native API). As discussed offline, the next step is to produce a new, more conservative PR where you would:
|
Closing the PR as this will be merged later. Will create another PR to deprecate Python Native API. |
Deprecate Python API:
This PR will be merged after discussion on FETS Chanllenge as mentioned by Kevin in #1143 (comment)