requirements.txt: Set versions as minimum instead of hardcoding as exact

[C0rn3j]

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
librespot 0.0.9 requires requests==2.30.0, but you have requests 2.32.3 which is incompatible.

If there turns out to be an issue later, it can be hardcoded as minimum + maximum.

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
librespot 0.0.9 requires requests==2.30.0, but you have requests 2.32.3 which is incompatible.

The way it is set at the moment breaks installing the project if newer versions need to be installed.

[kokarare1212]

Looks good.
However, only protobuf needs to match the version due to compatibility issues.

[kokarare1212]

Also, in general, ~= is better for major updates of libraries, as compatibility may be lost.

[C0rn3j]

protobuf needs to match the version due to compatibility issues.

Fixed - tracked in #130 apparently.

in general, ~= is better for major updates of libraries, as compatibility may be lost

Personally I prefer to allow the very latest, to catch issues sooner rather than later.
Python supports maximum versions too together with minimums, so that can be used to fixate a version if that manages to happen.
If you insist on ~= I will of course put that there, but am afraid it'll just cause this situation again later.

If a release could be tagged after merge to fix the issue in stable versions, that'd be neat!