</>PackageGraphPackageGraph

sqlparse

PyPIv0.6.0

A non-validating SQL parser.

Not recommended for new projects

No — sqlparse should not be adopted for new projects. No license declared — you have no explicit right to use this code.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 27 days ago. 5 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 49 KB installed.

  • BSupply chain: grade B, Good.

    This package lists no maintainer.

  • FLicense: grade F, Failing.

    No license declared — you have no explicit right to use this code.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding sqlparse to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

49 KB
Install size

Unpacked size of this package plus its entire runtime tree.

Tree depth

Longest resolved dependency chain below this package.

Compatibility

Python
python >=3.10

Quick start

A usage example from the sqlparse README.

import sqlparse

sqlparse.split("select * from foo; select * from bar;")
# ['select * from foo;', 'select * from bar;']

Used by

Popular packages that depend on sqlparse.

Relationship graph

Dependencies (left) and dependents (right) of sqlparse.

Djangosqlparse
sqlparse dependencies dependents

Frequently installed together

Release history

4 releases in the last two years, typically about 209 days apart.

Recent versions of sqlparse
VersionPublishedSizeLicense
0.6.0latest27 days ago49 KB
0.5.58 months ago45 KB
0.5.49 months ago45 KB
0.5.31 year ago43 KB
0.5.21 year ago43 KB
0.5.12 years ago43 KB
0.5.02 years ago43 KB
0.4.43 years ago40 KB
0.4.34 years ago42 KB
0.4.25 years ago41 KB
0.4.16 years ago41 KB
0.4.06 years ago41 KB
0.3.16 years ago40 KB
0.3.07 years ago39 KB
0.2.49 years ago38 KB

Overview

sqlparse is an PyPI package that a non-validating SQL parser. It has 1 known dependents in the graph. The latest version is 0.6.0.

Who should use it

Teams working in the PyPI ecosystem who need a non-validating SQL parser and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your PyPI stack.

Pros

  • Zero runtime dependencies — minimal footprint.

Cons

  • No license detected — review usage terms before adopting.

Auto-generated from collected registry metadata. No external claims are inferred.

Frequently asked questions

Should I use sqlparse?

No — sqlparse should not be adopted for new projects. No license declared — you have no explicit right to use this code.

How do I install sqlparse?

Run `pip install sqlparse` to add sqlparse to your PyPI project.

What license is sqlparse released under?

No license was detected in sqlparse's metadata; review the repository before use.

How popular is sqlparse?

PyPI does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on sqlparse.

Is sqlparse still maintained?

The most recent release of sqlparse (v0.6.0) was published 27 days ago.