Brendt Wohlberg

Could you check your `sporco` version? Both the dev version and most recent release have this as the first import statement: ```python from __future__ import absolute_import, division, print_function ``` which...

Sorry for the very long delay. It looks as if `pyfftw` is still unsupported on MacOS ARM hardware. It is possible to use `sporco` without `pyfftw`, but many of the...

Closing for now. Please respond here if and when you would like to pursue this further.

Could you try running the example scripts and report back on which ones work and which don't?

The error log makes me suspect that this might actually be a problem in `pyfftw`, which is used by the `sporco` solvers, which are called by the `sporco-cuda` tests to...

I just read your response on #8. Could you please also summarize the differences between the environment in which `sporco-cuda` works with no problems, and the one that results in...

Just to confirm, `sporco-cuda` is working fine on Machine 2, but gives the stack smashing error on Machine 1? Could you try using python 3.8 via conda (see the script...

Strange that you end up with Python 3.7 instead of 3.8; I suppose it's related to your use of a virtualenv. I don't think it matters, though, since 3.7 is...

Thanks for your debugging efforts. I will certainly update the installation instructions if we can figure out which of the different steps you took made a critical difference. For example,...

So the only difference is whether you install sporco from the cloned repo (which leads to failure) or from conda (which leads to success)? I'm at a loss to explain...