A command line tool for time-based queries on log files.
## How to install
pip install jack
To run jack, `cd` to a directory with log files (`.log` or `.log.gz` extension) and run something like this:
jack 8:15am to 8:20am
jack 8:15am to 8:20am PDT
jack 16:30 to 16:45
jack May 1st 16:30 to May 1st 16:45
jack 2014-03-01 8:15am to 2014-03-01 8:20am PDT
jack yesterday to today
## How to create and ship a change
* Mark your change in a branch off `master` and submit a pull-request on GitHub. Ping @dbader to review it.
#### Testing
* Test the package locally and make sure it installs cleanly and works via `pip install -e .` (in the project root).
#### Releasing
* Bump `PACKAGE_VERSION` in `setup.py`
* Create a git tag for the release:
* `git tag 0.0.1 -m "The best release so far"`
* `git push --tags origin master`
* `python setup.py sdist upload -r pypi`
## Roadmap
* Turn this into a `pip install`able package
* Add usage / nice errors for the CLI
* Add unit tests
* Set up TravisCI continuous integration
## Changelog
* `0.1.0`: First working PyPI release.
## Glossary
(todo)
## Where to get help
Talk to [@dbader](https://twitter.com/dbader).
1 maintainer
Metadata
1 maintainer
Release files for jack 0.1.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 | Actions |
|---|---|---|---|---|
| jack-0.1.0.tar.gz | 3.8 kB | Without provenance | Details for jack-0.1.0.tar.gz |
Release files / jack-0.1.0.tar.gz
| Download URL | jack-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a6f86c3d1ca758c84e145789032325a40e96918d1b980f64d5cce6d393adb81
|
|
BLAKE2b-256 checksum How to use checksums |
3854706884c8d0b1daac68c1f6745bb4e7fcea11999426af4fdc086c9b7cbd6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jack 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
