We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thanks for this very useful package! It solves a genuine problem with python's "all or nothing" approach to async programming.
I noticed that the classes produced by Synchronizer.create_blocking are not pickleable, even if the classes they wrap are.
Synchronizer.create_blocking
I then had a look at the tests and saw this comment:
synchronicity/test/pickle_test.py
Lines 12 to 20 in f65617b
This makes me think there is some history here...
If I wanted to make my wrapped classes pickleable, could you give me any pointers on where to start?
The text was updated successfully, but these errors were encountered:
honestly, i don't remember – i just tried to run the test again and it fails in some very opaque way :(
synchronicity is overdue for a refactoring – i think it would be good to revisit things like this!
Sorry, something went wrong.
No branches or pull requests
Thanks for this very useful package! It solves a genuine problem with python's "all or nothing" approach to async programming.
I noticed that the classes produced by
Synchronizer.create_blocking
are not pickleable, even if the classes they wrap are.I then had a look at the tests and saw this comment:
synchronicity/test/pickle_test.py
Lines 12 to 20 in f65617b
This makes me think there is some history here...
If I wanted to make my wrapped classes pickleable, could you give me any pointers on where to start?
The text was updated successfully, but these errors were encountered: