code-searcher 0.1.17

python package for code searching through whole code library

Table of Contents

• Short Overview.

• More info.

• Installation

• Typical examples of Usage

  • 1) To find all occurrences of some code.

  • 2) To find all occurrences of some regular expression pattern

  • 3) To see some statistics about your library.

  • 4) To add new files to examine.

  • 5) To get dictionary with content of all satisfy files.

• Links

• Releases

• Contributing

• Contacts

• License

Short Overview.

code_searcher is a simple Python package(py>=2.7 or py>=3.4) with the main purpose to make searching through your project codebase fast and simple.

Currently, fully supported file types are .py and .ipynb nonetheless, search functional can be applied to any file extensions which can be read as plain text in utf-8 encoding.

In additional it allows you to get some useful info about your project codebase. For more info check section: Typical examples of Usage

More info.

The main reason of building this package was to create universal tool to help support changes in functions signatures in both .py and .ipynb files.

It’s becoming quite useful when your project outgrows 1k lines of code and manual replacement becomes too annoying (Too easy to overlook replacement somewhere).

For more info check section: Typical examples of Usage

Installation

• Install via pip:

pip install code_searcher

Typical examples of Usage

In any case, the first thing you need to do is to import the necessary module and initialize class obj.

To do so you need to replace “path_to_folder_1” from the code below on most parent folder of all files you want to analyze.

If you have a code of all your projects structured that there is the main folder for all .py files and there is the main folder for all .ipynb files then use them.

from code_searcher import code_searcher_class
LIST_STR_FOLDERS_WHERE_TO_LOOK = ["path_to_folder_1", "path_to_folder_2", ...]
code_searcher_obj = code_searcher_class(
        LIST_STR_FOLDERS_WHERE_TO_LOOK,
        list_str_file_extensions=[".py", "ipynb"],
)

Please note that first initialization can be a long process if the folders where you search for files are deep and wide.

But after finding all files they won’t be downloaded again unless they were changed. So excellent performance is expected.

1) To find all occurrences of some code.

E.G. You’ve changed a function signature and want to do necessary changes in the library.

To find all the places where this function was used use the code below

code_searcher_obj.search_code_in_the_library(
    str_code_to_search="print_places_where_line_length_exceed_N",
    bool_is_to_search_case_sensitive=True,
)

Output:

For folder: c:\users\stanislav\desktop\my_python_projects\code_search_engine\project\code_searcher\src\code_searcher

--> For extension: .py
----> Found in:  code_searcher_class.py
------> 0) line: 93  Code_line: print_places_where_line_length_exceed_N(
------> 1) line: 444  Code_line: def print_places_where_line_length_exceed_N(

--> For extension: ipynb
----> NOTHING FOUND.

2) To find all occurrences of some regular expression pattern

code_searcher_obj.search_code_in_the_library_with_re(
    str_code_to_search="^from __future__ import[\s]+"
)

Output:

For folder: c:\users\stanislav\desktop\my_python_projects\code_search_engine\project\code_searcher\src\code_searcher

    --> For extension: .py
    ----> Found in:  additional_functions.py
    ------> 0) line: 12  Code_line: from __future__ import print_function
    ----> Found in:  code_searcher_class.py
    ------> 1) line: 11  Code_line: from __future__ import print_function
    ----> Found in:  decorators.py
    ------> 2) line: 12  Code_line: from __future__ import print_function
    ----> Found in:  working_with_files.py
    ------> 3) line: 12  Code_line: from __future__ import print_function

    --> For extension: ipynb
    ----> NOTHING FOUND.

3) To see some statistics about your library.

print(code_searcher_obj)

Output:

Folders to search in:
--> c:\users\stanislav\desktop\my_python_projects\code_search_engine\project\code_searcher\src\code_searcher
--> c:\users\stanislav\desktop\dashboard
Extensions to check:
--> .py
--> ipynb

Files Statistic of current code library:
--> For folder: c:\users\stanislav\desktop\my_python_projects\code_search_engine\project\code_searcher\src\code_searcher
--> Files_found = 5  Code_lines = 1203
----> .py:  Files_found = 5;  Code_lines = 1203;
----> ipynb:  Files_found = 0;  Code_lines = 0;
===============================================================================
--> For folder: c:\users\stanislav\desktop\dashboard
--> Files_found = 4  Code_lines = 175
----> .py:  Files_found = 0;  Code_lines = 0;
----> ipynb:  Files_found = 4;  Code_lines = 175;
===============================================================================

4) To add new files to examine.

If you’ve created a new file inside folder given to code_searcher then you should update files for code_searcher

code_searcher_obj.update_files()

5) To get dictionary with content of all satisfy files.

For now on this dictionary structure is

{“dir_path_1”: {“file_extension_1”: {“absolute_file_path_1”: str_file_content, ..}, ..}, ..}

code_searcher_obj.dict_str_file_by_path_by_ext_by_dir

Links

• Pypi

• readthedocs

• GitHub

Releases

See CHANGELOG.

Contributing

• Fork it (<https://github.com/stas-prokopiev/code_searcher/fork>)

• Create your feature branch (git checkout -b feature/fooBar)

• Commit your changes (git commit -am ‘Add some fooBar’)

• Push to the branch (git push origin feature/fooBar)

• Create a new Pull Request

Contacts

• Email: [e-mail]

• vk.com

• Facebook

License

This project is licensed under the MIT License.