Get SQLAlchemy

Version 1.3

Latest 1.3 Release: 1.3.1 (1.3.1 via Cheeseshop) (CHANGES)

SQLAlchemy 1.3.1 is signed using Michael Bayer’s PGP key id C4DAFEE1 (use gpg --recv-keys C4DAFEE1 to import).

Please be sure to review the 1.2 to 1.3 migration guide, found at What's New in 1.3?, for full details on changes made since 1.2.

Version 1.2

Latest 1.2 Release: 1.2.18 (1.2.18 via Cheeseshop) (CHANGES)

Release Support: Maintenance Mode

Please note: the 1.2 series is the current "Maintenance" series. Updates for critical fixes will be made available as needed, but applications which continue to be under active development are advised to begin upgrading to the current series of SQLAlchemy (currently the 1.3 series).

SQLAlchemy 1.2.18 is signed using Michael Bayer’s PGP key id C4DAFEE1 (use gpg --recv-keys C4DAFEE1 to import).

Please be sure to review the 1.1 to 1.2 migration guide, found at What's New in 1.2?, for full details on changes made since 1.1.

Development Versions

SQLAlchemy on GitHub

For further details on Git repository access please see development.


SQLAlchemy is covered by the MIT License.

Release Status

Major Version First Release Latest Release Latest Version Release Status
1.3 [docs] [What's New?] 2018-11-17 (beta) 2019-03-09 1.3.1 [changes] Current Release
1.2 [docs] [What's New?] 2017-07-10 (beta) 2019-02-15 1.2.18 [changes] Maintenance
1.1 [docs] [What's New?] 2016-06-16 (beta) 2018-03-06 1.1.18 [changes] EOL
1.0 [What's New?] 2015-03-13 (beta) 2017-08-03 1.0.19 [changes] EOL
0.9 2013-12-30 2015-07-22 0.9.10 [changes] EOL
0.8 2012-12-14 (beta) 2014-07-22 0.8.7 [changes] EOL
0.7 2011-05-21 2013-02-08 0.7.10 [changes] EOL
0.6 2010-02-03 (beta) 2012-05-06 0.6.9 [changes] EOL
0.5 2008-06-12 (beta) 2010-01-16 0.5.8 [changes] EOL
0.4 2007-08-12 (beta) 2008-10-12 0.4.8 [changes] EOL
0.3 2006-10-22 2007-10-14 0.3.11 [changes] EOL
0.2 2006-05-27 2006-09-05 0.2.8 [changes] EOL
0.1 2006-02-14 2006-05-05 0.1.7 [changes] EOL

About Release Status Categories

The following table summarizes each status category:

Release Status Explanation
Development Active development for the next major release of SQLAlchemy. The "development" status is by definition not released on Pypi and only exists within the git repository, typically under the master branch. When the first release of the "development" status is created, the status moves to "beta".
Beta Evaluation releases for the current development version. These releases are available on Pypi, however include a 'b' character in their version name so that per pep-0440 these releases will not be installed by the pip tool unless the --pre flag is specified. The "beta" status is generally mutually exclusive versus the "development" status.
Current Release The current official release of SQLAlchemy. Ongoing work is performed to close out regressions and bugs that can still be applied without significant risk of destabilization. Applications which are under active development should seek to always refer to at least the "current" release.
Maintenance The maintenance series exists when the "beta" series has become "current", and the previous "current" series becomes "maintenance". The maintenance series accepts a limited set of critical bug fixes as they are encountered, as it is expected that applications under active development will be migrating to the "current" release if they have not done so already. Once the next development version begins, the "maintenance" series is no longer released and moves to "EOL".
EOL This release version is no longer maintained and is considered legacy. Applications in production use against an EOL milestone are strongly advised to upgrade to a newer version.