This release is a pre-release and may not be stable for production use.
pyramid_pluggable_session
Want to be able to change out session backends using a simple configuration change, want to store your session data in a new location but re-implementing ISession from Pyramid looks too daunting, fear not, pyramid_pluggable_session makes this really simple.
Is this a pyramid_beaker replacement?
Yes. Although I’ve already been told that unless I implement ALL existing beaker backends that I am not doing it right, so I am hereby doing it wrong ;-).
Pull requests
Want to add a new backend? Perfect. Want to write some tests? Documentation? The whole nine yards? Please!
Clone this repo, create a new topic branch, and hack hack hack.
Push your topic branch to Github
Create a new pull request
I will review it, and if all is well pull it into this source tree!
0.0.0a2
- Add better protection against session fixation:
Upon failure to deserialize/unpack/expiration of session a new session id is generated.
Upon calling invalidate() a new session is generated with a new session id
Add more clean-up using the new clear() functionality. When a session fails to deserialize, we remove it from the backends, if a session fails to unpack we remove it from the backends, and if it has expired we also remove it from the backends.
Update the included backends memory/file/chain to add the new clear() function required by IPlugSession.
Add clear() to IPlugSession interface to allow the session to explicitly have the backend plugs remove the session data associated with a certain session id.
On _save_session we set the cookie to response that is provided to us by the callback, and not request.response which may not be the users response.
0.0.0a1
New features:
A file based session storage now exists.
A chain can now be constructed for session storage
0.0.0dev
A new ISession compliant Pyramid session provider appears.
A single backend exists, it is based on local Pyramid memory.
Metadata
Release files for pyramid_pluggable_session 0.0.0a2
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 |
|---|---|---|---|---|
| pyramid_pluggable_session-0.0.0a2.tar.gz | 11.4 kB | Without provenance | Details for pyramid_pluggable_session-0.0.0a2.tar.gz |
Release files / pyramid_pluggable_session-0.0.0a2.tar.gz
| Download URL | pyramid_pluggable_session-0.0.0a2.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
788a5cb01ba5a0b4ca48639a2941740b51974fc59c0ad6ee886b2ed1154b8b68
|
|
BLAKE2b-256 checksum How to use checksums |
005585f788f7f9d2c807a011d244bd50d4acb610e7b5cdf75dc6fb018cbad232
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyramid_pluggable_session 0.0.0a2
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.