Skip to main content

barking

Release Build status codecov Commit activity License

This is a template repository for Python projects that use uv for their dependency management.

Getting started with your project

1. Create a New Repository

First, create a repository on GitHub with the same name as this project, and then run the following commands:

git init -b main
git add .
git commit -m "init commit"
git remote add origin git@github.com:bryanhann/barking.git
git push -u origin main

2. Set Up Your Development Environment

Then, install the environment and the pre-commit hooks with

make install

This will also generate your uv.lock file

3. Run the pre-commit hooks

Initially, the CI/CD pipeline might be failing due to formatting issues. To resolve those run:

uv run pre-commit run -a

4. Commit the changes

Lastly, commit the changes made by the two steps above to your repository.

git add .
git commit -m 'Fix formatting issues'
git push origin main

You are now ready to start development on your project! The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.

To finalize the set-up for publishing to PyPI, see here. For activating the automatic documentation with MkDocs, see here. To enable the code coverage reports, see here.

Releasing a new version


Repository initiated with fpgmaas/cookiecutter-uv.

Metadata

Release files for barking 0.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 barking 0.0.1
File Size Uploaded Provenance Actions
barking-0.0.1.tar.gz 3.9 kB Without provenance Details for barking-0.0.1.tar.gz

Built distribution (wheel)

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

Total release size: 7.4 kB

Release files / barking-0.0.1.tar.gz

Download URL barking-0.0.1.tar.gz
Size 3.9 kB
Tags Source
SHA-256 checksum
How to use checksums
1dd78e4eadd6739e5ecc61dc0a4b78b2242ab029e5b891e06d32dacfb5042bac
BLAKE2b-256 checksum
How to use checksums
71ea70fe447f65be22b9596f0b08191a085f14c91ee90c46501cc0d3c49b8cea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.4.20

Release files / barking-0.0.1-py3-none-any.whl

Download URL barking-0.0.1-py3-none-any.whl
Size 3.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
43b592b316dcb763f7b2e27697f025e11f35220a537a1a31eedcab31799966be
BLAKE2b-256 checksum
How to use checksums
dd88ddf8461bfe21bfa39369f03e242588f1d61ed10ce277fc86e0ca75184140
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.4.20

Security for barking 0.0.1

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.

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files No provenance

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