because python’s dependency management is an unruly beast
Note that Automatic1111 is, by default, set up to run in a venv – a sort of little isolated Python install – so it won’t smack into the system packages, at any rate.
I think that the current version of Automatic1111 – I’m running off the dev branch – also pulled down the appropriate ROCm pytorch that AMD wants into its little venv, but I’m pretty sure that I recall needing to manually install that some months back, on an older version of Automatic1111. Other than that, I don’t think that I had to do anything significant with Python packages; there’s just a script that one runs to launch the package, and it also automatically downloads anything it needs the first time.
Note that Automatic1111 is, by default, set up to run in a venv – a sort of little isolated Python install – so it won’t smack into the system packages, at any rate.
I think that the current version of Automatic1111 – I’m running off the dev branch – also pulled down the appropriate ROCm pytorch that AMD wants into its little venv, but I’m pretty sure that I recall needing to manually install that some months back, on an older version of Automatic1111. Other than that, I don’t think that I had to do anything significant with Python packages; there’s just a script that one runs to launch the package, and it also automatically downloads anything it needs the first time.