copy operation is not atomic
Open
bug
- Dominant language
- Python
- Stars
- 30
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
if anything should go wrong during a graph copy operation, the original object will most likely be corrupted, since unpickleable member objects are deleted and then restored. Not sure how to fix this... some kind of try: except: wrapping so that the objects can be re-added before re-raising the exception?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.