🆘 enviroment.yml back to requirements.txt

:sos:
I don’t know how to fix this… im having issues installing basicsr so i tried with enviroment.yml generated with conda env export > environment.yml (it had a lot of packages), when running on st cloud it return ❗️ installer returned a non-zero exit code so i deleted the .yml from my (repo)[GitHub - angelicaba23/app-super-resolution at dev] and go back to requirements.txt but rn it download many dependencies i don’t have in the .txt


It’s important to recognize that requirements.txt or any other requirements file type only specifies the packages that you assert are necessary to make your code run. Of course, other packages may also depend on other packages that you’re not aware of; these are still dependencies of your app, even if you aren’t aware of them. So this is why other packages will be downloaded, even if you specifically don’t specify them.

Best,
Randy

@randyzwitch I created a new repo, which is a new version of GitHub - angelicaba23/app-super-resolution at dev that runs perfect on local (without the packages.txt).

When deploying got this but i don’t know where the enviroment.yml comes from, i don have it in github. I re-run and got from .cv2 import * ImportError: libGL.so.1: cannot open shared object file: No such file or directory
so im following this I created a new repo [[Streamlit sharing] Importerror: libgl.so.1: cannot open shared object file: no such file or directory opencv error - #10 by snehankekre

libGL.so is a system-level dependency, not a Python one. This means on Streamlit Cloud, you would either need to use a packages.txt file or because specifically because you are using opencv, you can specify opencv-python-headless in your requirements file.

I would recommend the “headless” route, as that package removes all the GPU and display driver code you won’t need on Streamlit Cloud.

Best,
Randy