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
When running various Python scripts, I often need to do this annoying dance: $ python script.py ... ModuleNotFoundError: No module named 'foo' $ pip install foo $ python script.py ... Module...
#4: Post edited
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
- $ pip install baz
- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
- Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell Python to react by attempting a `pip install` on that, rather than raising an exception?
- ------
- I am aware that:
* `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages.- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
- $ pip install baz
- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
- Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell Python to react by attempting a `pip install` on that, rather than raising an exception?
- ------
- I am aware that:
- * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always PyPi packages.
- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
#3: Post edited
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
- $ pip install baz
- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell it to react by attempting a `pip install` on that, rather than raising an exception?- ------
- I am aware that:
- * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages.
- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
- $ pip install baz
- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
- Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell Python to react by attempting a `pip install` on that, rather than raising an exception?
- ------
- I am aware that:
- * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages.
- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
#2: Post edited
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
$ pip install bar- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
- Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell it to react by attempting a `pip install` on that, rather than raising an exception?
- ------
- I am aware that:
- * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages.
- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
- When running various Python scripts, I often need to do this annoying dance:
- ```shell
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'foo'
- $ pip install foo
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'bar'
- $ pip install bar
- $ python script.py
- ...
- ModuleNotFoundError: No module named 'baz'
- $ pip install baz
- $ python script.py
- (correct output from script)
- ```
- Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff.
- Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell it to react by attempting a `pip install` on that, rather than raising an exception?
- ------
- I am aware that:
- * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages.
- * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case.
- * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.
#1: Initial revision
Automatically install all packages needed
When running various Python scripts, I often need to do this annoying dance: ```shell $ python script.py ... ModuleNotFoundError: No module named 'foo' $ pip install foo $ python script.py ... ModuleNotFoundError: No module named 'bar' $ pip install bar $ python script.py ... ModuleNotFoundError: No module named 'baz' $ pip install bar $ python script.py (correct output from script) ``` Yes, I know this can be solved by creating a `requirements.txt` file, packaging the script, etc. But I'm asking about cases where that ship has sailed. All I have is a script that optimistically imports stuff. Python already knows what package it's *supposed* to be, since it's named in the `ModuleNotFoundError`. Is there a way to tell it to react by attempting a `pip install` on that, rather than raising an exception? ------ I am aware that: * `ModuleNotFoundError` may raise not just for missing packages, but also modules (eg. `foo.py`) in the same directory. I'm happy with a solution that blindly assumes it's always a PyPi packages. * [Some](https://pypi.org/project/xdg-base-dirs/) packages use a different name for `pip install` and `import`. I'm happy with a solution that fails or installs the wrong package in this case. * It is dangerous to blindly install packages from PyPi. I'm okay with the risks.