Update poetry lock to allow SQLAlchemy v2

[baron]

It seems that #1578 adds support for SQLAlchemy v2 but the poetry lock file is still at 1.4.46.

[baron]

It seems that jupyter-cache is another blocking dependency:

jupyter-cache https://github.com/hwchase17/langchain/blob/master/poetry.lock#L2526 https://github.com/executablebooks/jupyter-cache/issues/92 https://github.com/executablebooks/jupyter-cache/pull/93

This dependency was introduced in pull request #534 but jupyter_cache doesn't seem to be called anywhere in the code base when you do grep -r "jupyter_cache" . in the root directory of the project.

[jzluo]

jupyter_cache is a dependency for myst-nb which is used in creating the docs. I do have a PR open with jupyter-cache to allow SQLAlchemy 2.

[baron]

Thanks for the clarification and your efforts. Added some reactions and a "+1".

[winstxnhdw]

jupyter-cache hasn't been maintained for more than 9 months, should we start looking for alternatives? Being blocked from SQLAlchemy 2.0 is pretty painful.

[elonzh]

Should we add SALAlchemy as an optional dependency?

[ryugonomura]

Should we add SALAlchemy as an optional dependency?

@elonzh Please add SALAlchemy 2.0.

[KennyRich]

@hwchase17 Please any update on this? Can I open a PR to fix this?

[vnktsh]

@jzluo Can we mark myst-nb as optional dependency? SQLAlchemy is such an important library for many data projects and being blocked because of rarely used feature is big pain.