Update configurations to latest pyproject.toml

[baggiponte]

Hey there. I opened a similar issue before Christmas on NVIDIA's NeMoGuardrail project. The latest Python standards recommend to configure the project with pyproject.toml over setup.py for several reasons - including, for example, the possibility to list build-time dependencies.

The so-called build backends (specified in PEPs 517 518) can read from pyproject.toml stuff such as the README, the dependencies and the version dynamically, so you won't have to maintain those.

Plus, I had a question: is there a reason for you to pin the dependencies with == constraints? are there any know incompatibilities with all these libraries? Generally Python libraries are not meant to be distributed with == in other cases but with >= to ensure compatibility. With == constraints, llm-guard installation might fail when attempting to install in an environment with conflicting deps.

I could implement a similar thing as I did here.

[asofter]

Hey @baggiponte , thanks for the suggestions. I am kicking off preparation for the next release, and this is first on my list.

[asofter]

On the library version constraints, there are a few dependencies where it makes difference like torch but mostly it doesn't, so I made a change for that as well.

[asofter]

Updated, thank you for the suggestion: https://github.com/laiyer-ai/llm-guard/blob/main/pyproject.toml

[baggiponte]

Thanks! Closing the issue :)