Errors

Every error fmsave raises on purpose is a FmsaveError; every warning it issues on purpose is a FmsaveWarning. GateCheckError is the one exception that is also more specific than its base: it is the ReaderCheckError a save opened with strict=True raises for a failed check.

fmsave sets no fixed size limit on a save. A part that claims or decompresses to far more than its compressed bytes could plausibly hold raises CorruptSaveError before that memory is spent; the message gives the ratio, what real saves show, and asks for a report if the game opens the save.

exception fmsave.FmsaveError

Bases: Exception

Base class for every error fmsave raises on purpose.

exception fmsave.NotAFmSaveError

Bases: FmsaveError

The file is not a Football Manager save.

exception fmsave.CorruptSaveError

Bases: FmsaveError

The save is damaged, truncated, or was being written while it was read.

exception fmsave.UnsupportedGameError

Bases: FmsaveError

The save comes from a Football Manager version fmsave cannot read.

exception fmsave.ReaderCheckError

Bases: FmsaveError

A reader’s checks failed, so its output would not be trustworthy.

exception fmsave.GateCheckError(message, checks=())

Bases: ReaderCheckError

A ReaderCheckError from failed reader checks, carrying every check of the failed pass.

This is what fmsave.open(…, strict=True) raises when an applied check misses its bounds. Catching ReaderCheckError catches it, and checks holds the gate names, the observed values and the bounds the message rounds, so nothing has to be parsed back out of the text. A ReaderCheckError raised for any other reason carries no checks.

Parameters:

• message (str)

• checks (tuple[ReaderCheck, ...])

Return type:

None

checks

Every reader of the failed pass, each with its own gates.

Type:

tuple[fmsave._checks.ReaderCheck, …]

exception fmsave.SaveChangedError

Bases: FmsaveError

The save file changed on disk after it was opened.

exception fmsave.SaveClosedError

Bases: FmsaveError

A reader was called on a closed save.

exception fmsave.AmbiguousNameError

Bases: FmsaveError

A name matched more than one record where exactly one was needed.

exception fmsave.FmsaveWarning

Bases: UserWarning

Base class for every warning fmsave issues on purpose.

exception fmsave.UnknownBuildWarning

Bases: FmsaveWarning

The save comes from an FM26 build fmsave has no full set of layout tables for, or from FM27, which fmsave reads only in part. For an FM27 build with no layouts registered, the message also says it borrows the registered FM27 layouts where section schemas match.

exception fmsave.ReaderCheckWarning

Bases: FmsaveWarning

A reader’s measured checks failed and it handed its table back anyway.

This is what a failed check does on a save opened without strict=True. The message is the one ReaderCheckError carries on a strict save. A structural failure, where the decode has no table to hand back at all, raises ReaderCheckError whatever the setting.