This release is a pre-release and may not be stable for production use.
Usage
rerun [options] <command>
where ‘options’ may include:
--verbose|-v List changed files before <command> output
--ignore|-i <D> Directory or filename to ignore. Changes to this file
do not trigger another execution of <command>.
e.g:
rerun python -m unittest mypackage.mymodule
will rerun your tests every time you save your source code. Handy for seeing the new test results in a console window after you hit ‘save’ in your editor, without having to change window focus.
It detects changes to files by polling file modification times once per second. On detecting any changes, it clears the terminal and reruns the given command.
Polling for modification times perhaps isn’t ideal. Registering of OS-specific notifications of file system events might be better. In practice though, I haven’t noticed it burden my machine, even in project directories containing hundreds of files.
It ignores directories called .svn, .git, .hg, .bzr, build and dist. It ignores files ending with .pyc or .pyo.
Dependencies
Tested on WindowsXP, Windows 7, MacOSX, and Ubuntu.
Runs under Python2.7 or 3.2.
No other dependencies.
Install
pip install rerun
Thanks
The idea came from the Bash command ‘watch’, and inspiration for this implementation came from an old blog post by Jeff Winkler, whos website http://jeffwinkler.net seems to have now died.
Contact
Jonathan Hartley, tartley@tartley.com
Metadata
Release files for rerun 1.0.1-beta
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distributions (sdists)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rerun-1.0.1-beta.zip | 7.2 kB | Without provenance | Details for rerun-1.0.1-beta.zip | |
| rerun-1.0.1-beta.tar.gz | 3.9 kB | Without provenance | Details for rerun-1.0.1-beta.tar.gz |
Release files / rerun-1.0.1-beta.zip
| Download URL | rerun-1.0.1-beta.zip |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3eb04bd46f5537b2a526a8d216c9167b942c642873c595b13ab4b5c28d8b9bb
|
|
BLAKE2b-256 checksum How to use checksums |
96821b8fb988e433c47863009a9a879ba18b4de45d449049d3ea1ddbfdf07e40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / rerun-1.0.1-beta.tar.gz
| Download URL | rerun-1.0.1-beta.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1dea72f8166d07a786bc8c783caf2d919a526a7d502f960f57bbcfc037ebc66d
|
|
BLAKE2b-256 checksum How to use checksums |
23e2ceb3a15c04e762f147af5dedaaf430de8c767153186274343c998103a888
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rerun 1.0.1-beta
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.