Closed
Description
This is necessary in libtmux and tmuxp.
tmuxp uses this for tmux
versions (via git and 3.0b, etc)
Needs to be flexible and ideally have no dependency
-
LegacyVersion deprecation
In
packaging
,LegacyVersion
(the supercessor toLooseVersion
) will be deprecated, we won't be able to support2.4-openbsd
(like what is seen on OpenBSD's tmux versions/home/t/work/python/libtmux/.venv/lib/python3.10/site-packages/packaging/version.py:127: DeprecationWarning: Creating a LegacyVersion has been deprecated and will be removed in the next major release warnings.warn( -- Docs: https://docs.pytest.org/en/stable/warnings.html
-
tmux versions
To the above, consider subclassing `Version` for tmux versions to handle git builds, platform builds, etc. then keeping `Version` for supporting pypi releases
-
Version
Assure thatlibtmux.__version__
/tmuxp.__version__
supports git refs /local
match groups