Tests |
|
Downloads |
|
About |
|
Status |
|
About
I’ve been using a TODO list for years in paper, inspired by the book “The Personal Software Process”, by Watts S. Humprey. But I read the article The Power of the TODO List, by James Hood and I decided to implement it in that way.
Basically, there are a file per day to write down 3 parts:
In progress: This is the most important part: things to be accomplished today.
Accomplished: things that were finished today.
Backlog: Things to be accomplished in the future.
Why to use GTD?
Because it is very simple and easy to use. Just install it with pip install gtd and edit the current day with python -m gtd. That’s it.
The format is quite simple. Just the headers “In progress”, “Accomplished” and “Backlog” for these tasks, and each task must start with a hyphen and space(’- ‘).
Each day, it will copy the previous file, and:
it will remove the ‘Accomplished’ section.
it will move to the ‘In progress’ section the tasks from the ‘Backlog’ section that with a due date previous to current date.
The ‘Backlog’ section can have a due date, if they starts with [YYYY-MM-DD].
Example:
In progress: - do cool things - do useful things Accomplished: - do minor stuff Backlog: - [2049-02-31] Take on the world
Roadmap
GTD is fully usable. In the near future it should be able to generate statistics and reports with the activity.
1 maintainer
Metadata
1 maintainer
Release files for gtd 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gtd-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / gtd-0.0.4-py3-none-any.whl
| Download URL | gtd-0.0.4-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
79044d808ef1fce9c1a1305888666a2b14bd972a38190c3c278965a8330e48c4
|
|
BLAKE2b-256 checksum How to use checksums |
dd4e8ccf2e56255e673800a7b2eb327945a4628c8841fb58b8fef9faea1858b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for gtd 0.0.4
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.
