This release is a pre-release and may not be stable for production use.
MONOLOGUE
==========
.. custom role to bypass the sphinx ref directive
.. role:: ref
Main documentation: http://feth.github.com/monologue/
.. include:: doc/whatsthis.rst
.. include:: doc/requirements.rst
.. include:: doc/about.rst
Don't use yet, unless you know what you're doing, because this is what's left to do:
* complete docstrings and doc; comply to joblib's doc style.
* maybe discuss some API improvements
* why not make a ProgressAndLog.progress member to hold all accessors regarding progress?
* maybe think of the same for log files.
* maybe some methods/attrs renaming should occur.
Metadata
Release files for monologue 0.0.0beta
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| monologue-0.0.0beta-py2.7.egg | Legacy Egg format | - | - | Details |
Release files / monologue-0.0.0beta-py2.7.egg
| Download URL | monologue-0.0.0beta-py2.7.egg |
|---|---|
| Size | 17.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
96bc2a1936c7487b9219080e28b622982786afb7928d7b3a091254a372cb75e2
|
|
BLAKE2b-256 checksum How to use checksums |
9c723ed9d24b92c364c614e96372cab521623b2887b5888caf2002027c4e4678
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for monologue 0.0.0beta
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.