Right now, the dependencies in the project are described in a file requirements.txt and too strict. There are a lot of strict locks to a minor version of some library, which makes it very difficult to use ReLiK for larger and adult systems (as a result of the huge number of dependency conflicts).
I suggest reviewing dependencies, or switching to more modern and smart dependency resolvers like poetry, hatch, uv or other. Thus, it will be easier for developers to integrate relic into their systems, which will lead to popularization and further development.
I have made such changes in my local fork here. Please, let me know what do you think of the proposed changes. I'm ready to help in case of any issues
Right now, the dependencies in the project are described in a file requirements.txt and too strict. There are a lot of strict locks to a minor version of some library, which makes it very difficult to use ReLiK for larger and adult systems (as a result of the huge number of dependency conflicts).
I suggest reviewing dependencies, or switching to more modern and smart dependency resolvers like poetry, hatch, uv or other. Thus, it will be easier for developers to integrate relic into their systems, which will lead to popularization and further development.
I have made such changes in my local fork here. Please, let me know what do you think of the proposed changes. I'm ready to help in case of any issues