a750-control
Python bindings for the a750_control robotic arm library.
Development install
Create and activate a Python 3.12 virtual environment:
cd /home/alex/a750_control
python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -U pip
Install the package in editable mode:
pip install -e . -Cbuild-dir=build/python -Ccmake.args="-DCMAKE_EXPORT_COMPILE_COMMANDS=ON"
Build a PyPI wheel
Linux binary wheels uploaded to PyPI must use a portable platform tag such as
manylinux, not the local linux_x86_64 tag produced by python -m build.
Use cibuildwheel to build inside a manylinux Docker container and repair the
wheel with auditwheel.
Install release tooling:
python -m pip install -U build cibuildwheel twine
Build the Python 3.12 manylinux wheel:
CIBW_BUILD=cp312-manylinux_x86_64 python -m cibuildwheel --platform linux --output-dir wheelhouse
The output should look like:
wheelhouse/a750_control-0.1.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
pyproject.toml passes -DBUILD_TESTING=OFF to CMake for package builds so
dependency test targets are not built as part of the wheel.
Check and upload
Check the built wheel:
python -m twine check wheelhouse/*.whl
Upload to TestPyPI first:
python -m twine upload --repository testpypi wheelhouse/*.whl
Install from TestPyPI in a clean environment:
python -m pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ a750-control
python -c "import a750_control; print(a750_control.Robot)"
If the TestPyPI package works, upload to PyPI:
python -m twine upload wheelhouse/*.whl
For authentication, use a PyPI API token with username __token__, or configure
PyPI Trusted Publishing for the GitHub repository.
Metadata
Release files for a750-control 0.1.1
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 | Actions Reset |
|---|---|---|---|---|
| a750_control-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details for a750_control-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
Release files / a750_control-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | a750_control-0.1.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 23.0 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1bba463c7258ab05cf652b26771f4f0715d795f6f67c9697448c0028301c0f4a
|
|
BLAKE2b-256 checksum How to use checksums |
c077d46aa63e746dce7773b47c67533b4ef9c25aa8160d71d5e1a278a0ee8be6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for a750-control 0.1.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.