[issue26202] The range() object is deepcopied as atomic

[Ethan Furman]

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>
_______________________________________