-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CLN: compat.bind_method and core.common.bind_method #10566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
well the doc string explains this |
The doc string says the first case (PY2) can't be used in PY3, but since the second case can be used in both PY2 and PY3 there's no need to have an |
see what u do I don't recall exactly what this is for |
This line in ops.py seems to be the only place it's used. |
There will probably be some reason, as also python-future proposes this for py2/3 compatible code: http://python-future.org/what_else.html#binding-a-method-to-a-class (but indeed, one of the two implementation can be removed, I propose to keep the one in compat?) |
I don't feel strongly about removing PY2:
|
closed by #10643 |
I'd like to remove
bind_method
from here and here, as I don't see any benefit oversetattr(cls, name, func)
. Is there any?The text was updated successfully, but these errors were encountered: