[stubsabot] Mark SQLAlchemy as obsolete since 2.0.0

[github-actions]

Release: https://pypi.org/pypi/SQLAlchemy/2.0.0
Homepage: https://www.sqlalchemy.org

[JelleZijlstra]

We should probably not treat prereleases as obsoleting our stubs. Let's wait for 2.0.0 final.

[hauntsaninja]

PR to stubsabot welcome!

[Avasam]

On a sidenote, I'd like to be able to get the stubs at least on par with https://github.com/microsoft/python-type-stubs/tree/main/sqlalchemy (used by Pylance) so it can be dropped from there. Also reducing the confusingly high number of source of truths for SQLAlchemy stubs.
Then see how close together I can make types-sqlalchemy (no mypy plugin) and sqlalchemy2-stubs (uses mypy plugin). A lot of users (myself included) won't be able to immediately upgrade to 2.0 anyway.

Other question, is it possible to specify <2.0.0 in METADATA.toml ? We already know 2.0 will come typed and typeshed's stubs shouldn't be used with it. So I don't see any harm in at least doing that if possible.

[Avasam]

We should probably not treat prereleases as obsoleting our stubs. Let's wait for 2.0.0 final.

I think 2.0 just got out today and that's what stubsabot caught. But also says that it's technically been obsolete since the first beta (oldest py.typed version), which is also true.

[AlexWaygood]

On a sidenote, I'd like to be able to get the stubs at least on par with https://github.com/microsoft/python-type-stubs/tree/main/sqlalchemy (used by Pylance) so it can be dropped from there. Also reducing the confusingly high number of source of truths for SQLAlchemy stubs. Then see how close together I can make types-sqlalchemy (no mypy plugin) and sqlalchemy2-stubs (uses mypy plugin). A lot of users (myself included) won't be able to immediately upgrade to 2.0 anyway.

Other question, is it possible to specify <2.0.0 in METADATA.toml ? We already know 2.0 will come typed and typeshed's stubs shouldn't be used with it. So I don't see any harm in at least doing that if possible.

FWIW, marking the stubs as officially obsolete doesn't preclude us from making improvements to the stubs -- we can still make changes until they're deleted from typeshed. And we're also under no obligation to delete the stubs immediately after they've been marked obsolete for 6 months (though we almost certainly should if the maintainers ask us to).

[AlexWaygood]

I'm happy to merge this now that the first-release-with-py.typed thing has been corrected. It doesn't stop us from making improvements to our SQLAlchemy stubs in the intervening period before we remove them.