Update chDB results - #1417
Conversation
chdb-core cannot cut PyPI releases frequently, but every GitHub release (including release candidates) publishes the full wheel set as assets. After the regular pip install, compare the installed version with the newest chdb-core release tag (PEP 440 ordering over the full release list, so rc tags participate and an rc of an already-released version can never win): if the release is strictly newer, install its wheel for the current architecture instead. If the check fails, e.g. offline, the PyPI build stays. The effective version is printed either way.
|
Results for Logs:
|
…, c6a.4xlarge, c6a.xlarge, c7a.metal-48xl, c8g.4xlarge)
|
Results for Logs:
|
…ned (c6a.large, c6a.metal, c6a.xlarge, c8g.metal-48xl)
|
Results for Logs:
|
…ned (c6a.large, c6a.metal, c7a.metal-48xl, c8g.metal-48xl, t3a.small)
|
Results for Logs:
|
|
Results for Logs:
|
…machine, keep the existing numbers
…f the existing numbers
|
Results for Logs:
|
Update chDB results for the chdb, chdb-parquet-partitioned and chdb-dataframe entries.
Also change their install scripts: keep
pip install chdbas the base; if the newest chdb-core GitHub release tag differs from the installed chdb-core version, install its wheel instead (chdb-core publishes wheels for every release, including release candidates that don't reach PyPI).