Use verlib2.Version instead of crate.client._pep440.Version

[amotl]

About

Instead of vendoring Version from packaging, pull it in via shared library verlib2.

Problem

crash broke after releasing crate==0.35.0, so I've yanked it again.

ModuleNotFoundError: No module named 'crate.client._pep440'

-- https://github.com/crate/crash/actions/runs/7562783871/job/20593938496?pr=421#step:5:29

Blocked By

• Compatibility: Re-add crate.client._pep440.Version from verlib2 crate-python#605
• Tests: Update to pandas 2.1 crate-python#606

[amotl]

crash broke after releasing crate==0.35.0, so I've yanked it again.

Just released 0.35.1, including a corresponding fix to make both artefacts forward- and backward-compatible. ¹

• Compatibility: Re-add crate.client._pep440.Version from verlib2 crate-python#605

Footnotes

1. Currently, we do not employ corresponding version pinning to strictly tie crate and crash together, that's why it needs to be compatible into both directions. Let us know if you think this should be discussed. ↩

[amotl]

The CI run is dead slow on Python 3.12, because it is building pandas 2.0.3? It became part of crate[test], but why is it selecting such an old version, for which are surely no binary builds (wheels) available on PyPI?

  Building wheel for pandas (pyproject.toml): still running...
  Building wheel for pandas (pyproject.toml): still running...
  Building wheel for pandas (pyproject.toml): finished with status 'done'
  Created wheel for pandas: filename=pandas-2.0.3-cp312-cp312-linux_x86_64.whl size=46018100 

Edit: crate/crate-python#606 / release 0.35.2 improves the situation, the run on Python 3.12 is much faster now.