Closed maximumspatium closed 6 years ago
I believe I hit that once also, and did something to work around that too. So how about we trying to fix it better this time? The issues seems to be exactly that "from copy import copy" is used somewhere, creating ambiguity between a module and a function name. And the right way to solve it would be use namespace reference (e.g. copy.copy()) everywhere. Let me know if you agree and I can fix it.
Let me know if you agree and I can fix it.
Sure, +1 for a better fix (if you'll be able to spot the issue).
Putting copy.copy(node_props)
right before deepcopy invocation results in the same error. On the other hand, copy(node_props)
works...
"from copy import copy" is used somewhere
Yep, that's core.py...
Another attempt to do the things right...
Merged, thanks!
Note that this is a part of bigger issue: https://github.com/pfalcon/ScratchABlock/issues/17 , for which I appreciate feedback.
I encountered an input that triggers the following import failure in decomp:split_node():
It looks like something "shadows" python's copy. Hence this simple fix.