You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
That binding=True is required for functools.wraps to work. Context: #6555
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
user202729
changed the title
[ENH] Explain effect of binding=False on @functools.wraps(f)
[ENH] Explain effect of binding=False on @functools.wraps(f) in the documentation of compiler directives
Dec 9, 2024
I do agree with could improve the documentation for the binding directive - it does leave you a little unclear what it's actually for.
I'm reluctant to start listing every individual thing that binding=False disables/breaks. Mainly because there's a lot of them. And because it's not actually deliberately disabling features - it just isn't using our nicer wrapper class. The better way of thinking of it is:
binding=True behaves more like a Python function in almost every way,
By the way, does binding=True result in slower function call in general? ( sagemath/sage#26254 says that there is a performance degradation which I assume is what they are mainly concerned about )
I haven't actually measured it in recent memory. I wouldn't be surprised if it was a little slower, but probably pretty close on versions of Python that support vectorcall.
Is your feature request related to a problem? Please describe.
That
binding=True
is required forfunctools.wraps
to work. Context: #6555Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: