## basecampreporting Python read-only interface to Basecamp projects, with support for Scrum concepts like sprints and backlogs.
It’s being developed for use in the django-baseboard project: http://github.com/cmheisel/django-baseboard/tree/master
Future plans include adding write capability and refactoring the Scrum-y stuff into seperate classes.
1 maintainer
Metadata
1 maintainer
Release files for basecampreporting 0.5
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 | |
|---|---|---|---|---|
| basecampreporting-0.5.tar.gz | 13.5 kB | Without provenance | Details |
Release files / basecampreporting-0.5.tar.gz
| Download URL | basecampreporting-0.5.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cd859c1796138c5e40fee388fa6828da62ef3fdfdc29f29150f98e2fe9235f4
|
|
BLAKE2b-256 checksum How to use checksums |
5bb6a086599c06080a4483d7b7bcb4e02654d0ae7c9a1b736bc48514743ac3a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for basecampreporting 0.5
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.
