Alex Coleman

Just +1 on this, i've tried this today with a package using `unittest.TestCase` for all the tests and I don't get any memray output: ``` $ pytest -v --memray ======================================...

Although in all fairness the [`pytest` docs on using unittest](https://docs.pytest.org/en/7.1.x/how-to/unittest.html#pytest-features-in-unittest-testcase-subclasses) says: > The following pytest features do not work, and probably never will due to different design philosophies: > -...

Had this issue today when using VSCode Python Extension (v2023.14.0) Test debugger in WSL2. Worked around it by changing the above setting but be great to know if this could...

Notwithstanding that this repo hasn't had a lot of recent action on it. Try changing the workflow permissions of your actions in the Repo settings.  This appeared to fix...

There are examples on SQLite docs of using `:memory:` as a [URI filename](https://www.sqlite.org/inmemorydb.html) with the syntax `file::memory:` so I believe it is an accepted syntax.

So the issue here is that by default the architecture of the new Mac M1s is using arm64 which i'd wager a guess these conda libraries haven't been built against...

I'd be happy to have a look at containerising this tool. I've used both Docker and Singularity in the past so can definitely aim to get rMAP containers for both....