You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An %%ai magic works anywhere the IPython kernel runs (JupyterLab, Jupyter Notebook, Google Colab, VSCode, etc.).
Problem
So I tried JupyterLite. In the running of "%pip install jupyter_ai_magics", I met
"ValueError: Can't find a pure Python 3 wheel for 'sqlalchemy<2,>=1'."
Proposed Solution
I understand JupyterLite is a special version.
If in theory, Jupyter-ai cannot work in it, please declare the limitation. If possible, but it takes time, please put JupyterLite support on your to-do list.
Thanks,
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Likely one of them depends on sqlalchemy which triggers the issue.
Not sure the package needs all these dependencies to work properly. Ideally it could support some of them as optional dependencies so it could indeed be used (maybe partially) in the browser via JupyterLite.
An %%ai magic works anywhere the IPython kernel runs (JupyterLab, Jupyter Notebook, Google Colab, VSCode, etc.).
Problem
So I tried JupyterLite. In the running of "%pip install jupyter_ai_magics", I met
"ValueError: Can't find a pure Python 3 wheel for 'sqlalchemy<2,>=1'."
Proposed Solution
I understand JupyterLite is a special version.
If in theory, Jupyter-ai cannot work in it, please declare the limitation. If possible, but it takes time, please put JupyterLite support on your to-do list.
Thanks,
The text was updated successfully, but these errors were encountered: