Stubs for Desbordante
Main repository is available at https://github.com/Mstrutov/Desbordante
Stubs are generated by https://github.com/sizmailov/pybind11-stubgen
Setup and Usage
This repository includes several helpful Makefile scripts for managing stubs and code formatting. Below are the available commands:
1. Install dependencies
To install all necessary dependencies and set up pre-commit hooks, run:
make init
2. Generate stubs
To generate the stubs for the desbordante library:
make stubs
This will run pybind11-stubgen to generate stubs, remove the old desbordante-stubs folder if it exists, and move the newly generated stubs to desbordante-stubs. The code will also be formatted after generation.
3. Run linters and formatters
To check the code with linters and formatters:
make lint
This command runs ruff to ensure the code is properly formatted and follows style guidelines.
4. Format the code
To automatically format the code:
make format
This command will run ruff and black to reformat the code in the desbordante-stubs folder.
1 maintainer
Metadata
1 maintainer
Release files for desbordante-stubs 0.3.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 | |
|---|---|---|---|---|
| desbordante_stubs-0.3.0.tar.gz | 11.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| desbordante_stubs-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.3 kB
Release files / desbordante_stubs-0.3.0.tar.gz
| Download URL | desbordante_stubs-0.3.0.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e390824b7e97436b6aea31533fb91682f6a87d543da830c8063f7dbc59345e75
|
|
BLAKE2b-256 checksum How to use checksums |
115519c55f246327de94369adb179de0d00265ceac1b63cbb18de219f854c5fc
|
| 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 Mar 27, 2025.
Transparency logRelease files / desbordante_stubs-0.3.0-py3-none-any.whl
| Download URL | desbordante_stubs-0.3.0-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecb05d15985ab76dd197c56cb9063c2d45f309e0a13d26ff70eeff943d6ba524
|
|
BLAKE2b-256 checksum How to use checksums |
1a5a6bafd458b3e50202902be683838ae98ea314dcc764d0ef4d7a540d0bff83
|
| 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 Mar 27, 2025.
Transparency logSecurity for desbordante-stubs 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for desbordante_stubs-0.3.0.tar.gz
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 Mar 27, 2025.
Transparency logA 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.
