Sanic-CookieSession implements a client side only, cookie-based session to be used with Sanic. Similar to the built-in session in Flask.
Quick Start
Installation
pip install Sanic-CookieSessionHow to use it
from sanic import Sanic, response
import sanic_cookiesession
app = Sanic(__name__)
app.config['SESSION_COOKIE_SECRET_KEY'] = 'abcd'
sanic_cookiesession.setup(app)
@app.route('/')
def index(request):
session = request.ctx.session
session.setdefault('c', 0)
session['c'] += 1
return response.text(session['c'])
if __name__ == '__main__':
app.run(debug=True)That’s it.
For more details, please see documentation.
License
BSD New, see LICENSE for details.
Links
1 maintainer
Metadata
1 maintainer
Release files for Sanic-CookieSession 0.3.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 | |
|---|---|---|---|---|
| sanic_cookiesession-0.3.1.tar.gz | 4.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sanic_cookiesession-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Security for Sanic-CookieSession 0.3.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.
