Guido van Rossum added the comment: > This is not really my area of expertise, but I would have thought if you > defined a __special__ method to something illegal (non-callable, or wrong > signature) it would be reasonable for Python to raise an error at class > definition (or assignment) time, not just later when you try to use it.
No, that's not the intention. > Somewhere I think the documentation says you are only allowed to use these > names as documented. Indeed, but it's not enforced. What it means is that when the next release of Python (or a different implementation) changes the meaning of a __special__ name, you can't complain that your code broke. (And please don't go suggesting that we start enforcing it.) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25958> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
