List view
- Due by December 19, 2025•2/2 issues closed
- Due by November 28, 2025•13/13 issues closed
- No due date•2/2 issues closed
A bug fix release
No due date•5/5 issues closed- No due date•4/4 issues closed
Drop support for Python 3.5, 3.6 and 3.7.
Due by April 13, 2024•16/16 issues closedA bug fix release.
No due date•18/18 issues closedA bug fix release.
No due date•4/4 issues closedBug fix release.
No due date•1/1 issues closedRemove support for older Python versions, bug fixes. sqlparse now requries Python>=3.5
Due by October 10, 2020•9/9 issues closed- No due date•18/18 issues closed
- No due date•24/24 issues closed
- No due date•10/10 issues closed
- No due date•10/10 issues closed
- No due date•8/8 issues closed
- No due date•4/4 issues closed
Hotfix release
No due date•3/3 issues closedThis is a bug fix release (if needed). All new development will go into 0.2.0.
No due date- No due date•6/6 issues closed
- No due date•5/5 issues closed
- No due date•20/20 issues closed
A bug fix release
No due date•5/5 issues closedGoals so far: - bug fixes
No due date•1/1 issues closed- No due date•2/2 issues closed
- No due date•3/3 issues closed
Bug fix release.
No due date•5/5 issues closedGoals so far: - clean up some internals
No due date•8/8 issues closedgoals (so far) - bug fixes
No due date•4/4 issues closedGoals (so far): - improve Python 3 compatibility
No due date•2/2 issues closedMaInly bug-fixing Transition to callables
No due date•6/6 issues closedGoals (so far): - remove extras - improve filter stack (callables, etc.) - performance improvements - code cleanup (esp. grouping) - switch to single code base for Python 2 and 3 - remove unused code (have a look at coverage, not all code seems to be actually used) - add support for additional statement types - keep API intact
No due date•31/31 issues closedBug fix release.
Due by May 5, 2012•5/5 issues closed