-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Daft equivalent of polars-lts-cpu #3564
Comments
Hello @jpedrick-numeus can you specify which issues specifically you are experiencing? Is there some instruction set (say SIMD) that the x86 emulator you are using is not supoprting? Thank you :) |
I'm not an expert regarding instruction sets. The module crashes on import.
I'm running Docker Machine on an M1 MacBook w/ an x86_64 docker image (mambaorg/micromamba) w/ the Rosetta emulator. |
@samster25 do you know anything about this? |
Hi @jpedrick-numeus, I'm working on also publishing a LTS CPU version of Daft similarly to what you suggested! |
Hi @jpedrick-numeus, We just started publishing a LTS version of daft here: https://pypi.org/project/daft-lts/0.4.2/#description Can you try installing |
Sure thing! Thanks! |
hi @jpedrick-numeus how did it work out for you? |
Hi @samster25 , I did some very light testing, but I've also noticed with the latest version of daft running on an x86_64 container on an M1 mac I'm able to run |
Is your feature request related to a problem?
I often develop for an x86 environment on an M1 MacBook using an x86_64 docker container. Related to #1021 as I consider adding Daft to my technology stack it causes some issues when testing/building docker images that incorporate Daft.
Describe the solution you'd like
Polars solves this problem by providing a package
polars-lts-cpu
which runs ok on an M1 chipset inside an x86_64 docker container. I don't have any strong opinions on the particular solution. As an end user here I would only like to be able to run Daft on an x86_64 VM running on an M1 MacBook in a docker container.Describe alternatives you've considered
Developing on a remote x86_64 based EC2 instance
Additional Context
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: