Debug #125 (dataclasses for expressions)

[matthiasdiener]

attrs: #125

[alexfikl]

FWIW, tried some of this in inducer/pytential#223. I tried to use pytest-memray to see which tests use the most memory, but didn't get anywhere..

[matthiasdiener]

It seems the problem is that too many warnings are issued 😵‍💫 ....

I was not able to run all of pytential's pytests with all of the warnings enabled, even locally; from just running some of the tests, the total number of warnings that I disabled in a433807 must be in the millions...

What we could do is:

• remove the warnings (like in a433807)
• or perhaps filter them for pytest runs (see e.g. https://docs.pytest.org/en/stable/how-to/capture-warnings.html#controlling-warnings) Edit: this does not work, see 3381324

@inducer

[inducer]

It seems the problem is that too many warnings are issued 😵‍💫 ....

OMG! That makes so much sense, but it never occurred to me. 🤦

[inducer]

The latest update to #125 drops the stacklevels on these to 1, which should result in a big reduction in the duplication of these warnings.

[alexfikl]

Well.. 🤯 Amazing catch!

[matthiasdiener]

Closing, #125 appears to work now.