Monitor and auto execute single script after modify
support go, python, c++, c. filename endswith .py .c .cpp .go extend other. Support django reload server when template change.
[zh_cn] 自动执行修改后的脚本
install
pip install seeing
use
seeing -f hello.py
seeing -s 3 -f hello.go # execute script after hello.go modified 3 seconds.
seeing -f hello.cpp # it will run g++ hello.cpp && ./a.out
seeing -f hello.c # same as cpp
# reload django devlop server
pip install gunicorn
seeing -c gunicorn project_name.wsgi
extend other
seeing -c sh hello.sh
seeing -c open hello.html
seeing -c node hello.js
seeing -c scrapy spider.py
Metadata
Release files for seeing 0.1.7
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 |
|---|---|---|---|---|
| seeing-0.1.7.tar.gz | 3.0 kB | Without provenance | Details for seeing-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seeing-0.1.7-py3.6.egg | Legacy Egg format | - | - | Details for seeing-0.1.7-py3.6.egg |
Total release size: 9.0 kB
Release files / seeing-0.1.7.tar.gz
| Download URL | seeing-0.1.7.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee573e7d498aefb86670a693fadc9a3c7f3e637242bc4e35159295d23db01418
|
|
BLAKE2b-256 checksum How to use checksums |
55e3dd00ff933713d515ebb7b164428c3d5ca76a64e9ef878469d8aedd5981a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.8
|
Release files / seeing-0.1.7-py3.6.egg
| Download URL | seeing-0.1.7-py3.6.egg |
|---|---|
| Size | 5.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
f87e04467d70f554874a24c382bdbac3f0660f71aee0b9602475ea287f068854
|
|
BLAKE2b-256 checksum How to use checksums |
dc9b0cd8b48bc92fb443543fd085fade9edd036b9156a46e5da7bb761b4f777f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.8
|
Security for seeing 0.1.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.
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.