Repository navigation
Packvium 1.5.0
Refusals you can name by type, and the replay promise of a result without building an
artifact. A misspelt configuration key is now refused (see Fixed).
Added
UnsupportedFeatureError,UnknownSolverError,UnknownObjectiveErrorand
PolicyErroronpackvium.pack_from_dictalready raised them; they are now importable
from the package root, so a refusal can be caught by type instead of by message.packvium.artifacts.replay_level(result)—"exact"or"not_guaranteed", the promise an
operational artifact of this result would make, without building the artifact.
Changed
- Faster beam and maximal-space search, same results. The beam skips work on expansions
that cannot beat the best plan so far, and the maximal-space solver stops checking for
containing spaces once none can exist. Measured: beam requests 3–6% faster,maximal_spaces
up to 20% faster on large orders. Every result is byte-identical.
Fixed
- A block answer reports the support each item really has.
HomogeneousBlockSolverwrote
support_ratio1.0 for every item, including those of a block set on a smaller one, which
overhang it. The bottom layer of each block now reports the share of its base that rests on
something. Withminimum_support_ratioabove zero the block solver is no longer tried at
all; its answer was built and then discarded by validation. - A misspelt
configurationkey is refused. A key the request schema does not declare in
configurationor itseffort_budget(profileforsolver_profile,top_kfor
alternatives) was silently ignored, so the request ran on defaults.pack_from_dictnow
raisesInvalidRequestErrorwith reasonnot_allowedand the key's pointer, for example
/configuration/profile. - An unknown
objectiveor access direction is a named request error.pack_from_dict
raisedUnknownObjectiveError/InvalidDirectionErrorwith no reason or field; it now raises
InvalidRequestErrorwith reasonnot_allowedand the value's pointer, like every other
refusal. The typedPackerAPI still raisesUnknownObjectiveError. Lengthrefuses a fractional float, asWeightalready did.Length.mm(0.1)silently
became 1600 ticks andLength.mm(1e-9)became 0; both now raiseTypeError. An integral float
such as100.0is exact and still accepted.- Compressible items are no longer laid out as rigid blocks.
HomogeneousBlockSolvernow
hands them to the general solver, asGridSolverdoes. - Refusal messages match
docs/ERRORS.md, e.g. a fixed placement with unknown keys says it
cannot carrythem.