✨ The Smalest ASGI framework for python ✨
Documentation: https://www.ngiri.co.tz/
ngiriapi
Ngiriapi is a lightweight ASGI framework/toolkit, which is ideal for building async web services in Python.
It is production-ready, and gives you the following:
- A lightweight, low-complexity HTTP web framework.
- WebSocket support.
- In-process background tasks.
- Startup and shutdown events.
- Test client built on
httpx. - CORS, GZip, Static Files, Streaming responses.
- Session and Cookie support.
- 100% test coverage.
- 100% type annotated codebase.
- Few hard dependencies.
- Compatible with
asyncioandtriobackends. - Great overall performance against independent benchmarks.
Requirements
Python 3.8+
Installation
$ pip3 install ngiriapi
You'll also want to install an ASGI server, such as uvicorn, daphne, or hypercorn.
$ pip3 install uvicorn
Example
example.py:
from ngiriapi.applications import ngiriapi
from ngiriapi.responses import JSONResponse
from ngiriapi.routing import Route
async def homepage(request):
return JSONResponse({'hello': 'world'})
routes = [
Route("/", endpoint=homepage)
]
app = ngiriapi(debug=True, routes=routes)
Then run the application using Uvicorn:
$ uvicorn example:app
For a more complete example, see pesaply/ngiriapi-example.
Dependencies
ngiriapi only requires anyio, and the following are optional:
- [
httpx][httpx] - Required if you want to use theTestClient. jinja2- Required if you want to useJinja2Templates.python-multipart- Required if you want to support form parsing, withrequest.form().itsdangerous- Required forSessionMiddlewaresupport.pyyaml- Required forSchemaGeneratorsupport.
You can install all of these with pip3 install ngiriapi[full].
Framework or Toolkit
ngiriapi is designed to be used either as a complete framework, or as an ASGI toolkit. You can use any of its components independently.
from ngiriapi.responses import PlainTextResponse
async def app(scope, receive, send):
assert scope['type'] == 'http'
response = PlainTextResponse('Hello, world!')
await response(scope, receive, send)
Run the app application in example.py:
$ uvicorn example:app
INFO: Started server process [11509]
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
Run uvicorn with --reload to enable auto-reloading on code changes.
Modularity
The modularity that ngiriapi is designed on promotes building re-usable components that can be shared between any ASGI framework. This should enable an ecosystem of shared middleware and mountable applications.
The clean API separation also means it's easier to understand each component in isolation.
Metadata
Release files for Ngiriapi 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ngiriapi-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for ngiriapi-0.0.2-py3-none-any.whl |
Release files / ngiriapi-0.0.2-py3-none-any.whl
| Download URL | ngiriapi-0.0.2-py3-none-any.whl |
|---|---|
| Size | 70.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f4851b0870c1de0fff4fb07b4bab3f24b94ccf2238552b313dd5a1a13ddad69
|
|
BLAKE2b-256 checksum How to use checksums |
bad32128d364119b1adf4a2421aa073f3df773cc74dff24271bc2877401bfa49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for Ngiriapi 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.