Skip to content

CHANGELOG: log the MLPE change, which is breaking - #15

Merged
luizfernandolj merged 1 commit into
masterfrom
changelog-mlpe
Nov 11, 2026
Merged

luizfernandolj merged 1 commit into
masterfrom
changelog-mlpe

Conversation

@luizfernandolj

Copy link
Copy Markdown
Collaborator

#14 removes the estimator from MLPE. MLPE(LogisticRegression()) now raises TypeError, cv/stratified/shuffle are gone from the signature, and there is no estimator_ after fit.

Anyone upgrading without reading the diff finds that at runtime. The Unreleased section had no ### Breaking Changes heading at all, although the v0.5.0 entry already uses that section for exactly this kind of change — the evaluation-metrics argument reorder.

The entry

It leads with what breaks and how to migrate (drop the argument — MLPE()), and says plainly that the estimate does not change: it was always the training prevalence read from the labels. The breakage is in the signature, not in the numbers.

Then why, with the measurement that justified it:

with #6 non-aggregative
training time 0.0571 s 0.0006 s
ratio vs quapy 347x 4.99x
training memory 6.90x 2.04x
estimation memory 1.90x 1.00x
train + estimation 8.51x 1.38x

And the comparison that identified the cost: CC, which trains one classifier and nothing else, cost 0.0523 s against MLPE's 0.0571 s over 142 datasets. What remained was one LogisticRegression.fit, for work the estimate never used. fit now takes 0.55 ms instead of ~57 ms, and the whole method over 142 datasets takes 50 s of CPU against 40 min.

Every figure was checked against q2_custo.csv of the two runs before being written.

Not logged

#13 changed this file's own section label and compare links. That is not a user-visible change to the library, and a changelog logging edits to itself would be noise.

Markdown only.

🤖 Generated with Claude Code

#14 removes the estimator from MLPE: MLPE(LogisticRegression()) now raises
TypeError, cv, stratified and shuffle are gone from the signature, and there
is no estimator_ after fit. Anyone upgrading without reading the diff finds
that at runtime, so it belongs in the file -- under Breaking Changes, which
is the section the v0.5.0 entry already uses for exactly this kind of
change, and which Unreleased did not have.

The entry says plainly that the estimate does not change and that migration
is to drop the argument, because the breakage is in the signature and not in
the numbers.

#13 is not logged: it changed this file's own labels and links, which is not
a user-visible change to the library.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@luizfernandolj
luizfernandolj merged commit 4ce918f into master Nov 11, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant