Skip to main content

Run commands quickly from the pyproject.toml (or pyqwe.toml) file.

Project description

🏎️💨 pyqwe

The Quick Work Environment for Python.

PyPI version License

Run commands quickly from the pyproject.toml (or pyqwe.toml) file.

pip install pyqwe

Usage

Add commands to the pyproject.toml or pyqwe.toml file.

🚨NOTE - If you have both a pyproject.toml and a pyqwe.toml file, the pyqwe.toml file will be used and the pyproject.toml file will be ignored.

[tool.pyqwe]
flask = "flask_app:run"
say_hello = "*:echo Hello World"

If you're using a pyqwe.toml file you can drop the [tool.pyqwe]

flask = "flask_app:run"
say_hello = "*:echo Hello World"

To see information on the available commands in the toml file you can run:

pyqwe list
# or
pyqwe ls
# or
qwe list
# or
qwe ls

You can run the commands by using the command name:

pyqwe flask
# or
qwe flask

Running pyqwe or qwe without any option or command will show all available commands in a menu you can choose from.

pyqwe
# or
qwe
🚥|🏎️
0 : Exit
1 : flask
2 : say_hello
Select a command to run [0]:

Choosing 1 will run the flask command.

Python commands

For Python, the commands are structured like (package &/ module):function

Package example

project/
    flask_app/
        __init__.py
[tool.pyqwe]
flask = "flask_app:run"

This command will run the function run() from the __init__.py file in the flask_app package.

Module example

project/
    app.py
[tool.pyqwe]
flask = "app:run"

This command will run the function run() from the app.py file.

Now run the pyqwe command:

pyqwe flask

This will start the Flask app.

*:... commands (terminal)

Any command that starts with * will be run using subprocess.

For example:

[tool.pyqwe]
say_hello = "*:echo Hello World"

Now running the pyqwe command:

pyqwe say_hello

Will print Hello World.

Run as shell

To run the command as a subprocess shell command, add the shell key to the command.

[tool.pyqwe]
say_hello = "*shell:echo Hello World"

Change the working directory

You can change the working directory of a subprocess by adding the folder within parentheses to the command, (node_app) for example.

The folder must be relative to the pyproject.toml file.

Absolute paths are not supported.

Moving up directories is not supported, ../node_app for example.

[tool.pyqwe]
npm_install = "*(node_app):npm install"

The shell key is still available when changing the directory.

[tool.pyqwe]
npm_install = "*shell(node_app):npm i"

Grouped commands

You can group commands together in a list to have one pyqwe command run multiple commands.

Grouped commands can also be run in Step, Sync, or Async mode. Async being the default.

This will run the commands in the group in sequence, pausing for confirmation between each command:

[tool.pyqwe]
group = [
    "@step",
    "*:echo 'Hello, World! 1'",
    "*:echo 'Hello, World! 2'",
    "*:echo 'Hello, World! 3'"
]

This will run the commands in the group in sequence, one after the other:

[tool.pyqwe]
group = [
    "@sync",
    "*:echo 'Hello, World! 1'",
    "*:echo 'Hello, World! 2'",
    "*:echo 'Hello, World! 3'"
]

This will run the commands in the group in parallel:

[tool.pyqwe]
group = [
    "@async",
    "*:echo 'Hello, World! 1'",
    "*:echo 'Hello, World! 2'",
    "*:echo 'Hello, World! 3'"
]

Of course, you can leave out the @step, @sync or @async to use the default async mode.

For example, this will also run the commands in the group in parallel:

[tool.pyqwe]
group = [
    "*:echo 'Hello, World! 1'",
    "*:echo 'Hello, World! 2'",
    "*:echo 'Hello, World! 3'"
]

Waiting before starting a runner

Sometimes you might need to have a runner wait before starting. This might be the case if you have a group of runners in async mode but one runner connects to another.

You can tell a runner to sleep for a number of seconds by using the sleep for marker:

[tool.pyqwe]
group = [
    "@async",
    "*:~10~ echo 'Hello, World! 1'",
    "*:echo 'Hello, World! 2'",
    "*:echo 'Hello, World! 3'"
]

This also works on module runs:

[tool.pyqwe]
flask = "~10~ flask_app:run"

Each of the examples above will sleep for 10 seconds before the runner will start.

Using environment variables

To use environment variables in the command, use the {{ }} markers.

pyqwe will evaluate any environment variables that are set before running any commands.

If pyqwe detects an environment variable that is not set, it will raise an error. An error will also be raised if environment variables are detected, and you do not have python-dotenv installed.

Here's an example of setting an environment variable in a command:

[tool.pyqwe]
talk = "*shell:echo {{MESSAGE}}"

pyqwe uses load_dotenv() from python-dotenv to load the .env file. You can change the name of the file to load, or add multiple env files by setting the __env_files__ settings key.

[tool.pyqwe]
__env_files__ = [".env", ".env.local"]
talk = "*shell:echo {{MESSAGE}}"

This is the same as running load_dotenv(".env") and load_dotenv(".env.local").

If you want to disable pyqwe from doing anything with environment variables, you can set the __env_ignore__ settings key to true.

[tool.pyqwe]
__env_ignore__ = true
talk = "*shell:echo {{MESSAGE}}"

This will disable the environment variable evaluation and loading of the .env file, and result in {{MESSAGE}} being printed to the console in this case.

Clearing the terminal setting

Setting the __clear_terminal__ setting option to true will clear the terminal immediately after the pyqwe command is run. Results may very on this setting between terminals and OS platforms.

This option is set to false by default.

[tool.pyqwe]
__clear_terminal__ = true
talk = "*shell:echo {{MESSAGE}}"

Other commands

pyqwe -h or --help will display help information.

pyqwe --version or -v will display the version of pyqwe.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pyqwe-3.1.2.tar.gz (51.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

pyqwe-3.1.2-py3-none-any.whl (11.8 kB view details)

Uploaded Python 3

File details

Details for the file pyqwe-3.1.2.tar.gz.

File metadata

  • Download URL: pyqwe-3.1.2.tar.gz
  • Upload date:
  • Size: 51.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for pyqwe-3.1.2.tar.gz
Algorithm Hash digest
SHA256 40e720d28b5e25ef8211915f753b4d4503bb01392f61490848091ec1fd87a1d9
MD5 a42a8fa0ffb952dce4f72e440035145f
BLAKE2b-256 82f1624cbe1df2ec5093674cff9f494d1c5621afc26b0e474bd24c99f076289b

See more details on using hashes here.

Provenance

The following attestation bundles were made for pyqwe-3.1.2.tar.gz:

Publisher: publish.yml on CheeseCake87/pyqwe

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file pyqwe-3.1.2-py3-none-any.whl.

File metadata

  • Download URL: pyqwe-3.1.2-py3-none-any.whl
  • Upload date:
  • Size: 11.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for pyqwe-3.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 d56196d6eaf2e9d59009eb61d632d8270ddf673d9c093e3d60b00e6aa4104670
MD5 8e94b1756b9c81a10c4f13ac2b697356
BLAKE2b-256 359c718e82343f18cba8d0f2d4ad3d02a824898710740d76b0b7206d1d9b1702

See more details on using hashes here.

Provenance

The following attestation bundles were made for pyqwe-3.1.2-py3-none-any.whl:

Publisher: publish.yml on CheeseCake87/pyqwe

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page