CRABpy
This library provides access to the CRAB and CAPAKEY webservices operated by the AGIV. Because connecting to these SOAP services from python can be somewhat complicated, this library makes it easier.
Build wheel or sdist
pip install hatch
hatch build
hatch build -t wheel
hatch build -t sdist
Work with pip-compile / pip-sync
full docs: https://pip-tools.readthedocs.io/en/latest/
To start, first install pip-tools:
pip install pip-tools
uv (optional)
You can also use uv and for the remainder of the readme replace pip, pip-compile or
pip-sync by uv pip, uv pip compile and uv pip sync.
uv is a very fast replacement for pip-toools. It's optional, but can save a lot of time.
pip install uv
Install requirements: pip-sync
Note, pip-sync also uninstalls everything from the virtualenv which does not belong
there according to the requirements file. This includes the project itself. You will
have to install crabpy again after pip-sync.
Since the requirements file of pip-sync is still a normal requirements file you can also
use pip install -r to install all libraries defined in it. This will not cleanup your
virtualenv and uninstall other libraries.
The compiled requirements files are made in a 3.11 environment.
pip-sync requirements-dev.txt
pip install -e .
requirements-dev.txt contains all libraries uncluding those for testing and development.
requirements.txt contains only the necessary libraries for running the library.
Update requirements: pip-compile
echo -e "\nStarting"
PIP_COMPILE_ARGS="-q --strip-extras --no-header --resolver=backtracking --no-emit-options pyproject.toml"
pip-compile $PIP_COMPILE_ARGS -o requirements.txt;
echo "requirements.txt done"
pip-compile $PIP_COMPILE_ARGS --extra dev -o requirements-dev.txt;
echo "requirements-dev.txt done"
echo "Finished"
Metadata
Release files for crabpy 1.8.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 | Actions |
|---|---|---|---|---|
| crabpy-1.8.0.tar.gz | 229.2 kB | Without provenance | Details for crabpy-1.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crabpy-1.8.0-py3-none-any.whl | Python 3 | none | any | Details for crabpy-1.8.0-py3-none-any.whl |
Total release size: 282.7 kB
Release files / crabpy-1.8.0.tar.gz
| Download URL | crabpy-1.8.0.tar.gz |
|---|---|
| Size | 229.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2aed835c2b76e52609dc920d60782d0340efeb2a48d2d9ea8cca39a23e46be53
|
|
BLAKE2b-256 checksum How to use checksums |
6613371088479d49b7521ee5494d23585bcece9af4c971f43eb5b7c4ceb4da2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.20
|
Release files / crabpy-1.8.0-py3-none-any.whl
| Download URL | crabpy-1.8.0-py3-none-any.whl |
|---|---|
| Size | 53.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a07c9aa76a559cfbf637ae20689884acb0b6eb905f59de55adce3bc2084ca742
|
|
BLAKE2b-256 checksum How to use checksums |
12710ddec3e3dfd15a1f8f6774773671e491f6cd830e6833252b8d210a9379bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.20
|
Security for crabpy 1.8.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.
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.