deps_installer
Lightweight helper to bundle and run small installer scripts included with a
Python application (Windows only). The package looks for an installers
folder (default: data/installers) in the packaged resources and executes
each file found there.
Quick highlights:
- Programmatic:
install_deps(installer_folder='data/installers') - Platform: Windows only
Quick Start
Programmatic call:
from deps_installer import install_deps
install_deps() # uses 'data/installers' by default
Example CLI (sample included):
python src/example_use.py --install_deps
Usage
- Function:
install_deps(installer_folder='data/installers'). - On non-Windows platforms the function prints a message and returns without running installers.
Notes:
- The function executes every file found in the provided folder using
subprocess.Popen. Ensure files are executable and trusted. - If you bundle with PyInstaller, include the
datafolder so installer files are available at runtime (see Packaging below).
Packaging (PyInstaller)
Embed the data folder so installer files are available at runtime. Example:
pyinstaller -F --clean --distpath dist ; \
--add-binary data:data ; \
--runtime-tmpdir tmp ; \
--name installer_try src/example_use.py
This places your data contents inside the executable runtime so
install_deps() can find data/installers.
Troubleshooting & Notes
- Missing folder:
os.listdirwill raise if the folder does not exist. Createdata/installers(or pass a different folder) before packaging. - Interactive installers: test installers manually—automated installs should avoid blocking prompts.
- Admin rights: if installers require elevation, re-launch your app as admin
(see
pyuacusage insrc/example_use.py).
Security
This project executes files shipped with the package. Only include files from trusted sources. For production use consider:
- restricting executable extensions (e.g.
.exe,.msi,.bat) - validating file hashes or signatures before execution
Metadata
Release files for deps-installer 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| deps_installer-1.0.2.tar.gz | 3.8 kB | With provenance | Details for deps_installer-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| deps_installer-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for deps_installer-1.0.2-py3-none-any.whl |
Total release size: 7.3 kB
Release files / deps_installer-1.0.2.tar.gz
| Download URL | deps_installer-1.0.2.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13e15529bf8a35fcefc5f9ae77eba40ce6895054d3f03653d87cb8352f09af91
|
|
BLAKE2b-256 checksum How to use checksums |
069872dcb1c6e4ad834fd552390fb15402b76e10ab3b5244c6cffb705727abdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2025.
Transparency logRelease files / deps_installer-1.0.2-py3-none-any.whl
| Download URL | deps_installer-1.0.2-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7531e1e024f59a15d9cbe3f16df8e59ba997cb86684c9ffdf4d0191bc9d79c9
|
|
BLAKE2b-256 checksum How to use checksums |
9277411ba404ad59a7c8672941c25113006bd43a15a9aac6188a84feb532a0ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2025.
Transparency logSecurity for deps-installer 1.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for deps_installer-1.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 22, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.