Hyperfast Python Template
Streamlining Python Project Development with a Comprehensive Toolset for Quality, Efficiency, and Maintainability
- Documentation: https://hyperfast-python.entelecheia.ai
- GitHub: https://github.com/entelecheia/hyperfast-python-template
- PyPI: https://pypi.org/project/hyperfast-python-template
The Hyperfast Python Template is a powerful and comprehensive solution designed to accelerate the development and maintenance of high-quality Python projects. By incorporating industry best practices and automating key aspects such as dependency management, releases, code formatting, testing, and documentation, this template streamlines the entire development process. It ensures code quality through continuous integration, coverage reporting, linting, and static type-checking while providing seamless support for Conventional Commits and Semantic Versioning. With the Hyperfast Python Template, developers can efficiently create and manage Python projects, focusing on their core functionality while enjoying a robust, well-organized, and maintainable codebase.
Quickstart
There are two ways to use this project:
- Use [Copier] to create a project to your local machine directly
- Inject [Hyperfast Python Template] into an existing project
I. Use Copier
- Install Copier
pipx install copier
- Run
copier copy --trust gh:entelecheia/hyperfast-python-template path/to/destination
- Do your work
II. Inject the template
- Install Copier
pipx install copier
- From the root of your project, run
copier copy --trust gh:entelecheia/hyperfast-python-template .
- Do your work
Managing Actions Secrets and Variables in Your Project
When using the HyFI-Template for your project, there are several GitHub Actions secrets and variables that you need to add to ensure proper functioning of the release action and optional JupyterBook deployment.
Adding PYPI_API_TOKEN and TEST_PYPI_API_TOKEN
To automate the release process of your project to PyPI, you need to provide two tokens: PYPI_API_TOKEN and TEST_PYPI_API_TOKEN. These tokens will be used by the GitHub Actions workflow to authenticate with PyPI and TestPyPI, respectively.
- Generate an API token for your PyPI account by following the instructions in the official PyPI documentation.
- Generate an API token for your TestPyPI account by following the instructions in the official TestPyPI documentation.
- In your GitHub repository, go to the "Settings" tab and click on "Secrets" in the left sidebar.
- Click the "New repository secret" button.
- Add the
PYPI_API_TOKENsecret with the value set to the token generated for your PyPI account. - Add the
TEST_PYPI_API_TOKENsecret with the value set to the token generated for your TestPyPI account.
By providing these tokens, your project's release action will have the necessary permissions to publish your package to PyPI and TestPyPI.
Optionally Adding CNAME for JupyterBook Deployment
If you plan to deploy the JupyterBook documentation to a custom domain, you'll need to add a CNAME variable to your GitHub repository.
- In your GitHub repository, go to the "Settings" tab and click on "Pages" in the left sidebar.
- Follow the instructions to configure your custom domain.
- In your GitHub repository, go to the "Settings" tab and click on "Repository Variables" in the left sidebar.
- Click the "New repository variable" button.
- Add a new variable with the key
CNAMEand set the value to your custom domain (e.g.,your-custom-domain.com).
By adding the CNAME variable, the GitHub Pages action in your deploy-docs.yaml workflow will properly configure the deployment to use your custom domain.
With the CNAME repository variable properly configured, your project will be set up to handle JupyterBook deployment to your custom domain effectively.
Changelog
See the CHANGELOG for more information.
Contributing
Contributions are welcome! Please see the contributing guidelines for more information.
License
This project is released under the MIT License.
1 maintainer
Metadata
1 maintainer
Release files for hyperfast-python-template 0.16.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hyperfast_python_template-0.16.3.tar.gz | 5.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hyperfast_python_template-0.16.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.4 kB
Release files / hyperfast_python_template-0.16.3.tar.gz
| Download URL | hyperfast_python_template-0.16.3.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7a13a24911421ccda8f5247b31aa9b17dff49acc42723d09a7322f7220ee348
|
|
BLAKE2b-256 checksum How to use checksums |
8e471a40bd77cfdf8f23dcb1c4475ca2bd4ec3ef2fd0bc045c1176c728c8538c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Nov 14, 2024.
Transparency logRelease files / hyperfast_python_template-0.16.3-py3-none-any.whl
| Download URL | hyperfast_python_template-0.16.3-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1cdc6ece2d124098fb12c3f65acb16f75df9060cf6dea04f67205e22470955f
|
|
BLAKE2b-256 checksum How to use checksums |
1b9ab38f6c5dc4e9339bf2d7eb749873c6e4d7f91973eb4fe223e645f25bafc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
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 Nov 14, 2024.
Transparency log
