This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Database component
Install all dependencies and extras with uv sync --all-extras.
Creating migrations
To create migrations modify database models first. Make sure to have the models imported in env.py by adding them into models.all module.
After models have been modified, run:
uv run alembic revision --autogenerate -m "Migration description" --rev-id="migration_id"
This command will generate a new migration file based on the changes made to the models.
Check the created migration file and make sure it is correct and remove Alembic autogenerated comments from the top and bottom of the functions. Remember to commit it in the repository.
Running migrations
To run migrations in development, in root of the project run:
docker-compose run --rm ansible
or make infra-full.
If you want to skip database initialization, just run make migrations.
In development, you can also run migrations manually by running:
uv run alembic upgrade head
But this does not run migrations to test databases.
Metadata
Release files for pinta-db 0.1.0
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 | |
|---|---|---|---|---|
| pinta_db-0.1.0.tar.gz | 4.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pinta_db-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / pinta_db-0.1.0.tar.gz
| Download URL | pinta_db-0.1.0.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01839991df7e40d2dfe3982a1559e15c76f8ccad29b8b9b4b7c7996746a8f4a7
|
|
BLAKE2b-256 checksum How to use checksums |
efca09302c9ddbe84dc9021110c5c65afe17b788219a8259c0d0b38739aeaf5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.1 {"installer":{"name":"uv","version":"0.11.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pinta_db-0.1.0-py3-none-any.whl
| Download URL | pinta_db-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ccd94d02fa3c7f5c6f2682d2ff9c5fd264ba7b45bcd6c49fdb95346044bb7dd7
|
|
BLAKE2b-256 checksum How to use checksums |
7467746c3a0f77b79b791beb860ad0ae0252a64a028d35321ff4d23cce800861
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.1 {"installer":{"name":"uv","version":"0.11.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pinta-db 0.1.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.