TCrudge - simple async CRUDL based on Tornado and Peewee ORM (Peewee Async)
Full documentation (http://tcrudge.readthedocs.io/en/latest/)
What is it?
Simple configurable framework to create CRUDL (Create, Read, Update, Delete, List) for models. TCrudge is under heavy development - tons of bugs are expected. You can use it in production, but API can be broken at any moment.
Why?
Tornado is fast. Peewee is great. REST is wonderful.
Dependencies
Tornado (https://github.com/tornadoweb/tornado)
Peewee (https://github.com/coleifer/peewee)
Peewee-async (https://github.com/05bit/peewee-async)
Installation
tcrudge is distributed via pypi: https://pypi.python.org/pypi/tcrudge/
pip install tcrudge
You can manually install latest version via GitHub:
pip install git+https://github.com/CodeTeam/tcrudge.git
How to?
Describe models using Peewee ORM. Subclass tcrudge.ApiListHandler and tcrudge.ApiItemHandler. Connect handlers with models using model_cls handler attribute. Add urls to tornado.Application url dispatcher.
For detailed example see tests (also, tests are available in Docker container with py.test).
You can run tests in docker container only. You’ll need docker and docker-compose.
Go to project root directory
Run docker-compose up, it builts and runs containers.
Go to tcrudge container bash: docker exec -ti tcrudge_tcrudge_1 bash
Run: DATABASE_URL=postgresql://user:dbpass@pg/test pytest
Features?
DELETE request on item is disabled by default. To enable it implement _delete method in your model.
Models are fat. _create, _update, _delete methods are supposed to provide different logic on CRUD operations
Django-style filtering in list request: __gt, __gte, __lt, __lte, __in, __isnull, __like, __ilike, __ne are supported. Use /?model_field__<filter_type>=<filter_condition> for complex or /?model_field=<filter_condition> for simple filtering.
Django-style order by: use /?order_by=<field_1>,<field_2> etc
Serialization is provided by Peewee: playhouse.shortcuts.model_to_dict. recurse, exclude and max_depth params are implemented in base class for better experience. If you want to serialize recurse foreign keys, do not forget to modify get_queryset method (see Peewee docs for details, use .join() and .select())
Validation is provided out-of-the box via jsonschema. Just set input schemas for base methods (e.g. post_schema_input, get_schema_input etc). Request query is validated for GET and HEAD. Request body is validated for POST, PUT and DELETE.
Pagination is activated by default for lists. Use default_limit and max_limit for customization. Pagination params are set through headers (X-Limit, X-Offset) or query: /?limit=100&offset=5. Total amount of items is not returned by default. HEAD request should be sent or total param set to 1: /?total=1
List handler supports default filtering and ordering. Use default_filter and default_order_by class properties.
Example
import asyncio
import peewee
import peewee_async
from playhouse.db_url import parse
from tornado import web
from tornado.ioloop import IOLoop
from tcrudge.handlers import ApiListHandler, ApiItemHandler
from tcrudge.models import BaseModel
# Configure Tornado to use asyncio
IOLoop.configure('tornado.platform.asyncio.AsyncIOMainLoop')
# Create database
DATABASE_URL = 'postgresql://user:dbpass@pg/test'
db_param = parse(DATABASE_URL)
db = peewee_async.PooledPostgresqlDatabase(**db_param)
# CRUDL Model
class Company(BaseModel):
name = peewee.TextField()
active = peewee.BooleanField()
class Meta:
database = db
# CL Handler
class CompanyDetailHandler(ApiItemHandler):
model_cls = Company
# RUD Handler
class CompanyListHandler(ApiListHandler):
model_cls = Company
default_filter = {'active': True}
app_handlers = [
('^/api/v1/companies/', CompanyListHandler),
('^/api/v1/companies/([^/]+)/', CompanyDetailHandler)
]
application = web.Application(app_handlers)
# ORM
application.objects = peewee_async.Manager(db)
with application.objects.allow_sync():
# Creates table, if not exists
Company.create_table(True)
application.listen(8080, '0.0.0.0')
loop = asyncio.get_event_loop()
# Start application
loop.run_forever()
Сontributors
[Borisov Sergey] (https://github.com/juntatalor)
[Shalamov Maxim] (https://github.com/mvshalamov)
[Nikolaev Alexander] (https://github.com/wokli)
[Krasavina Alina] (https://github.com/thaelathy)
[Ivanov Denis] (https://github.com/steinerr)
Metadata
Release files for tcrudge 0.9.11
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 |
|---|---|---|---|---|
| tcrudge-0.9.11.tar.gz | 34.3 kB | Without provenance | Details for tcrudge-0.9.11.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tcrudge-0.9.11-py3-none-any.whl | Python 3 | none | any | Details for tcrudge-0.9.11-py3-none-any.whl |
Total release size: 75.7 kB
Release files / tcrudge-0.9.11.tar.gz
| Download URL | tcrudge-0.9.11.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79d207fca14645bbeccf93909b83ef82ab3c063cd977799c8dcf99778e5aac01
|
|
BLAKE2b-256 checksum How to use checksums |
8ef17ee27257d45ad0246a79456d40869254c283be956e2eec348fc530fea874
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tcrudge-0.9.11-py3-none-any.whl
| Download URL | tcrudge-0.9.11-py3-none-any.whl |
|---|---|
| Size | 41.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2883631934b84bfcb2da555506ec069744fbb05b58c68b4a0685598ec219de9
|
|
BLAKE2b-256 checksum How to use checksums |
aceff94f25cb171fcd6ad4d66032420358e35400745a116a33d98a4c687ed99a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tcrudge 0.9.11
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.