Timeline for Should I automatically install needed modules?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 2, 2015 at 0:56 | history | edited | Jace Browning | CC BY-SA 3.0 |
Add a way to call `pip` from within a script
|
| Jul 1, 2015 at 22:50 | comment | added | spelchekr | @JaceBrowning I email him new versions as I code them. For instance, I send him an email with script_rev16.py attached. That's about all he can handle. | |
| Jul 1, 2015 at 20:02 | history | edited | Jace Browning | CC BY-SA 3.0 |
[Edit removed during grace period]
|
| Jul 1, 2015 at 19:56 | comment | added | Idan Arye |
pip can read the package list from a file - pip install -r requirements.txt. The OP can distribute requirements.txt as part of their program, and when they add a new module requirement they add it to requirements.txt. The installation command can be wrapped in a shell script that the grandpa just need to double-click.
|
|
| Jul 1, 2015 at 19:50 | comment | added | Jace Browning | Fair enough. I'll ask OP to clarify how this code is currently being distributed. | |
| Jul 1, 2015 at 19:41 | comment | added | user53141 |
It may be assuming too much to assume that a to a non-technical user, pip is something you run "simply".
|
|
| Jul 1, 2015 at 18:56 | comment | added | Jace Browning | See an example package here: github.com/jacebrowning/template-python-demo | |
| Jul 1, 2015 at 18:56 | history | answered | Jace Browning | CC BY-SA 3.0 |