qds
qds (Quick Dirty Scripts) is a CLI tool that lets you create and run quick Python scripts from the command line with minimal setup.
Installation
Install via pip:
pip install qds-run
Overview
When you first run any qds command, it initializes a directory in your home folder:
-
~/.qds/qds.tomlA TOML file containing metadata about your scripts. -
~/.qds/<script>.pyPython files where each script’s code lives.
You can then add, edit, list, rename, run, and delete these scripts directly from your terminal.
Basic Usage
-
Initialize your workspace The first time you invoke any command,
~/.qds/qds.tomland the~/.qds/folder will be created automatically. -
Create a new script skeleton
qds add <script_name>
For example:
qds add base64conv
You’ll be prompted to enter a description; after confirming, a file named
~/.qds/base64conv.pyis created. -
Edit your script Open
~/.qds/base64conv.pyin your editor. By default, it will contain a template like this:from qds import qds @qds( args=[("text", str, "Sample text to be provided")], ) def run(text: str) -> str: pass
-
@qdsdecoratorargs: a list of(name, type, description)tuples defining the arguments your script accepts.
-
runfunction- The entry point; return a string to be printed.
-
-
Run your script
You will be prompted to fill in the arguments.
qds run base64conv
Example: Text to Base64 Converter
-
Add the script:
qds add base64conv
-
Edit
~/.qds/base64conv.pyso thatrunlooks like this:import base64 from qds import qds @qds( args=[("text", str, "Text to encode to Base64")], ) def run(text: str) -> str: encoded = base64.b64encode(text.encode("utf-8")).decode("utf-8") return encoded
-
Use it:
$ qds run base64
Available Commands
| Command | Description |
|---|---|
qds add |
Create a new script skeleton |
qds delete |
Delete an existing script |
qds list |
List all available scripts |
qds rename |
Rename a script |
qds run |
Run a script with the given arguments |
qds update |
Update the description of a script |
qds view |
Show the source code of a script |
qds --help |
Display help message |
qds --version |
Display application version |
Metadata
Release files for qds-run 0.1.1
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 |
|---|---|---|---|---|
| qds_run-0.1.1.tar.gz | 6.5 kB | Without provenance | Details for qds_run-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qds_run-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for qds_run-0.1.1-py3-none-any.whl |
Total release size: 15.2 kB
Release files / qds_run-0.1.1.tar.gz
| Download URL | qds_run-0.1.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
519e50d3725fa113ad994160f9be9182d9761375a8ab55546a8d44a287b3149b
|
|
BLAKE2b-256 checksum How to use checksums |
13bfd084b2716aa9615cb543a3a3896f5895ed4678f40d157b937f74a5eaac98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Windows/10
|
Release files / qds_run-0.1.1-py3-none-any.whl
| Download URL | qds_run-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e07ee4be81bb8e6d366720570d9f0172c1163aa1819539ccf3058731e872954
|
|
BLAKE2b-256 checksum How to use checksums |
a152640cbcc5a82d1a199ebc2e4bf145bfd9027a1fcdacdf4b3c4dc847d912ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Windows/10
|
Security for qds-run 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.