Tyler Yep
Tyler Yep
Ah, makes sense, thank you for clarifying!
Hmm I think the M1 Macs could be the source of the problem, but I have no way of testing it out or trying to find a fix. The next...
Yep, that's a mistake with the packaging setup. Will accept a PR fixing this!
HI @ssbarnea, I would be open to moving this plugin to the PyCQA org. Could you explain what the process to do so looks like?
With the rise of Ruff and the inclusion of this flake8 rule already, I don't think ownership of this plugin needs to change anymore. To a faster future!
This seems better-suited (and already implemented) in `mypy --strict`, or in various sub-settings. I don't think Pylint needs to duplicate this functionality, and if it did, it would likely slow...
Oh, I didn't realize that pylint already parsed type annotations - in that case, this seems like a perfectly valid idea then.
Hmm, perhaps recursive layers? Not sure what this could be
Try using explicit kwargs: `summary(model, x=x, y=y)` Or using a tuple for input data: `summary(model, input_data=(x,y)`
Good idea, PRs implementing this behavior are welcome! Based on the output value, it should choose the most appropriate unit automatically.