PyStandups
A command line utility for working with daily standups. A "standup" is a brief description of what work will be done that day. PyStandups supports:
- Storing standups for each day
- Reviewing the previous day's standup (in case the actual work done ended up being different from what was planned)
- A rudimentary "backlog" to save things for later standups
Standups are stored as a JSON dictionary. The location is hardcoded (see DATA_DIR). The schema and format may change without warning between versions of PyStandups, so back this up if it's important. However, the goal is to keep the data simple enough to be self-explanatory and trivial to migrate.
Usage
standup today- prepare standup at the beginning of the day. PyStandups will try to intelligently fill in as much information as possible, and you will have the opportunity to edit it in your editor.standup later- take quick notes for future standups.standup todayautomatically fills in the data fromstandup later. For more sophisticated management of planned tasks, use an external tool like Jira.standup get todayandstandup get last- print the relevant standup to standard out. These are mainly intended for use in scripts.
Old Standups
PyStandups does not support working with standups older than today or other complex tasks. You can use an external tool like jq to work with the JSON file directly.
Install
pip install pystandups to install latest release.
The project is managed by poetry so if you want to work on the code see poetry install.
Make sure you have $VISUAL (preferred) or $EDITOR set. If relevant, the command should include the "wait" parameter so that PyStandups is blocked until you close the editor window. So for example, subl -w not subl.
Metadata
Release files for pystandups 0.4.7
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 |
|---|---|---|---|---|
| pystandups-0.4.7.tar.gz | 4.2 kB | Without provenance | Details for pystandups-0.4.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pystandups-0.4.7-py3-none-any.whl | Python 3 | none | any | Details for pystandups-0.4.7-py3-none-any.whl |
Total release size: 8.8 kB
Release files / pystandups-0.4.7.tar.gz
| Download URL | pystandups-0.4.7.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec1d1e4d63f1e8224bff05818d7bd0f730515ca793d01e62bcdaba3f2b4dee77
|
|
BLAKE2b-256 checksum How to use checksums |
ea50a489ede4564b245c1563e38c454b9a34cb252498f9bb257e70515ed96798
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.5 Linux/5.15.50-1-lts
|
Release files / pystandups-0.4.7-py3-none-any.whl
| Download URL | pystandups-0.4.7-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9a946768180595cc0e321ad3a66051608fb2f30c6dced83b45f7586ac1822fd
|
|
BLAKE2b-256 checksum How to use checksums |
7ceaf0aedf92af2d0be4a350a2655060b91c37ea9e108165c750d14b3d2bb584
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.5 Linux/5.15.50-1-lts
|
Security for pystandups 0.4.7
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.