tree_processing - Elegant composition of tree-traversal algorithms
Installation
pip install tree_processing
tl;dr
Stop writing complex logic with os.walk like this:
results = []
for (path, dirnames, filenames) in os.walk(x):
# Compare certain files between x and y folder hierarchies.
for filename in filenames:
if not valid_filename(filename):
continue
x_path = os.path.join(path, filename)
if filter_path(x_path):
continue
y_path = os.path.join(y, os.path.relpath(path, x), filename)
results.append(compare(x_path, y_path))
to_recurse = []
for dirname in dirnames:
dirpath = os.path.join(path, dirname)
if valid_foldername(dirname) and not filter_path(dirpath):
to_recurse.append(dirname)
dirnames[:] = to_recurse
Use tree_processing, and write code like this instead:
traversal = topdown(make_root(x, y), folders_and_files.which(~filter_path))
process_folder = recurse_into_folders.which(valid_foldername)
process_file = compare_files.which(valid_filename)
accumulate = accumulator([], append_not_none)
results = traversal(accumulate(process_folder, process_file))
And use the same tools to process tree data structures in your code, too.
How it Works
Conceptually, these tree traversals involve four separate tasks:
- Actually discovering and iterating over nodes of the tree
- Deciding which nodes are relevant to the overall process (filtering)
- Operating on the relevant nodes
- Accumulating results from the operations
But the obvious way to write the code is complex, because the code for those tasks is complected. The goal of tree_processing is to let you think about those tasks separately, and combine them in a simple, boilerplate-free way. (It also allows describing the accumulation of results declaratively, rather than explicitly repeatedly modifying an accumulator variable inside a loop.)
First, given an abstract root node and a getter (rule for finding the children of a node), a traversal algorithm produces a Traversal object representing the entire tree. This can be iterated over like a generator for lower-level use, but the main use case is to call the Traversal to process the entire tree. Traversal is a class, but the design of tree_processing otherwise shuns classes — you can express the missing pieces of logic in the natural way, with ordinary functions.
The per-node actions are represented by arbitrary callable objects — you can pass functions directly, or instances of your own classes implementing __call__. A Traversal is called using either a single callable applied to all nodes, or two callables (one for internal nodes and one for leaf nodes).
Passing an initial value for accumulation signals that results should be accumulated. The processing callables will be passed the current accumulated value and are responsible for updating it, which they can do either by mutating the existing value or returning a new one. Helper decorators are provided to combine processing and accumulation logic; this provides flexibility without forcing you to pass a separate argument for the accumulation function.
Filtering is naturally a modification to other parts of the process, rather than a step in itself. But tree_processing still simplifies the code greatly, by providing some useful decorators. You can combine decorated "filter" callables into a "chain", and easily apply their logic to filter the tree traversal ahead of time, as well as to "reject" nodes during processing. (In a top-down traversal, if an internal node is rejected, its children will not be visited.)
tree_processing offers special support for filesystem operations, in the form of common actions compatible with the traversal system and a standard getter (by default, it does not follow symlinks and treats them as ordinary files). But the same core logic lets you process any kind of tree by just filling in the blanks in the algorithm.
Examples
Copy all files, folders and symlinks (like shutil.copytree with symlinks=True and copy_function=shutil.copy:
from tree_processing.traversal import topdown
from tree_processing.actions.filesystem import copy_files, propagate_folders
from tree_processing.node_getters.filesystem import default_get, make_root
def copy_tree(src, dst):
topdown(make_root(src, dst), default_get)(propagate_folders, copy_files)
List non-hidden files in non-hidden folders:
from tree_processing.traversal import topdown
from tree_processing.actions.filesystem import hidden
from tree_processing.node_getters.filesystem import default_get, make_root
def display_files(node):
if not node.internal:
print(f'{node.current}')
def print_visible_files(src):
# When a single action is passed, it's used for both files and folders.
topdown(make_root(src), default_get.which(~hidden))(display_files)
Count lines in all files (assuming only directories and regular files):
from tree_processing import sum_results
from tree_processing.traversal import topdown
from tree_processing.node_getters.filesystem import default_get, make_root
def add_lines(node):
if node.internal:
return 0 # skip folders
file_path = node.current
# The built-in traversals provide pathlib.Path objects.
assert file_path.is_file()
with open(file_path) as f:
return sum(1 for _ in f)
# The `sum_results` decorator adds up results from processing each node.
# It can also be used with ordinary `@decorator` syntax — but because that
# involves calling it ahead of time, the sum would not be reset between
# traversals. Using it this way, the sum starts from 0 each time that
# `count_all_lines` is called.
def count_all_lines(src):
return topdown(make_root(src), default_get)(sum_results(add_lines))
Using separate file and folder handlers, the product of file name lengths:
from operator import mul # to build a custom accumulator
from tree_processing import accumulator
from tree_processing.traversal import topdown
from tree_processing.node_getters.filesystem import default_get, make_root
def multiplicative_identity(node):
return 1
def file_name_length(node):
return len(node.name)
def file_name_length_product(src):
# The decorator can also be applied to a pair of callables:
process = accumulator(1, mul)(multiplicative_identity, file_name_length)
return topdown(make_root(src), default_get)(process)
Copyright © 2025 Karl Knechtel
This project is open source software, distributed under the terms of the MIT License.
Please see LICENSE.txt for details.
Metadata
Release files for tree-processing 0.4.1
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 |
|---|---|---|---|---|
| tree_processing-0.4.1.tar.gz | 10.7 kB | Without provenance | Details for tree_processing-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tree_processing-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for tree_processing-0.4.1-py3-none-any.whl |
Total release size: 21.0 kB
Release files / tree_processing-0.4.1.tar.gz
| Download URL | tree_processing-0.4.1.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04dbabf2c6ac3b104037e8aeb451bfc84811c84655ac68d9d8069234f56caad9
|
|
BLAKE2b-256 checksum How to use checksums |
8b216a8d8606dbc17ccc7b99dce3e1e91017a80b9888cbe059b1526a6305f367
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / tree_processing-0.4.1-py3-none-any.whl
| Download URL | tree_processing-0.4.1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5198bc36e2053ac024e9e06ca7cd33b42d285c7b3c53e491448c9eab16f0df77
|
|
BLAKE2b-256 checksum How to use checksums |
9966bb0bb25eee1bc292f2918c81b93aab87f34a1a2524c7ceab82abe1f8284d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for tree-processing 0.4.1
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.