The Object HTTP Mapper provides tools both to expose your objects as WSGI applications, and to create objects with attributes that delegate to web requests.
Objects are generally containers, with attributes as resources in those containers. The resources are not homogenous – one might be a JSON object, another XML, another a string. HTTP methods (GET, PUT, DELETE) are used to get, set, and delete attributes.
This project is in a subversion repository and the development version can be installed with easy_install OHM==dev. Interested users should probably follow the development.
Metadata
Release files for OHM 0.1
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 |
|---|---|---|---|---|
| OHM-0.1.tar.gz | 19.0 kB | Without provenance | Details for OHM-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| OHM-0.1-py2.4.egg | Legacy Egg format | - | - | Details for OHM-0.1-py2.4.egg |
Total release size: 49.5 kB
Release files / OHM-0.1.tar.gz
| Download URL | OHM-0.1.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4155abaa0cd2a186829294e6404dad916cb08584819520d0044b6040aadd8d0a
|
|
BLAKE2b-256 checksum How to use checksums |
6a5fdcf22702e80341b6769179a30c93fd1a5be10b260b519b2a06ddd423a21f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / OHM-0.1-py2.4.egg
| Download URL | OHM-0.1-py2.4.egg |
|---|---|
| Size | 30.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
dfdaeaf055979b380e28f860d065a83a8a0af03fce809092bd1524b2b405894e
|
|
BLAKE2b-256 checksum How to use checksums |
904a8ac717e21e5f4a82ba73e96aa1bed17e8fa3c2c4b133dda14080f30c9d6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for OHM 0.1
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.