executing
PyPIv2.2.1Get the currently executing AST node of a frame, and other information
Adopt with care
executing is usable, with caveats. Last published 373 days ago. 2 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- CMaintenance: grade C, Fair — worth a look.
Last published 373 days ago. 2 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 28 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
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 executing to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Python
- python >=3.8
Quick start
A usage example from the executing README.
import executing
node = executing.Source.executing(frame).nodeUsed by
Popular packages that depend on executing.
Relationship graph
Dependencies (left) and dependents (right) of executing.
Frequently installed together
Release history
2 releases in the last two years, typically about 43 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.2.1latest | 1 year ago | 28 KB | MIT |
| 2.2.0 | 1 year ago | 26 KB | MIT |
| 2.1.0 | 2 years ago | 25 KB | MIT |
| 2.0.1 | 2 years ago | 24 KB | MIT |
| 2.0.0 | 2 years ago | 24 KB | MIT |
| 1.2.0 | 3 years ago | 24 KB | MIT |
| 1.1.1 | 3 years ago | 22 KB | MIT |
| 1.1.0 | 4 years ago | 22 KB | MIT |
| 1.0.0 | 4 years ago | 16 KB | MIT |
| 0.10.0 | 4 years ago | 17 KB | MIT |
| 0.9.1 | 4 years ago | 16 KB | MIT |
| 0.9.0 | 4 years ago | 16 KB | MIT |
| 0.8.3 | 4 years ago | 16 KB | MIT |
| 0.8.2 | 5 years ago | 16 KB | MIT |
| 0.8.1 | 5 years ago | 16 KB | MIT |
Overview
executing is an PyPI package that get the currently executing AST node of a frame, and other information. It has 1 known dependents in the graph. The latest version is 2.2.1, released under the MIT license.
Who should use it
Teams working in the PyPI ecosystem who need get the currently executing AST node of a frame, and other information 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
- Clear open-source license (MIT).
- Zero runtime dependencies — minimal footprint.
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use executing?
executing is usable, with caveats. Last published 373 days ago. 2 releases in the last 2 years.
How do I install executing?
Run `pip install executing` to add executing to your PyPI project.
What license is executing released under?
executing is distributed under the MIT license.
How popular is executing?
PyPI does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on executing.
Is executing still maintained?
The most recent release of executing (v2.2.1) was published 1 year ago.