Why there are 2 requirements files? (requirements.txt, requirements_versions.txt)

[przemoc]

Installation procedures in wiki refer to requirements.txt, yet launch.py uses requirements_versions.txt.

When we sort packages listed in them for easier comparison between them, we can see they differ in various ways:

$ git rev-parse HEAD
5c0c778a65c8f89a85395fb10e32d3b35ea57196
$ dwdiff -c <(sed 's,[=><]=, &,' requirements.txt | sort) <(sed 's,[=><]=, &,' requirements_versions.txt | sort) | sed 's, ,,g'

Legend:
red color - stuff present only in requirements.txt
green color - stuff present only in requirements_versions.txt

To briefly sum up:

• majority of packages in requirements.txt do not have version specified
• some packages have different versions specified (fairscale, scikit-image, timm)
• invisible-watermark and TencentARC/GFPGAN are listed only in requirements.txt
• requirements.txt and requirements_versions.txt list packages in different order (which is not shown above)

What's the idea behind having those two files and why different versions are specified in them?

[przemoc]

--VOLDY RETARD GUIDE-- located at https://rentry.org/voldy provides following information:

webui.bat installs requirements from files requirements_versions.txt, which lists versions for modules specifically compatible with Python 3.10.6.
If you choose to install for a different version of python, editing webui.bat to have set REQS_FILE=requirements.txt instead of set REQS_FILE=requirements_versions.txt may help (but I still reccomend you to just use the recommended version of python).