A modern and simplest convenient ORM package in Python. FireO is specifically designed for the Google's Firestore, it's more than just ORM. It implements validation, type checking, relational model logic and much more facilities.
Installation
pip install fireo
Example Usage
from fireo.models import Model
from fireo.fields import TextField
class User(Model):
name = TextField()
u = User()
u.name = "Azeem Haider"
u.save()
# Get user
user = User.collection.get(u.key)
print(user.name)
Documentation
Full documentation is available in the FireO Doc.
Contributing
Bug reports and pull requests are welcome. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
- Check FireO Project TODO list or newcomers contribute
- Checkout Feature branch (latest working branch)
- Write tests for your functionality
- Mention in Documentation, what you has done and how other can use it
License
This is official FireO Repository. Powered by OctaByte Licensed under Apache License 2.0
Metadata
Release files for fireo 1.1.0
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 |
|---|---|---|---|---|
| fireo-1.1.0.tar.gz | 26.1 kB | Without provenance | Details for fireo-1.1.0.tar.gz |
Release files / fireo-1.1.0.tar.gz
| Download URL | fireo-1.1.0.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1779776fb3c0702e348da76812d418dfe6a82adeb5748b34828787ab042b65b
|
|
BLAKE2b-256 checksum How to use checksums |
143fba02ed281882ec281412c1b48500ac316d99a196f7af8ffceef13e206939
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.2 requests-toolbelt/0.9.1 tqdm/4.40.0 CPython/3.6.7
|
Security for fireo 1.1.0
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.