ttrac
a script to track your working times
installation
pip install ttrac
usage
data file
The data file will be created on your first ttrac start. The default path is ~/.config/ttrac/data.json, but you can use every command with -f/--file argument to specify a different file
commands
$ ttrac
Usage: ttrac [OPTIONS] COMMAND [ARGS]...
Options:
--help Show this message and exit.
Commands:
break combines subcommand that allows you to take a break
cat prints content of the data file
file prints path to the data file
start start timetracking
status show all tracked times of the given day
stop stop timetracking
version prints the installed ttrac version
example
Here is an example how ttrac status output looks like:
+----------+----------------+
| day | 21-05-2021 |
+----------+----------------+
| start | 09:15:44 |
| duration | 0:28:07.180515 |
| stop | - |
+----------+----------------+
if you append -t\--total, all tracked days will be printed
+------------+------------+
| day | 19-05-2021 |
+------------+------------+
| start | 07:04:18 |
| duration | 7:24:15 |
| stop | 14:28:33 |
| Breaks | |
| - start | 08:59:41 |
| - stop | 09:21:11 |
| - duration | 0:21:30 |
+------------+------------+
+------------+------------+
| day | 20-05-2021 |
+------------+------------+
| start | 07:04:18 |
| duration | 7:25:42 |
| stop | 14:30:00 |
| Breaks | |
| - start | 13:02:02 |
| - stop | 13:03:59 |
| - duration | 0:01:57 |
+------------+------------+
+----------+----------------+
| day | 21-05-2021 |
+----------+----------------+
| start | 09:15:44 |
| duration | 0:23:05.789542 |
| stop | - |
+----------+----------------+
The corresponding data file looks like this(ttrac cat):
{
"19-05-2021": {
"start": "07:04:18",
"breaks": [
{
"start": "08:59:41",
"stop": "09:21:11"
}
],
"stop": "14:28:33"
},
"20-05-2021": {
"start": "07:04:18",
"stop": "14:30:00",
"breaks": [
{
"start": "13:02:02",
"stop": "13:03:59"
}
]
},
"21-05-2021": {
"start": "09:15:44"
}
}
Metadata
Release files for ttrac 0.0.8
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 | |
|---|---|---|---|---|
| ttrac-0.0.8.tar.gz | 3.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ttrac-0.0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.9 kB
Release files / ttrac-0.0.8.tar.gz
| Download URL | ttrac-0.0.8.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
463a450e9398a36b88fedbca5d6bae6f563614c992a49b82ac66d86386263c64
|
|
BLAKE2b-256 checksum How to use checksums |
e55b6611c96d456a19c77c7fd6ce7b9cc3d9883f2bf9a88d32f040e490883d33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Release files / ttrac-0.0.8-py3-none-any.whl
| Download URL | ttrac-0.0.8-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0877a4cc679c8d7b48e34b1834980ec7701b7d976e40da4e9eab6b0bd1098bdb
|
|
BLAKE2b-256 checksum How to use checksums |
804935fdec4fb466a6514b5d16042924d6ebcb875842a9644ac1a62e9f8bc329
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.5
|
Security for ttrac 0.0.8
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.