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
While working on support for SQLAlchemy 2.0 on behalf of crate/crate-python#485 and crate/crate-python#488, we discovered that the updated code will no longer be compatible with SQLAlchemy 1.3.
If you agree, we will have to come up with a proper release and deprecation plan.
My proposal, already briefly discussed with @seut, would be to run a 0.30.0 maintenance release, which adds a corresponding warning for users who are still on SA13. Then, we would move on by integrating the SA20 changes, and probably release them with a crate-python 1.0.0 version (maybe after running a few 1.0.0bX releases). In this manner, the 1.x series will support SA14 and SA20, while the 0.x series would still be able to receive maintenance patches, and keeps supporting SA13.
With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered:
Hi.
While working on support for SQLAlchemy 2.0 on behalf of crate/crate-python#485 and crate/crate-python#488, we discovered that the updated code will no longer be compatible with SQLAlchemy 1.3.
If you agree, we will have to come up with a proper release and deprecation plan.
My proposal, already briefly discussed with @seut, would be to run a 0.30.0 maintenance release, which adds a corresponding warning for users who are still on SA13. Then, we would move on by integrating the SA20 changes, and probably release them with a crate-python 1.0.0 version (maybe after running a few 1.0.0bX releases). In this manner, the 1.x series will support SA14 and SA20, while the 0.x series would still be able to receive maintenance patches, and keeps supporting SA13.
With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: