[issue26202] The range() object is deepcopied as atomic
Ethan Furman
report at bugs.python.org
Mon Jan 25 16:24:46 EST 2016
Ethan Furman added the comment:
I don't have much experience with the copy module, but I don't see any problems with the code.
Does copy.copy suffer from the same problem? If yes, is it fixed with this same patch, or is more work needed?
----------
nosy: +ethan.furman
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26202>
_______________________________________
More information about the Python-bugs-list
mailing list