#Journal
Journal is a Python command line tool to help with keeping a date and time
organized journal for work, personal, or any reason really!
Inspired by Peter Lyons' [article](http://peterlyons.com/leveling_up.html) on career development, my own experiences, and too much free time.
Related:
* [My blog post explaining Journal](http://asktherelic.com/2011/08/16/journaling/)
##Installation
Journal is on pypi at [http://pypi.python.org/pypi/journal/](http://pypi.python.org/pypi/journal/)
To install, from a command line:
$ pip install journal
or
$ easy_install journal
depending on how much Python work you do.
Journal only requires Python, (tested on Python 2.5, 2.6, 2.7).
The `journal` command should now be available on your command line.
##Usage
It's as simple as:
$ journal "Task foo completed"
and a `~/.journal/[DATE].txt` file will be created using the current date with a timestamp and your entry appended to that file. Keep entering your tasks you complete during the day and then you can quickly view your work at the end of the day. Or review what you did yesterday, just before your morning scrum meeting! Or review what you did last week, when you come back on Monday! Build a simple record of your work and gain better understanding of your work.
The API for viewing and listing previous entries is currently a WIP, but you
should be able to view specific entries for a day by using the flag `--view|-v`.
Short tags work with these dates.
$ journal --view "yesterday"
$ journal --view "12 days ago"
$ journal --view "8/14"
# Easiest way to view today (t)
$ journal -vt
# Easiest way to view yesterday (y)
$ journal -vy
You can view all entries since a specific previous date, using the flag
`--since`. This is sparse output, dates without entries will be skipped quietly.
$ journal --since "yesterday"
$ journal --since "7 days ago"
##Advanced usage
By default, journal entries are stored in `~/.journal`. By providing the `--location|-l path` command line switch entries will be read from & written to the provided directory. This functionality is useful for having journals dealing with separate domains:
$ journal -l ~/.work "Got all of the monies"
$ journal -l ~/.home "Spent all the monies"
See below for using a `.journalrc` to define these journals & storage locations.
###Configuration
You can create a `.journalrc` file (or one specified with the `-c` switch) to define default journal directories:
[journal]
default: work
[home]
location: ~/Dropbox/journals/home
[work]
location: ~/Dropbox/journals/work
With multiple journals defined, you can use the `--journal|-j name` switch to choose which journal to write to.
#History
##v0.4.0 - WIP
- more tests?
##v0.3.0 - 2012/05/09
- added support for multiple journals and journal locations
- added ~/.journalrc for storing default configurations of journals/locations
- changed argument handling to add all arguments to the same entry instead of
splitting them up
##v0.2.0 - 2011/08/18
- added multiple journal messages from 1 command line; multi-arg entries
- added '--since' and '--view' args to view previous entries using human-readable dates
##v0.1.0 - 2011/08/16
- working journal recording
- view entries made today
Journal is a Python command line tool to help with keeping a date and time
organized journal for work, personal, or any reason really!
Inspired by Peter Lyons' [article](http://peterlyons.com/leveling_up.html) on career development, my own experiences, and too much free time.
Related:
* [My blog post explaining Journal](http://asktherelic.com/2011/08/16/journaling/)
##Installation
Journal is on pypi at [http://pypi.python.org/pypi/journal/](http://pypi.python.org/pypi/journal/)
To install, from a command line:
$ pip install journal
or
$ easy_install journal
depending on how much Python work you do.
Journal only requires Python, (tested on Python 2.5, 2.6, 2.7).
The `journal` command should now be available on your command line.
##Usage
It's as simple as:
$ journal "Task foo completed"
and a `~/.journal/[DATE].txt` file will be created using the current date with a timestamp and your entry appended to that file. Keep entering your tasks you complete during the day and then you can quickly view your work at the end of the day. Or review what you did yesterday, just before your morning scrum meeting! Or review what you did last week, when you come back on Monday! Build a simple record of your work and gain better understanding of your work.
The API for viewing and listing previous entries is currently a WIP, but you
should be able to view specific entries for a day by using the flag `--view|-v`.
Short tags work with these dates.
$ journal --view "yesterday"
$ journal --view "12 days ago"
$ journal --view "8/14"
# Easiest way to view today (t)
$ journal -vt
# Easiest way to view yesterday (y)
$ journal -vy
You can view all entries since a specific previous date, using the flag
`--since`. This is sparse output, dates without entries will be skipped quietly.
$ journal --since "yesterday"
$ journal --since "7 days ago"
##Advanced usage
By default, journal entries are stored in `~/.journal`. By providing the `--location|-l path` command line switch entries will be read from & written to the provided directory. This functionality is useful for having journals dealing with separate domains:
$ journal -l ~/.work "Got all of the monies"
$ journal -l ~/.home "Spent all the monies"
See below for using a `.journalrc` to define these journals & storage locations.
###Configuration
You can create a `.journalrc` file (or one specified with the `-c` switch) to define default journal directories:
[journal]
default: work
[home]
location: ~/Dropbox/journals/home
[work]
location: ~/Dropbox/journals/work
With multiple journals defined, you can use the `--journal|-j name` switch to choose which journal to write to.
#History
##v0.4.0 - WIP
- more tests?
##v0.3.0 - 2012/05/09
- added support for multiple journals and journal locations
- added ~/.journalrc for storing default configurations of journals/locations
- changed argument handling to add all arguments to the same entry instead of
splitting them up
##v0.2.0 - 2011/08/18
- added multiple journal messages from 1 command line; multi-arg entries
- added '--since' and '--view' args to view previous entries using human-readable dates
##v0.1.0 - 2011/08/16
- working journal recording
- view entries made today
Metadata
Release files for journal 0.4.0
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 | |
|---|---|---|---|---|
| journal-0.4.0.tar.gz | 7.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| journal-0.4.0.macosx-10.10-x86_64.tar.gz | Details |
Total release size: 19.3 kB
Release files / journal-0.4.0.tar.gz
| Download URL | journal-0.4.0.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f84a3cf2df04583d4bab3ca6ddd843810235aa11083561a94570910d9b78843e
|
|
BLAKE2b-256 checksum How to use checksums |
6f2e5df4b55581672578cf050c0345eb1f860f20a3272c625b1b2d165831651e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / journal-0.4.0.macosx-10.10-x86_64.tar.gz
| Download URL | journal-0.4.0.macosx-10.10-x86_64.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60e22afe13675b79ea45fd4e2e559300125be2aba77c7df890e8614a576b45c1
|
|
BLAKE2b-256 checksum How to use checksums |
7a62b25ac53f1461c63e8567a2a634bd1e72794de7cb766b4f737835401ae11a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for journal 0.4.0
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.