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
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! 👋
@janzinho
Thanks for opening this issue. This is probably a breaking change that will require some regression testing. Would you like to open a PR for this change?
Thank you for answer. I think I don’t have the necessary know-how to create a pull request with a solution proposal. Is there any other way I can help or contribute?
Hi @janzinho. This was fixed by PR #521 (fixed issue #478 which was a duplicate of this issue but it slipped past us) so any Jupyter Scheduler >= 2.7 would depend on SQLAlchemy >= 2.
Problem
Hi,
I can only run jupyter-scheduler when using sqlalchemy==1.4.48 and ipython-sql==0.4.1 which are both old versions.
Proposed Solution
It would be great if you could upgrade jupyter-scheduler to be compatible to sqlalchemy-2.0.15 and ipython-sql-0.5.0.
Best,
Jan
The text was updated successfully, but these errors were encountered: