Metadata-Version: 2.1
Name: python_code_analyzer
Version: 1.0.8
Summary: A python code analyzer that high jacks the current settrace function to analyze executed code.
Home-page: https://github.com/josephedradan/code_analyzer
Author: Joseph Edradan
Author-email: edradanjoseph245@gmail.com
License: MIT
Keywords: python,analyzer,debugger,python code analyzer,python analyzer
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: Unix
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Requires-Python: >=3.7
Description-Content-Type: text/markdown
Provides-Extra: testing
License-File: LICENSE


# Code Analyzer

![PyPI - Python Version](https://img.shields.io/pypi/pyversions/python-code-analyzer)
[![PyPI version](https://badge.fury.io/py/python-code-analyzer.svg)](https://badge.fury.io/py/python-code-analyzer)
[![tests](https://github.com/josephedradan/code_analyzer/actions/workflows/test.yml/badge.svg)](https://github.com/josephedradan/code_analyzer/actions/workflows/test.yml)


### What is this?
A python code analyzer that allows you to visually see how your code works after executing code.
Alternatively, you can think of it as a python debugger that prints all the lines executed.

### Why would you use this?
Let's say you don't want to use a python debugger and you want to see how your code runs line by line printed out. You can import this module and add a few lines of code to initialize the analyzer and run your code, and
you will get a simple analysis of the code executed in your terminal or exported to a txt or html file. 

It is not advised to use this analyzer in a big project as the output won't fit in your terminal; though, using an export
method call to see the code in a file might be more useful/helpful.

### Requirements:
    python>=3.7
    rich
    colorama
    pandas

### Example:

    from code_analyzer import CodeAnalyzer
    
    code_analyzer = CodeAnalyzer()  # Initialize analyzer
    code_analyzer.start()
    
    # Comment that will be displayed on the next line
    code_analyzer.record_comment_for_interpretable_next("Function definition here!")
    
    
    def recursive(depth: int) -> int:
        # Comment that will be displayed on the previous line
        code_analyzer.record_comment_for_interpretable_previous({"__depth": depth})
        if depth <= 0:
            code_analyzer.record_comment_for_interpretable_next({"Final depth": depth})
            return depth
    
        return recursive(depth - 1)
    
    
    code_analyzer.record_comment_for_interpretable_next("This is where the fun begins")
    recursive(5)
    
    code_analyzer.stop()
    code_analyzer.print()
    
    # code_analyzer.get_code_analyzer_printer().print_debug()
    code_analyzer.get_code_analyzer_printer().export_to_txt()
    
    # code_analyzer.get_code_analyzer_printer().print_rich()  # export_rich_to_html prints to console by default
    code_analyzer.get_code_analyzer_printer().export_rich_to_html()
    
    Or just look at the other examples in examples folder.


### Output

![example_recursive.png](https://raw.githubusercontent.com/josephedradan/code_analyzer/main/images/example_recursive.png)

## [Rich output html](https://htmlpreview.github.io/?https://github.com/josephedradan/code_analyzer/blob/main/examples/example_recursive_code_analysis_rich.html)
### Notes

In the output of a print (Such as in the image above):

* Blue foreground code is a callable's definition.
* Green foreground code is a callable being executed.
* Red foreground text are {Variable: value} pairs found in between the `{}` brackets that are new to the current interpretable relative to its scope. 
* Purple foreground text are (arguments) found in between the `()` brackets passed to the method calls below:
    * .record_comment_for_interpretable_next(...) 
    * .record_comment_for_interpretable_previous(...)
    
In the output of a rich export (such as the .html files in the examples folder):

* Blue background code is a callable's definition.
* Green background code is a callable being executed.
* Orange foreground text are {Variable: value} pairs found in between the {} brackets that are new to the current interpretable relative to its scope. 
* Red foreground text are (arguments) found in between the () brackets passed to the method calls below:
    * .record_comment_for_interpretable_next(...) 
    * .record_comment_for_interpretable_previous(...)

__IF YOU SEE CODE THAT DOESN'T SEEM TO BE CODE THAT YOU SHOULD BE ANALYZING WHEN USING TYPE HINTING, ADD THE 
IMPORT BELOW TO THE TOP OF THE FILE TO POSSIBLY REMOVE IT__

    from __future__ import annotations

### Installation
    pip install python-code-analyzer

### [pypi](https://pypi.org/project/python-code-analyzer/)

__TODO:__
* Fancy visualizer
* Memory usage?
* Timing code?
* profiler (Time and calls amount)
