Version pinning in dependencies

[sitmo]

The pyproject.toml file has specific version pinning of dependencies that cause conflicts with other libs that have different constraints. The likelihood of dependency conflicts is substantially increased if dependency versions are all pinned instead of leaving the ranges flexible. Can you relax the version contrains to improve interoperability?

E.g. I cant install vast.ai alongside matplotlib because it conflict with this specific version constraint

"python-dateutil==2.6.1"

Matplotlib requires python-dateutil (>=2.7)

Other specific version depedencies in the pyproject.toml:
"borb (==2.1.25)"
"argcomplete==3.5.1"
"urllib3==2.2.3"

[stackanthony]

Can you make a PR for updating the pyproject.toml based on your use-case? @sitmo

[sitmo]

Very good @stackanthony, here is the pull-request #211