Rookie ninja
Official web: http://rookie.ninja
TODO:
Documentation
CHANGELOG
0.1.1 (2016-05-21)
add support absolute path config
0.1.0 (2016-05-21)
remove duplicate code
0.0.12 (2016-05-21)
Definitive fix style in pypi
0.0.11 (2016-05-21)
Prevent exception for fleets not content players
0.0.10 (2016-05-21)
if the configuration file does not exist returns a human error
Try again pypi …
0.0.9 (2016-05-21)
fix call others folders
0.0.8 (2016-05-21)
fix location statics
0.0.7 (2016-05-21)
fix TemplateNotFound
0.0.6 (2016-05-21)
fix text in pypi
0.0.5 (2016-05-21)
Remove changelog dependency
0.0.4 (2016-05-21)
try fix pypi
0.0.3 (2016-05-21)
fix dependencies
0.0.2 (2016-05-21)
fix package in pypi
fix compatible versions
0.0.1 (2016-05-21)
initial release
1 maintainer
Metadata
1 maintainer
Release files for rookieninja 0.1.2
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 |
|---|---|---|---|---|
| rookieninja-0.1.2.tar.gz | 3.4 MB | Without provenance | Details for rookieninja-0.1.2.tar.gz |
Release files / rookieninja-0.1.2.tar.gz
| Download URL | rookieninja-0.1.2.tar.gz |
|---|---|
| Size | 3.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fb229611f4de0d7c8b8c2c8d5069865ccb1d3a224002201c7070a800fd85a69
|
|
BLAKE2b-256 checksum How to use checksums |
019cbf49bc4e3c3f0fbb5e245ebd914e93d5e7f469c3b212220fc2857bd1dab5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for rookieninja 0.1.2
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.
