This release is a pre-release and may not be stable for production use.
The Problem
Timeclocks are too cumbersome – just keep track of the things I did.
In my job, I tend to do a lot of development which involves losing track of time and getting lost in other peoples’ code.
I also happen to do user support which involves reacting to received emails, phone calls, and disturbances I notice on our systems.
Every two weeks, I have to report on “what I’ve been doing for the past two weeks” and tend to forget everything of importance (who I helped which actually translates to who owes us something) and only remember all the things that are really important to me – my code.
All the time tracking tools I investigated (including the online ones and even the command line ones (this one was the coolest)) were too cumbersome. I didn’t want to keep track of exactly how much time I spent doing X, Y, and Z, I didn’t want to remember to punch in and out of my own workspace. Thus, I wrote didit one afternoon.
- Features:
Simple, CLI, and doesn’t impose timeclock behavior on your otherwise flexible self.
Respects .rst markup just like pypi and python.
Will look for an $EDITOR environment variable when it needs one.
Keeps its database(s) in python shelve files in a ~/.didit/ folder making it easy to reference your done-deals from other python code should you want to.
There are too many tools like this out there. This one isn’t a game-changer, but its about as simple as can be.
I hope you like it.
Installation
% sudo pip install diddit
Usage
% didit-remember -c work -m 'Wrote `diddit`. Thank god.' % didit-remember --message 'Helped L. User parallelize his ``Mathematica`` code.' % didit-remember -c personal # <-- This launches `vim` for me! % didit-report --categories=work,general,personal work ~~~~ 2011-05-05: - Wrote `diddit`. Thank god. general ~~~~~~~ 2011-05-05: - Helped L. User parallelize his ``Mathematica`` code. personal ~~~~~~~~ 2011-05-05: - Drank a beer.
One of the benefits of .rst:
% didit-report --days=7 -c work > thisweek.rst && rst2pdf thisweek.rst
Get the source
…from my github account and make it better!
Metadata
Release files for didit 0.3.0dev
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 | |
|---|---|---|---|---|
| didit-0.3.0dev.tar.gz | 4.9 kB | Without provenance | Details |
Release files / didit-0.3.0dev.tar.gz
| Download URL | didit-0.3.0dev.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a93747c077bb489cc099206a6eaa551612191571c2fa67b0a19876358a58ba6b
|
|
BLAKE2b-256 checksum How to use checksums |
19e41e6191680612272ca6f4c90234bdef501d4aaf09ea1e04dcf1fa35baaa1e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for didit 0.3.0dev
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.