let-me-render-that-4u (lmrt4u)
Python Package for the lmrt4u agile artefact render tool
Package
Basic structure of package is
├── README.md
├── lmrt4u
│ ├── __init__.py
│ ├── __main__.py
│ ├── controller.py
│ ├── entry.py
│ ├── helpers.py
│ ├── initializer.py
│ ├── interface.py
│ ├── loader.py
│ ├── parser.py
│ ├── renderer.py
│ ├── tuples.py
│ └── validator.py
├── requirements.txt
└── setup.py
Installation
To install the tool without the use of the code repository
pip install lmrt4u-dbneal
Usage
To run the tool do
python -m lmrt4u
This generates a sample Lmrt4ufile in current directory. File can be modified manually then re-run to display updated sprint information.
To run the tool without leveraging to user interface you can pass arguments directly
python -m lmrt4u Burndown Chart
Lmrt4uFile
The Lmrt4uFile contains the backlog information that will be used when the burndown charts are generated. Please note that all sprint properties are enforced through a verification module so make sure to follow the configuration guide below.
Here's a brief example of the file (All information in parenthesis is for the user and should NOT be included in the file):
sprints: (List of sprints contained in the backlog, sample file contains one but you can include as many as you'd like)
Sample Sprint: (This is the name of a sprint)
active: true (A boolean property, if a sprint is active (True) then a burndown chart will be generated)
end: '2019-04-16' (End date for the sprint, *must occur after the start date*, *must match format 'yyyy-MM-DD'*)
start: '2019-04-02' (Start date for the sprint, *must match format 'yyyy-MM-DD'))
stories: (List of arguments with each unique item representing a story)
- - Story Name 1 (This is the name of a story in the sprint)
- This is the description (This is the description for the story)
- 10 (This is the amount of story points assigned to the story)
- '2019-04-03' (This is the completion date, put null if the story is yet to be completed)
Requirements
Package requirements are handled using pip. To install them do
pip install -r requirements.txt
Credits & References
Python module template taken from mtchavez/python-package-boilerplate
SDD template taken from CSUF Course COP3331 Template
Metadata
Release files for lmrt4u-dbneal 0.0.3
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 |
|---|---|---|---|---|
| lmrt4u-dbneal-0.0.3.tar.gz | 5.8 kB | Without provenance | Details for lmrt4u-dbneal-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lmrt4u_dbneal-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for lmrt4u_dbneal-0.0.3-py3-none-any.whl |
Total release size: 15.0 kB
Release files / lmrt4u-dbneal-0.0.3.tar.gz
| Download URL | lmrt4u-dbneal-0.0.3.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a10a9f1d0d557f3d4b605f7e13ba271e3033daa3ebb26e84239ae67d2ec7f5d5
|
|
BLAKE2b-256 checksum How to use checksums |
e573f709913897519b1044d6e9b45bef7144cd3a527680b79f2b9ba8724ef027
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Release files / lmrt4u_dbneal-0.0.3-py3-none-any.whl
| Download URL | lmrt4u_dbneal-0.0.3-py3-none-any.whl |
|---|---|
| Size | 9.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23bf9db7306f9c53f8ea80f9ff4d4533316fe75812dbacf0b91f305bab86e48f
|
|
BLAKE2b-256 checksum How to use checksums |
38270c82abcc30990aea04122779bfd626959f5e6fe2cc429459e8a57a2b6298
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.7.2
|
Security for lmrt4u-dbneal 0.0.3
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.