evo-gpfe - Genetic Programming Feature Engineer
A scikit-learn-compatible symbolic feature constructor for tabular data,
powered by DEAP. evo-gpfe evolves expression
trees that combine the original features into new, informative ones,
complementing evo-gafs (which selects among existing
features).
Part of the evo-suite family (import name: evo_gpfe).
Documentation: https://evo-suite.readthedocs.io/
Why evo-gpfe?
| Capability | evo-gpfe |
|---|---|
| Sequential hall-of-fame strategy: relevance minus redundancy minus parsimony | Yes |
| Protected primitives (safe division, log, sqrt, ...) so any random tree evaluates | Yes |
Multiple relevance metrics: mutual_info, correlation, spearman, model_score |
Yes |
| Anti-bloat: static tree-height limit and a parsimony penalty | Yes |
Native scikit-learn fit/transform/get_feature_names_out, usable in a Pipeline |
Yes |
Built-in multi-dataset GPBenchmarkRunner |
Yes |
Installation
pip install evo-gpfe # core
pip install "evo-gpfe[viz]" # + matplotlib for the plotting helpers
Quickstart
from sklearn.datasets import load_diabetes
from evo_gpfe import GPFeatureEngineer, GPConfig
X, y = load_diabetes(return_X_y=True, as_frame=True)
engineer = GPFeatureEngineer(
config=GPConfig(population_size=80, n_generations=20, n_features_to_generate=3, verbose=False)
)
engineer.fit(X, y)
print(engineer.summary())
X_augmented = engineer.transform(X)
print("Output features:", list(engineer.get_feature_names_out()))
The GP-then-GA combo
evo-gpfe and evo-gafs are independent but complementary: construct new
features with GP, then select the best subset (original + generated) with GA.
from evo_gafs import GAFeatureSelector, GAConfig
X_aug = engineer.fit_transform(X, y)
selector = GAFeatureSelector(estimator=..., feature_names=list(engineer.get_feature_names_out()))
selector.fit(X_aug, y)
See 06_gp_then_ga_pipeline.py in the repository's examples/evo-gpfe/
directory for the full example.
Documentation & examples
- Full documentation (user guide + API reference): https://evo-suite.readthedocs.io/
- Runnable examples: the repository's
examples/evo-gpfe/directory.
Citation
@software{evo_gpfe,
author = {Skrauba, Axel},
title = {evo-gpfe: Genetic Programming Feature Engineer for tabular data},
year = {2026},
version = {0.1.0},
url = {https://github.com/AxelSkrauba/evo-suite}
}
License
Metadata
Release files for evo-gpfe 0.1.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 | |
|---|---|---|---|
| evo_gpfe-0.1.0.tar.gz | 23.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| evo_gpfe-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.3 kB
Release files / evo_gpfe-0.1.0.tar.gz
| Download URL | evo_gpfe-0.1.0.tar.gz |
|---|---|
| Size | 23.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9f379975302f4dbf8bc76b346e9a34b9803cc868d2be1e924dfbd6798ff956e
|
|
BLAKE2b-256 checksum How to use checksums |
92c1b9c6d4ebd4f6a52fcf22d902be73aff21ef3e731197ed2b90fe5537808d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logRelease files / evo_gpfe-0.1.0-py3-none-any.whl
| Download URL | evo_gpfe-0.1.0-py3-none-any.whl |
|---|---|
| Size | 27.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1181172787b845d776e005e4170a1269236d13081370be1a4450ed2caba418b9
|
|
BLAKE2b-256 checksum How to use checksums |
87fdaec8138328d6dcf519bedde85ef2f3e651453c161b99cdf43c96bb625485
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency log