Skip to main content

logo

pirogue

A tool to automatically create views and triggers on PostgreSQL databases

It supports both psycopg 2 and 3. One or the other is required.

Read the docs: https://opengisch.github.io/pirogue

Metadata

Release files for pirogue 3.0.1

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

Source distribution (sdist)

Source distribution for pirogue 3.0.1
File Size Uploaded
pirogue-3.0.1.tar.gz 1.0 MB Details

Built distribution (wheel)

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

Total release size: 1.0 MB

Release files / pirogue-3.0.1.tar.gz

Download URL pirogue-3.0.1.tar.gz
Size 1.0 MB
Tags Source
SHA-256 checksum
How to use checksums
26f42b465bbadc4238348da1735a5673fc1166056a523919aad6d216d049a7e5
BLAKE2b-256 checksum
How to use checksums
15c3f7880b81cda5b10a341218734fe278b3ecb797f0a08599abb44c9a035e4c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 9, 2025.

Transparency log

Release files / pirogue-3.0.1-py3-none-any.whl

Download URL pirogue-3.0.1-py3-none-any.whl
Size 20.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e95fd175d927e8b4709d5b5e59494d3e0eb4dd77ebe321663e2300acba1cada5
BLAKE2b-256 checksum
How to use checksums
e36da20d8586d259a72eeccb6fe5418ab8a5e89fffab2e1abee914c94266f25d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 9, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

3.0.1 This release

2 release files

3.0.0

2 release files

2.2.0

2 release files

2.1.0

2 release files

2.0.1

2 release files

1.4.2

2 release files

1.4.1

2 release files

1.4.0

2 release files

1.3.4

2 release files

1.3.3

1 release file

1.3.0

1 release file

1.2.5

2 release files

1.2.4

2 release files

1.2.3

2 release files

1.2.2

2 release files

1.2.1

2 release files

1.2.0

2 release files

1.1.0

2 release files

1.0.4

2 release files

1.0.3

1 release file

1.0.1

1 release file

1.0.0

1 release file

0.5.6

1 release file

0.5.5

1 release file

0.5.4

1 release file

0.5.3

1 release file

0.5.1

1 release file

0.4.9

1 release file

0.4.8

1 release file

0.4.7

1 release file

0.4.5

1 release file

0.4.4

1 release file

0.4.3

1 release file

0.4.2

1 release file

0.4.1

1 release file

0.4

1 release file

0.3

1 release file

0.2

1 release file

0.1

1 release file

0.0.0

1 release file

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