Sanic session management for humans

:warning: Warning: This poject in Pull-Request-Only mode. I don't use Sanic anymore for any of my projects and will not make any changes by my own in foreseeable future. I recommend to use AIOHTTP since it more mature and have bigger adoption (I'm not judging by github stars only). Though I will accept pull requests from others if you want to see updates in the code.

sanic_session is session management extension for Sanic that integrates server-backed sessions with most convenient API.

sanic_session provides a number of session interfaces for you to store a client's session data. The interfaces available right now are:

Redis (supports both drivers aioredis and asyncio_redis)
Memcache (via aiomcache)
Mongodb (via sanic_motor and pymongo)
In-Memory (suitable for testing and development environments)

Installation

Install with pip (there is other options for different drivers, check documentation):

pip install sanic_session

or if you prefer Pipenv:

pipenv install sanic_session

Documentation

Documentation is available at sanic-session.readthedocs.io.

Also, make sure you read OWASP's Session Management Cheat Sheet for some really useful info on session management.

Example

A simple example uses the in-memory session interface.

from sanic import Sanic
from sanic.response import text
from sanic_session import Session, InMemorySessionInterface

app = Sanic()
session = Session(app, interface=InMemorySessionInterface())

@app.route("/")
async def index(request):
    # interact with the session like a normal dict
    if not request.ctx.session.get('foo'):
        request.ctx.session['foo'] = 0

    request.ctx.session['foo'] += 1

    return text(request.ctx.session['foo'])

if __name__ == "__main__":
    app.run(host="0.0.0.0", port=8000)

Examples of using redis and memcache backed sessions can be found in the documentation, under Using the Interfaces.

— ⭐️ —

Metadata

Release files for sanic-session 0.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sanic-session 0.8.0
File	Size	Uploaded	Provenance
sanic_session-0.8.0.tar.gz	9.9 kB	Apr 7, 2021	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for sanic-session 0.8.0
File	Interpreter	ABI	Platform	Reset
sanic_session-0.8.0-py3-none-any.whl 13.1 kB Apr 7, 2021 Without provenance	Python 3	none	any	Details

Total release size: 23.0 kB

Release files / sanic_session-0.8.0.tar.gz

Download URL	sanic_session-0.8.0.tar.gz
Size	9.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`c9c500f015f22577d5c9c7743d637741b50f97e1689fa795318d614b6dbb58d8`
BLAKE2b-256 checksum How to use checksums	`da9914e37b8a0141495d5141adbc62bb88c223a6fd53255b8ab623d20dc89c09`
Upload date	Apr 7, 2021
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.0`

Release files / sanic_session-0.8.0-py3-none-any.whl

Download URL	sanic_session-0.8.0-py3-none-any.whl
Size	13.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`ead1b62c4c7773cfaaa22d77ed0eb23b423d1d60b21e11225cc9132dff37b2dd`
BLAKE2b-256 checksum How to use checksums	`233af9df6b7206956b150ca9057659fc85ded4ee607c531e4f29fe5c65cb3f61`
Upload date	Apr 7, 2021
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.0`

Security for sanic-session 0.8.0

Report project as malware

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.