Pre-release
This release is a pre-release and may not be stable for production use.
Read about DIP
Mechanics of Contributing
- Optional: create an issue and assign it a milestone
- Chose the issue to work, like issue #23
- In you local ctc-dip repository
git switch maingit pull origingit checkout -b i-<issue number>continuing the #23 examplegit checkout -b i-23git push --set-upstream origin i-<issue number>continuisng the #23 examplegit push --set-upstream origin i-23
- Put only code changes required for the issue on the branch; meaning, make a new branch for every issue.
- Push as often as desired using github.com as the backup of your work in progress.
- Create a PR when the disucssion changes from the issue to the solution. In other words, discussing the issue for clarification or options should be done on the issue. Discussing implementation details like a for or while loop should be done on a PR.
- When the PR clears all of its checks and has been reviewed, squash and merge it. Take this time to rewrite the commit message. Remove all unimportant messages about making fixes for linters or indentation. Make the message more comphrensive and a summary.
Metadata
Release files for ctc-dip 1.0.0rc5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ctc_dip-1.0.0rc5-py3-none-any.whl | Python 3 | none | any | Details |
Release files / ctc_dip-1.0.0rc5-py3-none-any.whl
| Download URL | ctc_dip-1.0.0rc5-py3-none-any.whl |
|---|---|
| Size | 456.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0804eb9b2dfd7afa2cee81f74b5a954e7a5820073410ac5b83e8c209da29ec6a
|
|
BLAKE2b-256 checksum How to use checksums |
a0469cf393bc5749851e397610bc1fcb9dcd3cb50c73bcad36c9744323e61729
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 8, 2026.
Transparency log