New submission from Guðni Nathan <[email protected]>:
Currently, attempting to deepcopy a property object will result in an
unexpected TypeError:
>>> import copy
>>> obj = property()
>>> new_obj = copy.deepcopy(obj)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "C:\Program
Files\WindowsApps\PythonSoftwareFoundation.Python.3.7_3.7.1264.0_x64__qbz5n2kfra8p0\lib\copy.py",
line 169, in deepcopy
rv = reductor(4)
TypeError: can't pickle property objects
What I believe is happening here is that since property objects are not treated
by the copy module as atomic, they are passed off to be pickled and so our
error is raised.
This can be fixed in a similar manner to how it works for type objects,
function objects and more.
Adding a single line of code to Lib/copy.py after line 208:
d[property] = _deepcopy_atomic
Means that property objects will be treated as atomic, and therefore returned
as-is.
----------
components: Library (Lib)
messages: 353375
nosy: Guðni Nathan
priority: normal
severity: normal
status: open
title: Deepcopying property objects results in unexpected TypeError
type: behavior
versions: Python 3.7
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue38293>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
