Skip to main content

PyPI Build Status Coverage Status

A (very) simple file versioning system

Version: 1.7.0

Detailed documentation on the available commands can be found on the quicksave wiki

Getting started:

The first thing you’ll need to do is create a new database where quicksave can store its data:

$ quicksave init <path>

That will setup the new database so it’s ready to use.

After that, you’re good to go. You can register new files so they’re tracked by quicksave, save new states of registered files, and revert to previously saved states. There are several other commands which modify the database itself, but I’m only covering those three listed commands in this guide (and none of their various options). For detailed documentation on all of the available commands, check out the wiki page.

To track (AKA register) a new file in quicksave use:

$ quicksave register <filepath>

Which will copy the initial state of the file, and provide the names of the file and state keys you’ll need use this file. For a brief description of file and state keys, see this note on the wiki.

To then save a new state of the file, use the save command:

$ quicksave save <filepath>

Quicksave will use the the absolute path and the base file name derived from filepath to automatically decide which file key to use.

Lastly, to get the file back into a previously saved state, use the revert command:

$ quicksave revert <filepath> <state>

Again, quicksave will attempt to determine which file key to use based on the absolute path and the file name. Quicksave will lookup the provided state key and revert the file.

Metadata

Release files for quicksave 1.7.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 quicksave 1.7.0
File Size Uploaded Provenance
quicksave-1.7.0.tar.gz 20.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for quicksave 1.7.0
File Interpreter ABI Platform
quicksave-1.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 49.6 kB

Release files / quicksave-1.7.0.tar.gz

Download URL quicksave-1.7.0.tar.gz
Size 20.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b2dc2c9b5c45dd450cb60bdd6dfbc150d69d57ec9d408a545e8f2c7f78b4e9e3
BLAKE2b-256 checksum
How to use checksums
ac8587fdb370ced8ccb48f321875d663f01384bc0a6ed2bf04f85b9322b8b253
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / quicksave-1.7.0-py3-none-any.whl

Download URL quicksave-1.7.0-py3-none-any.whl
Size 29.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
24b867bc850c36f40c0e09c6ebcef8ad301a57c61fcf0849e7e3529990ccbe56
BLAKE2b-256 checksum
How to use checksums
ea63576b3e950fb061cb02d726d79b02ee2494da90e6f96fbffd0acc74995301
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for quicksave 1.7.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page