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

Non-pickle based serialization #32

Open
martintb opened this issue Mar 4, 2025 · 0 comments
Open

Non-pickle based serialization #32

martintb opened this issue Mar 4, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@martintb
Copy link
Collaborator

martintb commented Mar 4, 2025

We should be able to use the inspect module to get all of the arguments passed to a constructor. If we store this dictionary, we should be able to use this for both serialization/deserialization but also for recreating Pipeline incantations.

My thought is to place this in PipelineOp and have the storage be automatic and opaque to the user.

The only weak point in this scheme is that, if the user dynamically changes any variables, this won't be reflected in the serialized Pipeline. A workaround would be to modify the getattr so that it looks in the storage dictionary first before looking in the class members.

@martintb martintb added the enhancement New feature or request label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant