Skip to main content
# quay client
[![Build Status](https://travis-ci.org/tinyclues/quay_client.svg?branch=master)](https://travis-ci.org/tinyclues/quay_client) [![Coverage Status](https://coveralls.io/repos/github/tinyclues/quay_client/badge.svg?branch=delete_package)](https://coveralls.io/github/tinyclues/quay_client?branch=delete_package)

This is a client for the quay.io api

## Contributing to quay client

All contributions, bug reports, bug fixes, documentation improvements, enhancements and ideas are welcome.

### Working with the code

Now that you have an issue you want to fix, enhancement to add, or documentation to improve, you need to learn how to work with GitHub.
We use the [Github Flow](https://guides.github.com/introduction/flow/)

Finally, commit your changes to your local repository with an explanatory message, quay client uses a convention for commit message prefixes.
Here are some common prefixes along with general guidelines for when to use them:
* ENH: Enhancement, new functionality
* BUG: Bug fix
* DOC: Additions/updates to documentation
* TST: Additions/updates to tests
* BLD: Updates to the build process/scripts
* PERF: Performance improvement
* CLN: Code cleanup
* NOBUILD: special tag to skip test & build

Metadata

Release files for quay_client 3

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

Built distribution (wheel)

Table of built distributions (wheels) for quay_client 3
File Interpreter ABI Platform
quay_client-3-py2-none-any.whl Python 2 none any Details

Release files / quay_client-3-py2-none-any.whl

Download URL quay_client-3-py2-none-any.whl
Size 6.5 kB
Tags Python 2
SHA-256 checksum
How to use checksums
5d3df064b440c4f4c9e3f6995ad87c4b6cb54fbc32e6d7b0b19d76bb0c4cd4c3
BLAKE2b-256 checksum
How to use checksums
00568e16e9c1b6bfb60242648b774e08cdc5c7732e91ea8b9133d55f28890749
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for quay_client 3

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.

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