Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
The best approach is probably to just check the script beforehand, something like the following grep import script.py should list all imports and you can then evaluate and install them. If you...
#1: Initial revision
by
cafce25
·
2023-06-18T06:13:27Z (over 3 years ago)
The best approach is probably to just check the script beforehand, something like the following
```bash
grep import script.py
```
should list all imports and you can then evaluate and install them.
If you really want to automate things you can write a short shell script to loop & install modules for example this one in bash:
```bash
#!/usr/bin/env bash
while :;
do
{ STDERR="$( { ${@}; } 2>&1 1>&3 3>&- )"; } 3>&1;
if [[ $? -eq 0 ]]; then
break
else
module=$(printf '%s' "$STDERR" | grep ModuleNotFoundError | cut -d\' -f 2)
pip install $module
fi
done
```
when saved as `install.sh` in the current directory can be used as `bash install.sh python script.py`
If you create a virtual environment with something like `python -m venv env; source env/bin/activate` (which you should do to not pollute your global packages anyways) before you can generate a `requirements.txt` with `pip freeze > requirements.txt` afterwards and save yourself the hassle in future.