R. David Murray added the comment: By the way, when I say "again", I'm referring to the "return type of alternative constructors" thread:
http://www.mail-archive.com/python-dev@python.org/msg92163.html This is effectively an extension of that discussion, because replace is an alternative constructor, with the additional complication of taking an existing instance as input. Rereading that thread, I think Guido's answer is that the subclass API needs to be clearly documented: http://www.mail-archive.com/python-dev@python.org/msg92191.html Which I guess means we get to decide what it is, and then figure out how to implement it. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20371> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
