Barry A. Warsaw added the comment: I'd be very hesitant to add anything to 2.7 that changes (even broken) behavior here. It might make more sense to backport the more strict checks to 3.5. OTOH, we can save people from all programming errors, and if warnings are basically ignored (plus, adding warnings *can* break things), then perhaps we should only document the limitations.
There's already some description of copy()'s limitations, so either add another warning there, or in the static method objects description in section 3.2 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29902> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
