big-todo
Make a big TODO file by concatenating all TODO files in a directory tree.
install
pip install big-todo
usage
usage: btodo - make a big TODO file [-h] [--name NAME] [--include-header] dir
positional arguments: dir the root directory
optional arguments: -h, --help show this help message and exit --name NAME the name of the file to combine --include-header prepend the relative file path to each section
example use
From the repo root, run:
big-todo demo_folder --include-header
This will traverse the demo_folder and generate a virtual TODO file with headers turned on, meaning the path of the file being appended will be inserted as the first line of output.
1 maintainer
Metadata
1 maintainer
Release files for big-todo 0.0.5
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 |
|---|---|---|---|---|
| big-todo-0.0.5.tar.gz | 2.1 kB | Without provenance | Details for big-todo-0.0.5.tar.gz |
Release files / big-todo-0.0.5.tar.gz
| Download URL | big-todo-0.0.5.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
89f28a20f8da51abcff0584ba14b96872fa67df041878fbe2b0f4c27b6884dc4
|
|
BLAKE2b-256 checksum How to use checksums |
78b7f3fefac969517e3827614beaa56025c080973912c93cb1c906880666c631
|
| 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/40.8.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.6
|
Security for big-todo 0.0.5
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.
