Mortar
Mortar will be an environment that insulates the application developer from the implementation details of storage, retrieval and searching of content.
This will allow applications to be developed in one environment, say on a simple local Python+SQLite setup, and then deploy to another environment, say Google App Engine or a clustered array of Amazon EC2 instances, with no changes to application code.
This architecture should also provide a seamless environment for application developers to work with a disparate array of data sources.
A secondary aim is to allow DBAs and system administrators to optimise the performance of applications without modifying any application code.
However, for now, it is in the very early stages of development and should probably be avoided unless you simply want to see how it’s shaping up or you want to actively participate in development.
1 maintainer
Metadata
1 maintainer
Release files for mortar 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 |
|---|---|---|---|---|
| mortar-0.1.2.tar.gz | 14.5 kB | Without provenance | Details for mortar-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mortar-0.1.2-py2.6.egg | Legacy Egg format | - | - | Details for mortar-0.1.2-py2.6.egg |
Total release size: 58.4 kB
Release files / mortar-0.1.2.tar.gz
| Download URL | mortar-0.1.2.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82496d42b43766f11e49bb5fc8e718cf4182bf62c18ccb1411ed0b5f76886c14
|
|
BLAKE2b-256 checksum How to use checksums |
f2cacd0ba66a83aa67018013b5dea963a7379320d9e695ef7a8284912e81c414
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / mortar-0.1.2-py2.6.egg
| Download URL | mortar-0.1.2-py2.6.egg |
|---|---|
| Size | 43.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
5dacfc9ec73464f8f6187455bb5a1ac2dacc4d17844a7e395982906f99762a8e
|
|
BLAKE2b-256 checksum How to use checksums |
f940ef55d39b3b0537719bc14ab33ad470ff3f8d626bb0b7055da9462c627d49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mortar 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.
