-
Notifications
You must be signed in to change notification settings - Fork 14
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
pip install is broken with error from libsql-ffi
#58
Comments
The problem is somewhere in the sqlite3mc CMake-build in https://github.com/tursodatabase/libsql. Looks like some kind of a Apple toolchain change, discussed here for example: ponylang/ponyc#3684 |
I found a temporary fix for macOS:
|
Anyone being able to solve this on windows? I have the same problem (Windows 11) |
can confirm the same, this is bad . really bad. DX should be first thing a DBaaS company should focus on. *constructive criticism. |
@nikhil-swamix Yes. That is why this package is tagged as experimental. |
I tweaked the README.md to make the experimental status more explicit: f4ff8ad |
agreed the package name is explicit enough. btw the bun guys were able to support windows eventually maybe some references can be taken from there. currently i want to use turso with python, if i use default sql library (inbuilt) or other flavors, lets say peewee or sqlalchemy,
vector search+gold standard of local development ie sqlite, is one of the reason im testing before recommending (mostly startups), and also the generous free tier. please let me know very approx ETA as per your estimates on resolution of this. |
I am trying to install the latest v0.0.34 on my machine (Intel Mac, Monterey and Python v3.8.19). It fails with following:
I tried installing an older version (0.0.28) which had worked earlier, but it is failing with the same error:
Even the older versions point to the same libsql-ffi version (
libsql-ffi v0.2.1
). This highlights another issue, we are not pinning the dependencies.first reported here - https://discord.com/channels/933071162680958986/1241858417757257809/1241858417757257809
The text was updated successfully, but these errors were encountered: