Skip to content
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

[Python] Merge native and ChipStack #20437

Closed
mrjerryjohns opened this issue Jul 7, 2022 · 2 comments
Closed

[Python] Merge native and ChipStack #20437

mrjerryjohns opened this issue Jul 7, 2022 · 2 comments
Labels
python stale Stale issue or PR

Comments

@mrjerryjohns
Copy link
Contributor

Problem

Once #20234 merges, we'll have a split initialization model where native handles MemoryInit, and ChipStack handles the remaining bits needed for safe initialization of the stack. This is not ideal, since both are effectively serving two halves of the same initialization story.

We should remove native, and consolidate all initialization in ChipStack, and have each Python module effectively call into the ChipStack singleton to safely call into the SDK through ChipStack.Call or ChipStack.CallAsync methods.

@stale
Copy link

stale bot commented Jan 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale Stale issue or PR label Jan 5, 2023
@stale
Copy link

stale bot commented Jan 14, 2023

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Jan 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
python stale Stale issue or PR
Projects
None yet
Development

No branches or pull requests

1 participant