Closed anentropic closed 3 years ago
I prefer to keep this open until @marcdownie (and others?) can confirm it also works for them.
We can still do a new release in the meantime with what we have now - would also make it easier for others to test it.
I prefer to keep this open until @marcdownie (and others?) can confirm it also works for them.
We can still do a new release in the meantime with what we have now - would also make it easier for others to test it.
Let's do that!
I'm back (sorry about the pause); and I'm up to date with main, out of conda, using the pre-release pip cffi, not having an x64 parallel brew installation any more, and ... I'm still on the cffi python MemoryError.
The MemoryError is the only remaining issue at this point, and so far only @marcdownie has reported it with a conda environment...
To be clear (because this is quite the issue!) I was only not getting the MemoryError in my base conda; I've never made it past the MemoryError outside of a conda environment. And, this morning, after much uninstalling bits of my system, now even conda is throwing the MemoryError.
Results! I walked away from my python superfund site onto a fresh machine. Either the prerelease cffi, or the lack of detritus left over from x64 brew, is in fact the missing ingredient.
WGPU_BACKEND_TYPE=Metal PYGLFW_LIBRARY=/opt/homebrew/Cellar/glfw/3.3.4/lib/libglfw.3.3.dylib python3.9 examples/triangle_glfw.py
Gives me a triangle!
Awesome! Too bad it's still a mystery as to what exactly causes the MemoryError, but at least you get to experience the triangle now!
I think the MemoryError is picking up the wrong ffi or trampoline lib, the one without Apple's secret write+execute trampoline sauce. The real mystery to me is how conda managed to move ahead of pip here, which led me to see a working triangle last week. I'd still feel better if I can verify that this all works in a fresh venv, but for now, I'm back to feeling ok about wgpu-py on M1. So a LGTM for this and #190 from me.
There it is!
Overview (edited by AK):
get_surface_id_from_canvas
work for M1. #195I was getting this error:
https://nomodulenamed.com/m/wheel.pep425tags says:
But:
https://wheel.readthedocs.io/en/stable/news.html
...sounded possibly relevant. The previous version to that is
0.34.2
which was also mentioned on the nomodulenamed page
And yes, this fixed it:
and poetry install then succeeded.
I'm not totally sure where the problem originates, whether you need to pin
wheel==0.34.2
in yoursetup.py
or some other part of the build machinery is to blame.(Pinning
wheel==0.34.2
in mypyproject.toml
didn't help, because Poetry didn't know about the dependency relationship and tries to installwgpu
first... so for now it's fixed by manually installing oldwheel
version in my virtualenv)Just posting this in case it helps someone else.