Page MenuHomeElementl

Handle LegacyVersion
ClosedPublic

Authored by jordansanders on Jun 28 2021, 8:25 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 13, 10:27 PM
Unknown Object (File)
Fri, Mar 10, 11:09 PM
Unknown Object (File)
Feb 21 2023, 6:59 PM
Unknown Object (File)
Feb 12 2023, 10:08 PM
Unknown Object (File)
Feb 10 2023, 12:55 PM
Unknown Object (File)
Feb 10 2023, 1:07 AM
Unknown Object (File)
Feb 9 2023, 5:12 PM
Unknown Object (File)
Feb 6 2023, 10:19 PM
Subscribers
None

Details

Summary

packaging.version.parse can return either a Version or a LegacyVersion.
LegacyVersion doesn't have a major attribute:

python_modules/libraries/dagstermill/dagstermill/compat.py:5: error: Item "LegacyVersion" of "Union[LegacyVersion, Version]" has no attribute "major" [union-attr]

While it's probably safe to assume that Papermill will never publish a
non-parsable version, I'm switching this to safely handle occurances
when parse returns a LegacyVersion instead of ignoring the mypy warning.

Test Plan

unit

Diff Detail

Repository
R1 dagster
Branch
jordan-fixup-papermill-version-check (branched from master)
Lint
Lint Passed
Unit
No Test Coverage