Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Top 13 Python Code Analysis and Linter Projects
-
-
scalene
Scalene: a high-performance, high-precision CPU, GPU, and memory profiler for Python with AI-powered optimization proposals
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
MonkeyType
A Python library that generates static type annotations by collecting runtime types (by Instagram)
-
coala
coala provides a unified command-line interface for linting and fixing all your code, regardless of the programming languages you use.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Flake8
flake8 is a python tool that glues together pycodestyle, pyflakes, mccabe, and third-party plugins to check the style and quality of some python code.
-
prospector
Inspects Python source files and provides information about type and location of classes, methods etc
-
unimport
:rocket: The ultimate linter and formatter for removing unused import statements in your code. (by hakancelikdev)
Project mention: The GIL can now be disabled in Python's main branch | news.ycombinator.com | 2024-03-11
I collected a list of profilers (also memory profilers, also specifically for Python) here: https://github.com/albertz/wiki/blob/master/profiling.md
Currently I actually need a Python memory profiler, because I want to figure out whether there is some memory leak in my application (PyTorch based training script), and where exactly (in this case, it's not a problem of GPU memory, but CPU memory).
I tried Scalene (https://github.com/plasma-umass/scalene), which seems to be powerful, but somehow the output it gives me is not useful at all? It doesn't really give me a flamegraph, or a list of the top lines with memory allocations, but instead it gives me a listing of all source code lines, and prints some (very sparse) information on each line. So I need to search through that listing now by hand to find the spots? Maybe I just don't know how to use it properly.
I tried Memray, but first ran into an issue (https://github.com/bloomberg/memray/issues/212), but after using some workaround, it worked now. I get a flamegraph out, but it doesn't really seem accurate? After a while, there don't seem to be any new memory allocations at all anymore, and I don't quite trust that this is correct.
There is also Austin (https://github.com/P403n1x87/austin), which I also wanted to try (have not yet).
Somehow this experience so far was very disappointing.
(Side node, I debugged some very strange memory allocation behavior of Python before, where all local variables were kept around after an exception, even though I made sure there is no reference anymore to the exception object, to the traceback, etc, and I even called frame.clear() for all frames to really clear it. It turns out, frame.f_locals will create another copy of all the local variables, and the exception object and all the locals in the other frame still stay alive until you access frame.f_locals again. At that point, it will sync the f_locals again with the real (fast) locals, and then it can finally free everything. It was quite annoying to find the source of this problem and to find workarounds for it. https://github.com/python/cpython/issues/113939)
A little introduction about pylint. Pylint is a static code analyzer, it analyses your code without actually running it. Pylint looks for potential errors, gives suggestions on coding standards that your code is not adhering to, potential places where refactoring might help, and also warnings about smelly code.
MonkeyType collects runtime types of function arguments and return values, and can automatically generate stub files or add type annotations directly to your Python code based on the types collected at runtime.
Project mention: To Review or Not to Review: The Debate on Mandatory Code Reviews | dev.to | 2024-04-24Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.
Pylama is a code audit tool for Python that wraps tools like Pylint, pycodestyle, PyFlakes, McCabe, and others to provide a unified interface.
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
Python Code Analysis and Linter related posts
- Enhance Your Project Quality with These Top Python Libraries
- The GIL can now be disabled in Python's main branch
- Polars – A bird's eye view of Polars
- Static Typing for Python
- W1203: logging-fstring-interpolation (Solved)
- Smooth Packaging: Flowing from Source to PyPi with GitLab Pipelines
- Python 3.13 Gets a JIT
-
A note from our sponsor - InfluxDB
www.influxdata.com | 25 Apr 2024
Index
What are some of the best open-source Code Analysis and Linter projects in Python? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | mypy | 17,506 |
| 2 | scalene | 11,163 |
| 3 | Pylint | 5,110 |
| 4 | MonkeyType | 4,533 |
| 5 | vprof | 3,948 |
| 6 | code2flow | 3,709 |
| 7 | coala | 3,512 |
| 8 | Flake8 | 3,257 |
| 9 | prospector | 1,908 |
| 10 | pydeps | 1,611 |
| 11 | pylama | 1,038 |
| 12 | PythonBuddy | 273 |
| 13 | unimport | 237 |
Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com