Kantun
A lightweight, model-agnostic hyperparameter tuning library.
Built as a companion to KANBoost, but with zero
hard dependency on it — Kantun works with any estimator that follows a
scikit-learn-like fit/predict/predict_proba interface. Use it with
KANBoost, with RandomForestClassifier, with your own custom model —
your choice.
Why a separate package?
Not everyone using KANBoost needs hyperparameter search, and not everyone doing hyperparameter search needs KANBoost. Splitting them keeps each library's dependency footprint minimal and lets Kantun be useful on its own.
Install
pip install kantun
To also tune KANBoost models, install it separately:
pip install kanboost
Quickstart
from kantun import KantunSearch
from kanboost import KANBoostClassifier
param_space = {
"n_estimators": [30, 60, 100],
"learning_rate": [0.1, 0.2, 0.3],
"kan_hidden": [3, 4, 6],
"kan_grid": [2, 3],
}
search = KantunSearch(
KANBoostClassifier,
param_space,
n_iter=10,
cv=3,
scoring="auc",
)
search.fit(X, y)
print(search.best_params_, search.best_score_)
best_model = search.best_estimator_ # ready to use
results_df = search.results_dataframe() # sorted leaderboard
Works with any sklearn-style estimator, not just KANBoost
from sklearn.ensemble import RandomForestClassifier
from kantun import KantunSearch
search = KantunSearch(
RandomForestClassifier,
{"n_estimators": [50, 100], "max_depth": [3, 5, None]},
n_iter=5, cv=3, scoring="f1",
use_eval_set=False, # RandomForestClassifier.fit() has no eval_set kwarg
)
search.fit(X, y)
How it decides whether to use early stopping
KantunSearch inspects the target model class's fit() signature. If
it finds an eval_set parameter (as KANBoost's estimators do), it
automatically passes eval_set=(X_val, y_val) on each fold so early
stopping kicks in during the search itself. You can override this with
use_eval_set=True/False explicitly.
Supported scoring
- Classification:
"auc"(default),"f1","accuracy", or a callablescorer(y_true, y_pred, y_prob, labels) -> float(higher is better). - Regression:
"neg_mse"(default),"neg_mae", or a callablescorer(y_true, y_pred) -> float(higher is better).
Continuous parameter ranges
param_distributions values are usually lists, but for
search_type="random"/"halving" (not "grid", which must enumerate)
a value can instead be a callable sampler(rng) -> value, where rng
is a random.Random seeded from random_state:
param_space = {
"n_estimators": [30, 60, 100],
"kan_lr": lambda rng: 10 ** rng.uniform(-3, -1), # log-uniform
"learning_rate": lambda rng: rng.uniform(0.01, 0.3), # linear-uniform
}
Time budget
time_budget_s caps wall-clock search time. It's checked between combos
(in batches of n_jobs) or between halving rungs -- never mid-fit, so a
combo already dispatched always finishes, and at least one combo/rung
always runs. If the budget is hit before halving's final full-data rung,
the best candidate from the last completed rung is promoted so fit()
still succeeds.
search = KantunSearch(KANBoostClassifier, param_space, time_budget_s=600)
Skipping the final refit
By default fit() refits best_params_ on the full dataset
(best_estimator_). Pass refit=False to skip that -- useful when
model_cls is expensive to train and you only need best_params_/
cv_results_.
Search types
-
search_type="random"(default): samplesn_iterrandom combinations -
search_type="grid": tries every combination inparam_distributions -
search_type="halving": successive halving -- starts every candidate on a small, stratified subsample of each fold's training data (held-out validation data is always full and untouched), keeps the top1/halving_factorby score, and grows the training subsample byhalving_factoreach round until a round trains on the full data. Training-set size is the resource halved (not, say,n_estimators), since it's the only resource meaningful for any estimator -- kantun tunes arbitrary sklearn-compatible models, not just KANBoost. Useful when you have more candidates than you can afford to fully evaluate.search = KantunSearch( KANBoostClassifier, param_space, search_type="halving", n_iter=20, cv=3, halving_factor=3, min_resource=50, )
Speeding up an expensive search
Two independent knobs, useful together or separately, both aimed at the case kantun was built for: tuning an estimator that's slow to fit per combination (like KANBoost, ~10-20x a tree ensemble):
n_jobs: evaluate multiple param combos concurrently (threads, not processes -- safe for CUDA device selection, and PyTorch releases the GIL during tensor ops so real overlap still happens).search = KantunSearch(KANBoostClassifier, param_space, n_jobs=4)
prune=True: abandon a combo after its first CV fold if that fold's score already falls more thanprune_marginstandard deviations (of the current best combo's own fold spread) below the running best -- skips the remainingcv - 1folds for combos that are essentially never going to become the best. A pruned combo's single-fold score is recorded incv_results_("pruned": True) but never becomesbest_params_/best_score_. Off by default; the first combo evaluated is never pruned (there's nothing to compare against yet).search = KantunSearch(KANBoostClassifier, param_space, prune=True, prune_margin=1.0)
License
MIT — see LICENSE.
Metadata
Release files for kantun 0.0.4
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 | |
|---|---|---|---|---|
| kantun-0.0.4.tar.gz | 16.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kantun-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / kantun-0.0.4.tar.gz
| Download URL | kantun-0.0.4.tar.gz |
|---|---|
| Size | 16.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08a0418ec977f4216b9de503e3b3da10b3c4a552ac8d7311cc16dff759d00fe1
|
|
BLAKE2b-256 checksum How to use checksums |
14131d19213dc67b39e60daf5d3952d070618b85689fc3cbdd26de58faad7817
|
| 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 9, 2026.
Transparency logRelease files / kantun-0.0.4-py3-none-any.whl
| Download URL | kantun-0.0.4-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6207b40e301576f74c2724fc87399d01362560b1f090a27b6951367cbf27aaf7
|
|
BLAKE2b-256 checksum How to use checksums |
2aa8ed07d2c31047755612b09ce13fd6453c1fa306dc829aea44ffa8081764d8
|
| 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 9, 2026.
Transparency logSecurity for kantun 0.0.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kantun-0.0.4.tar.gz
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 9, 2026.
Transparency logA 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.