Update to qestdb 2.0.3 API

[antst]

This implements qestdb-2.0 API and lift qestdb dependancy to questdb==2.0.3, as only 2.0.3 version of questdb python module client can be build by pip from sources (if Rust compiler "cargo" is installed).
Earlier versions have bugs here and there and PIP can not build them.
Also, it is much easier to convince questdb people to provide binaries (to avoid building altogether) for recent client, than for old one.

[antst]

@CM000n please, look at it. As everyone, who upgraded to 2024.12, has problem currently.

[mgumz]

@antst

Logger: homeassistant.setup
Source: setup.py:269
First occurred: 07:04:57 (1 occurrences)
Last logged: 07:04:57

Setup failed for custom integration 'qss': Requirements for qss not found: ['questdb==2.0.3'].

I git-cloned your branch to custom_components (or rather only the qss subfolder). HA:2024.12.2

[antst]

@antst

Logger: homeassistant.setup
Source: setup.py:269
First occurred: 07:04:57 (1 occurrences)
Last logged: 07:04:57

Setup failed for custom integration 'qss': Requirements for qss not found: ['questdb==2.0.3'].

I git-cloned your branch to custom_components (or rather only the qss subfolder). HA:2024.12.2

As there is no prebuilt wheel for questdb yet, and there are couple of obstacles which prevent installation of questdb from sources automatically, you need to look for instructions here:
#52 (comment)

[CM000n]

shouldn't we at least support all patch and minor version jumps instead of pinning a specific version?

[mgumz]

@CM000n no, why? when you pin the dep … you do a release on which you know that it works. someone at questdb releases a breaking version, which results in issues opened here.

[CM000n]

If they take semantic versioning seriously, minor patch releases should never break the API. With a pin, I see a greater risk that users will then remain on a lower version than currently available and not notice and use security-relevant patches.
Unfortunately, I don't have the time or inclination to publish a Qss release for every questdb patch release.

[CM000n]

I don't know if I like this approach, I'll have to think about it again.
But I think this change should be done independently with the changes necessary for the questdb client update.

[CM000n]

hello @antst. Thank you very much for this PR 😊 Can you please also adjust the pyproject.toml file and update the lock file

[CM000n]

Also pre-commit hooks are failing at the moment 😉

[mgumz]

@antst works.

[antst]

hello @antst. Thank you very much for this PR 😊 Can you please also adjust the pyproject.toml file and update the lock file

I updated deps and version in project file and mainifest and incorporated changes which should make liniter happy. But I have zero clue about lock file. Keep in mind, I am not python dev :)

[saintman23]

Lookingforward for a fix to use QuestDB with latrest HA...