taggregator
Find lines of source code you have tagged with custom categories, defined inside a config.json file.
For example, to tag a piece of code which contains a bug, write a comment as below:
do_stuff()
# @BUG(HIGH) buggy_code() throws an unhandled exception!
buggy_code()
do_more_stuff()
You can then run tagg in the project root directory and it will output the file name, line number and description to the console as below.
taggregator/taggregator/taggregator.py :57 # @BUG(HIGH) Throws OSError on some files if in use
taggregator/taggregator/taggregator.py :64 # @SPEED(MEDIUM) Regex search of processed line
taggregator/taggregator/__main__.py :34 # @TODO(LOW) Allow user to specify path for config file
Each line marked with a tag will be ordered and coloured by priority. By default, there are a number of tags and priorities in the config file installed.
Installation
$ pip3 install --upgrade taggregator
Installation will also create a config file at ~/.taggregator/config.json but the program will prioritise a config file stored in {current_directory}/.taggregator/config.json if it exists.
Run
From project root
$ tagg
From a specified folder
$ tagg Assets/Scripts
Only return lines marked with "speed" and "refactor"
$ tagg -t "speed, refactor"
Create config file in current directory
$ tagg create .
Workflow integration
It might be useful to bind taggregator to a key combination in a tool like vim. For example, place this in your ~/.vimrc:
nnoremap <leader>t :!clear;tagg<CR>
Presuming your vim leader is ',' you can then access your taggregator todo list at any time by typing ',t' while editing.
Metadata
Release files for taggregator 0.0.40
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 |
|---|---|---|---|---|
| taggregator-0.0.40.tar.gz | 8.2 kB | Without provenance | Details for taggregator-0.0.40.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| taggregator-0.0.40-py3-none-any.whl | Python 3 | none | any | Details for taggregator-0.0.40-py3-none-any.whl |
Total release size: 25.1 kB
Release files / taggregator-0.0.40.tar.gz
| Download URL | taggregator-0.0.40.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a57958976b2d36bac064d522364db3d736dba751c98987021d9437862fb73755
|
|
BLAKE2b-256 checksum How to use checksums |
bf16eaf4fbbf910fea427e58dd2ce96612913cbb8f9e0a877a0a7f75c01cb53e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.9.1 setuptools/36.6.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/2.7.15
|
Release files / taggregator-0.0.40-py3-none-any.whl
| Download URL | taggregator-0.0.40-py3-none-any.whl |
|---|---|
| Size | 17.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bfe83200fce99e758d74ad2a0b8344a8ec30a56f9f371e8e0b7c8c60d5059da0
|
|
BLAKE2b-256 checksum How to use checksums |
7ddf1c909c159b3dfd510795ce45e76049bcf7891858a1045832aed9c0d1944e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.9.1 setuptools/36.6.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/2.7.15
|
Security for taggregator 0.0.40
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.