Incremental Progress
This project is intended to be a tool for showing the incremental changes necessary to get something working. Incremental Progress takes a copy of the source file and resulting test output for simple projects.
Configuration
To configure Incremental Progress, create a config file in the root of your project.
An example can be found in ./example/config.ini
Overall the setup is simple.
[DEFAULT]
test_runner = pipenv run pytest
monitored_path = ./
pytest_to_markdown = True
storage_path = ./step-by-step/
[PROGRESS]
monitored_files = ['./incremental/processor.py', './setup.py', './incremental/cli.py']
Where monitored_files is the path from root to the file you are editing and
where test_runner is the command to run that executes your tests.
Use of pytest-md
Pytest-md is a package that will write test outputs to an MD file.
This configuration option allows for easy to read results that have the same timestamp as the incremental file.
If this option is not enabled, the results will be written to a file as captured stdout and stderr.
Historical Information gathering
Incremental Progress will capture a copy of the source file and a snapshot of the results of test_runner in a temp directory.
This will allow for viewing of the steps you have made during your progress towards functional code.
How to capture your incremental progress
- Install Incremental Progress
pip install incremental-progress - Add configuration file. See the configuration section
- start Incremental Progress:
incremental-progress
Incremental Progress will run till killed. This is a lightweight process as it uses watches for IO interaction and not direct monitoring.
Renders
Current:
- Saves copies of the source file to a directory timestamped.
- Saves copies of the results of
test_runnerto a directory timestamped.
Future:
- Turn the code into syntax highlighted frames for a gif.
- Turn the results of the test runner into highlighted frames for a gif.
- Do a left / right with code and tests results as a gif.
- Monitor all files in a path. Complications on this cause recursion.
Improvements
- Use custom class of DefaultDirWatcher
to watch for all directories except for the
storage_path
Release files for incremental-progress 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| incremental-progress-1.1.0.tar.gz | 3.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| incremental_progress-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Release files / incremental-progress-1.1.0.tar.gz
| Download URL | incremental-progress-1.1.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65b8cba0a9ac5281886a25a4da62b29b98a491c5326224ce70e6fa885dc7dfd7
|
|
BLAKE2b-256 checksum How to use checksums |
dcfb0223518345ed4126d5232fbe01f45a854090d94a29b07ec726862fac100e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.5
|
Release files / incremental_progress-1.1.0-py3-none-any.whl
| Download URL | incremental_progress-1.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d03bd9bdd34e2397fb94dedb5cb16a70d7c5b70bc51f582371eea6438c20014
|
|
BLAKE2b-256 checksum How to use checksums |
54a47c4507c0e9cc7bcd5026fed26d324e08bb5266887f6a7dc64f7167ec629d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.5
|