chore(deps)!: py-serializable==^1.1.1 -> ^2.0.0

[jkowalleck]

bump to py-serializable v2.0.0: https://github.com/madpah/serializable/releases/tag/v2.0.0
This is considered a breaking change, as downstream users might rely on the same package's previous version.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ 100.00% (target: 80.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (2a87f50)	5092	4760	93.48%
Head commit (b03cfa6)	5092 (+0)	4760 (+0)	93.48% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#775)	20	20	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[hseg]

Looking over the PR, I'm struck by the fact that it hard-bumps the dependency on
py-serializable to ^>=2.0.0. However, this is unnecessarily strict:

from importlib.metadata import version
from packaging.Version import Version

match Version(version('py-serializable')):
    case ver if ver < Version('2.0.0'):
        import serializable
    case ver if Version('2.0.0') <= ver < Version('3.0.0'):
        import py_serializable as serializable
    case _:
        throw ImportError("Can't predict py-serializable compatibility")

The benefit here is that it loosens the need to bump the cyclonedx and
py-serializable versions in lockstep. Thankfully, AFAICT cyclonedx is the
only reverse dependency of py-serializable currently packaged in AUR aur,
so this case isn't so bad, but good practice is good practice.

[jkowalleck]

re: #775 (comment)

i also thought about having a compatibility layer for supporting ^1.1.1||^2.
I decided against this, as python venvs exist for people that need the old version of py-serializable, still.
So there should be simply no reason to support backwards compatibility here.

[hseg]

Fair enough - I did notice in reading some discussion threads that that appears to be the currently accepted solution direction for this class of problems, so this may just be a matter of clashing cultural expectations - my main experience with package management innards comes from the Haskell world, which supports multiple package versions being installed and so encourages packages to declare wider compatibility windows so as not to overconstrain the solver. 9 feb 2025 18:43:11 Jan Kowalleck ***@***.***>:

…

re: #775 (comment)[#775 (comment)] i also thought about having a compatibility layer for supporting *^1.1.1||^2*. I decided against this, as python venvs exist for people that need the old version of py-serializable`, still. So there should be simply no reason to support backwards compatibility here. — Reply to this email directly, view it on GitHub[#775 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAJTW5JQEOPWH5355VWEZRD2O6AR5AVCNFSM6AAAAABWY3NDNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBWGM4TMMBTHE]. You are receiving this because you commented. [Imagen de rastreo][https://github.com/notifications/beacon/AAJTW5MGPXW6PFJ2Y2HL7GD2O6AR5A5CNFSM6AAAAABWY3NDNWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTU5XTGIO.gif]

[jkowalleck]

A preview of the fix/feature is available via https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v9.0.1-rc.1

[jkowalleck]

was released via https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v9.0.0