Basic common configuration tools used in the SPARC platform. Includes, but not limited to Zope Component ZCML utilities.
ZCA Configuration
Tools that leverage SPARC packages are usually also dependant on Zope Component Architecture (http://docs.zope.org/zope.component/narr.html). Use of ZCA requires component configuration,which SPARC does via ZCML (https://github.com/zopefoundation/zope.component/blob/master/docs/zcml.rst).
Among other things, sparc.common provides access to Configure(), an easy function that can be used to configure dependant applications.
- ### Usage - ZCA configuration
This simplifies your ability to create components via ZCML and have your application parse the ZCML files to allow them to be registered for lookup. >>> import a.package.that.contains.a.configure.zcml >>> import another.package.that.contains.a.configure.zcml >>> from sparc.common import Configure >>> Configure([your.package.that.contains.a.configure.zcml, … another.package.that.contains.a.configure.zcml])
You will now have access to components configured within those packages.
- ### Usage - Retrieve user feedback from CLI application
This simplifies the process of getting feedback for processing within a CLI application. >>> import sparc.common >>> from sparc.common import Configure >>> from sparc.common import ICallable >>> from zope.component import getUtility >>> Configure([sparc.common]) >>> asker = getUtiliy(ICallable, ‘sparc.common.ask_question’) >>> answer = asker(u”How are you?”, required = True, answers = … {‘1’:’awesome’,’2’:’ok’,’3’:’not so good’}, tries = 3) How are you? (1) awesome (2) ok (3) not so good
>>> print answer '1'
0.0.1
initial release
0.0.2
let value getter have a default
allow pacakge-less zcml imports (file-path only zcml declarations)
update IPyContainerConfigValue to allow deep key reference
fix dependency identifiers
fix generator error
remove dependency on ZCA from implementations
remove dependency on zope.component
add travis ci config
Metadata
Release files for sparc.configuration 0.0.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 |
|---|---|---|---|---|
| sparc.configuration-0.0.2.tar.gz | 12.0 kB | Without provenance | Details for sparc.configuration-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sparc.configuration-0.0.2-py2-none-any.whl | Python 2 | none | any | Details for sparc.configuration-0.0.2-py2-none-any.whl |
Total release size: 34.1 kB
Release files / sparc.configuration-0.0.2.tar.gz
| Download URL | sparc.configuration-0.0.2.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7915b0df3befa6a68fbd20fa691a7405ee9eb146ab34dfc3c1d7798498bd9fc4
|
|
BLAKE2b-256 checksum How to use checksums |
fb224095e4e8c079f797a7c5f1fc962a40995f7e32674e1c0b8ac8a0c14fb06b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / sparc.configuration-0.0.2-py2-none-any.whl
| Download URL | sparc.configuration-0.0.2-py2-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
f71a7fa190ea6617dbba90ade901b5fcd72bd81d5da2baf25075d7ff11170ff0
|
|
BLAKE2b-256 checksum How to use checksums |
0312019b87d674b0ddf257f48c5f44d5fec920544a1d0780c4ae98024a5a9cd5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sparc.configuration 0.0.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.