Oh, no, I can work around it. I am thinking of people that will end up
with the same problem in the future. If there is no plan to support
deepcopy why do not specialize deepcopy to show an error message and
abort?
As it is just a stub, I can write it and make a pull request for it
too. I suppose that the better is to specialize it for the concrete
class and not the AbstractModel, as someone may want to implement a
model that supports deepcopy.
I will submit a change to the documentation soon. I just don’t know if
it is not kinda long considering the size of the issue. Feel free to
say to me rewrite it.