PRO only does two things, but it does them well: it runs processes,
and restarts select processes when their dependent files change.
PRO is designed to be useful for running processes in development, but
there are probably better options for running your processes in production.
Installation
------------
pip install pro
Usage
-----
pro runfile.py
Your runfile contains the description of which processes to run, and
an optional list of files to observe for each process group. A process
can be defined as a command to run as a string, or as a CMD object,
which can specify a directory in which to run.
Example runfile.py:
import os
from pro import CMD, run
run(CMD('python manage.py runserver 8080', cd='example_project'))
run('python -m SimpleHTTPServer 8888', watch_list=['watchme'])
sass_file = 'static/css/style.sass'
run('sass %s' % sass_file, watch_list=[sass_file])
template_dir="static/templates"
handlebars_inputs=os.path.join(template_dir, '*.handlebars')
handlebars_output=os.path.join(template_dir, 'templates.js')
cmd = 'handlebars `ls %s` -f "%s"' % (handlebars_inputs, handlebars_output)
run(cmd, watch_list=[handlebars_inputs])
Metadata
Release files for pro 0.1.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 |
|---|---|---|---|---|
| pro-0.1.2.tar.gz | 3.4 kB | Without provenance | Details for pro-0.1.2.tar.gz |
Release files / pro-0.1.2.tar.gz
| Download URL | pro-0.1.2.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad97558f242b44ffb8316b2bad76aa46c3bd787e7f42989890f0e4f5fd2e2304
|
|
BLAKE2b-256 checksum How to use checksums |
937a3a23e09c6032ad44e65f6bd8d14bf4496aff93d75bc277edfee14e59a7e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pro 0.1.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.
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.