ShowCallStack
Shows a simplified view of the call stack.
This module is similar to Python's built-in traceback and inspect modules, but is easier to use and displays more simple output. This module is useful for demonstrating what the call stack looks like during recursive function calls. Simply add a from showcallstack import showCallStack line and then call showCallStack() from wherever you wish to see the state of the call stack and the local variables in each call frame.
Example Usage
This program...
from showcallstack import showcallstack
def a():
varA = 42
b()
def b():
varB = 86
c()
def c():
varC = 99
showcallstack()
spam = 'SPAM!
a()
...outputs this:
The call stack is 3 call(s) deep:
(Here is the "bottom" of the call stack.)
Local variables of call to a():
varA (type: int) == 42
Local variables of call to b():
varB (type: int) == 86
Local variables of call to c():
varC (type: int) == 99
(Here is the "top" of the call stack.)
Global variables:
spam (type: str) == 'SPAM!'
This recursive factorial program...
from showcallstack import showcallstack
def factorial(num):
showcallstack()
if num == 1:
return 1
else:
return num * factorial(num - 1)
factorial(4)
...outputs this:
The call stack is 1 call(s) deep:
(Here is the "bottom" of the call stack.)
Local variables of call to factorial():
num (type: int) == 4
(Here is the "top" of the call stack.)
Global variables:
No global variables.
The call stack is 2 call(s) deep:
(Here is the "bottom" of the call stack.)
Local variables of call to factorial():
num (type: int) == 4
Local variables of call to factorial():
num (type: int) == 3
(Here is the "top" of the call stack.)
Global variables:
No global variables.
The call stack is 3 call(s) deep:
(Here is the "bottom" of the call stack.)
Local variables of call to factorial():
num (type: int) == 4
Local variables of call to factorial():
num (type: int) == 3
Local variables of call to factorial():
num (type: int) == 2
(Here is the "top" of the call stack.)
Global variables:
No global variables.
The call stack is 4 call(s) deep:
(Here is the "bottom" of the call stack.)
Local variables of call to factorial():
num (type: int) == 4
Local variables of call to factorial():
num (type: int) == 3
Local variables of call to factorial():
num (type: int) == 2
Local variables of call to factorial():
num (type: int) == 1
(Here is the "top" of the call stack.)
Global variables:
No global variables.
You can also call the showcallstack.getcallstack() function to get this output as a list of strings.
Support
If you find this project helpful and would like to support its development, consider donating to its creator on Patreon.
Metadata
Release files for ShowCallStack 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ShowCallStack-0.3.0.tar.gz | 4.2 kB | Without provenance | Details for ShowCallStack-0.3.0.tar.gz |
Release files / ShowCallStack-0.3.0.tar.gz
| Download URL | ShowCallStack-0.3.0.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f60b0145477af8a4a8486a9b47d9297028246ffc4f0e656d42e5b8ecc26cb71
|
|
BLAKE2b-256 checksum How to use checksums |
8b5de23ccbbb618c192a375c081580145efec7d965d8a2255a2e4169e8371d84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.2
|
Security for ShowCallStack 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.