<commit_before>pepy
====
pepy (pronounced p-pie) is a python binding to the pe-parse parser.

Building
========
If you can build pe-parse and have a working python environment (headers and
libraries) you can build pepy.

1. Build pepy:
  * python setup.py build
2. Install pepy:
  * python setup.py install

Authors
=======
pe-parse was designed and implemented by <NAME> (<EMAIL>)
pepy was written by <NAME> (<EMAIL>)
<commit_msg>Start to document things.<commit_after>pepy
====
pepy (pronounced p-pie) is a python binding to the pe-parse parser.

Building
========
If you can build pe-parse and have a working python environment (headers and
libraries) you can build pepy.

1. Build pepy:
  * python setup.py build
2. Install pepy:
  * python setup.py install

Using
=====
There are a number of objects involved in pepy. The main one is the *parsed*
object. This object is returned by the *parse* method.

`
import pepy
p = pepy.parse("/path/to/exe")
`

The *parsed* object has a number of methods:

* get_entry_point: Return the entry point address
* get_bytes: Return the first N bytes at a given address
* get_sections: Return a list of section objects
* get_imports: Return a list of import objects.
* get_exports: Return a list of export objects.
* get_relocations: Return a list of relocation objects

Authors
=======
pe-parse was designed and implemented by <NAME> (<EMAIL>)
pepy was written by <NAME> (<EMAIL>)

{'fraction_non_alphanumeric': 0.10204081632653061, 'fraction_numerical': 0.0028149190710767065, 'mean_word_length': 4.286245353159852, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6491319', 'n_tokens_mistral': 447, 'n_tokens_neox': 434, 'n_words': 200}