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
Upgrade to SQLAlchemy 2.x #478
Comments
The sqlalchemy 2.x dependency was introduced in pandas 2.2.0, which was released on 2024-01-19. |
@mattholy thank you for opening this issue. We plan to update to SQLAlchemy 2.x at some point but this is not a priority / we are not working on it now. |
Hi @andrii-i, thanks for your work on this project, we use it extensively and it's really great! Is there any chance you are able to upgrade to SQLAlchemy 2.x? We are finding this is a major blocker recently. Many thanks! |
Hi @adampinky85. Glad you are finding Jupyter Scheduler useful. We are still planning to update to SQLAlchemy 2.x at some point but this is not a priority / we are not working on it now. At the same time, could you please share more about why Jupyter Scheduler not using SQLAlchemy 2.x is a major blocker for you recently? |
thanks @andrii-i, yes we manage environments running jupyterlabs and the kernel is built with a large number dependencies for research purposes including jupyter-scheduler. On the EC2 instance we also have a number of project that are cloned and available for users to access from their notebooks (e.g., analysis libraries or business logic). There are now a number of libraries that require SQLAlchemy 2.x. which are not compatible to run from our notebooks. jupyter-scheduler is exactly the right tool for our use case, we don't need airflow / apscheduler etc. as it requires more effort for users. They want to be able to run their notebooks easily with a few clicks. |
Hi all,
Pandas is now depending on SQLAlchemy 2.x
When using pandas and jupyterlab at the same time, which is a very common situation, it may case some conflicts.
jupyter-scheduler/pyproject.toml
Line 36 in 1b50f81
The text was updated successfully, but these errors were encountered: