We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
_ is not a bad dunder name. _ is often used functions whose names are not relevant. Please consider excluding _ from PLW3201's rules.:
_
prediction_energy = custom_jvp_method( # type: ignore[assignment] # pyright: ignore prediction_energy, nondiff_argnums=(0, 2, 3)) @prediction_energy.defjvp # type: ignore[no-redef, attr-defined, misc] def _(self, observation: FisherMessage, weights: Weights, primals: tuple[RivalMessage], tangents: tuple[RivalMessage] ) -> tuple[JaxRealArray, JaxRealArray]: natural_explanation, = primals
The text was updated successfully, but these errors were encountered:
Incidentally, not sure where to write this, but the previewed rules that were useful to me were:
Sorry, something went wrong.
Seems reasonable, it's almost certainly intentional.
bad-dunder-method-name
@NeilGirdhar perhaps you're looking for #7993?
Avoid flagging bad-dunder-method-name for _ (#8015)
d942a77
This is almost certainly _not_ an accidentally mistyped dunder method. Closes #8005.
charliermarsh
Successfully merging a pull request may close this issue.
_
is not a bad dunder name._
is often used functions whose names are not relevant. Please consider excluding_
from PLW3201's rules.:The text was updated successfully, but these errors were encountered: