Open atechnicolorskye opened 1 year ago
Any luck with this @atechnicolorskye? I am getting the same error on Ubuntu 22.04.2 running on a cloud server with an AMD EPYC 7B13 processor.
I am getting the same error on an M1 MBA. Has anyone made any progress so far?
same here on a M1 MBP.
I have the same problem. New install of Ubuntu 22.04 LTS. i7 processor. Has anybody above solved this? What past version of Ubuntu do I need to install? @atechnicolorskye @sachitsaksena @emilhe @wseis
Update. Skranger is working for me with Python 3.10. I get the above error with 3.11 and 3.12.
Skranger is working for me with Python 3.10. It's not working with 3.11 or 3.12. See my above comment for the error returned. There have been some very significant performance improvements with 3.11 and 3.12.
Can also confirm that this does not work in a Debian-based Docker container with Python 3.11. But it does work when I rollback the container to Python 3.10.
Any idea what might have changed with Python 3.11, @crflynn?
Same problem here with while executing python 3.11 on a Debian 12 machine. Both pip and conda instalation raised the error. As a workaround, reverting to python 3.10 and intalling skranger 0.8.0 (pip) solved the error.
I have rolled back to Python 3.10 but still get this error. I am on Windows. Any help?
Sorry to ask but are there any plans to fix this issue @crflynn? Unfortunately I will have to drop skranger
as a dependency in if it is not supported for up-to-date python versions, a pity since it is the fastest implementation out there. I'd gladly open a PR but I have no clue what might be triggering this error. If you have any idea I could try to look into it and fix it.
Hi,
I'm on an M2 Mac and I get the above error whereas it works fine with my Intel Mac. Do you have any idea why this is happening?
Cheers, Sky