A previous release had provenance metadata, but this release does not. View details.
This release is a pre-release and may not be stable for production use.
GLLM Docproc
Description
A library for orchestrating the processing of document. Typically in a Gen AI applications (but not limited to just Gen AI).
Installation
Prerequisites
Mandatory:
- Python 3.11+ — Install here
- pip — Install here
- uv — Install here
- gcloud CLI (for authentication) — Install here, then log in using:
gcloud auth login
Install from Artifact Registry
This requires authentication via the gcloud CLI.
- Export token
export GCLOUD_ACCESS_TOKEN="$(gcloud auth print-access-token)"
- Configure the index in your
pyproject.tom;
[[tool.uv.index]]
name = "gen-ai-internal"
url = "https://oauth2accesstoken:${GCLOUD_ACCESS_TOKEN}@glsdk.gdplabs.id/gen-ai-internal/simple/"
- Add the dependency
uv add gllm-docproc
Local Development Setup
Prerequisites
-
Python 3.11+ — Install here
-
pip — Install here
-
uv — Install here
-
gcloud CLI — Install here, then log in using:
gcloud auth login
-
Git — Install here
-
Access to the GDP Labs SDK GitHub repository
1. Clone Repository
git clone git@github.com:GDP-ADMIN/gl-sdk.git
cd gl-sdk/libs/gllm-docproc
2. Setup Authentication
Set the following environment variables to authenticate with internal package indexes:
export UV_INDEX_GEN_AI_INTERNAL_USERNAME=oauth2accesstoken
export UV_INDEX_GEN_AI_INTERNAL_PASSWORD="$(gcloud auth print-access-token)"
export UV_INDEX_GEN_AI_USERNAME=oauth2accesstoken
export UV_INDEX_GEN_AI_PASSWORD="$(gcloud auth print-access-token)"
3. Quick Setup
Run:
make setup
4. Activate Virtual Environment
source .venv/bin/activate
Local Development Utilities
The following Makefile commands are available for quick operations:
Install uv
make install-uv
Install Pre-Commit
make install-pre-commit
Install Dependencies
make install
Update Dependencies
make update
Run Tests
make test
Contributing
Please refer to the Python Style Guide for information about code style, documentation standards, and SCA requirements.
Metadata
Release files for gllm-docproc-binary 0.13.25b19
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gllm_docproc_binary-0.13.25b19-cp313-cp313-manylinux_2_28_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.28+ x86-64 | Details for gllm_docproc_binary-0.13.25b19-cp313-cp313-manylinux_2_28_x86_64.whl |
| gllm_docproc_binary-0.13.25b19-cp312-cp312-manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64 | Details for gllm_docproc_binary-0.13.25b19-cp312-cp312-manylinux_2_28_x86_64.whl |
Total release size: 11.8 MB
Release files / gllm_docproc_binary-0.13.25b19-cp313-cp313-manylinux_2_28_x86_64.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | gllm_docproc_binary-0.13.25b19-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.9 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
aa2139a5169209560b9c755a441468d2972551fdf8f4551c0b340370fd98ed00
|
|
BLAKE2b-256 checksum How to use checksums |
ad81006b3db3ad34617a95dc519c4415fed0918201dee22263c05a41368d45f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"AlmaLinux","version":"8.10","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / gllm_docproc_binary-0.13.25b19-cp312-cp312-manylinux_2_28_x86_64.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | gllm_docproc_binary-0.13.25b19-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 5.9 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
d53498d89f47b7047992972d408c47473f013991bc4f1d257f3ffceab9d5153c
|
|
BLAKE2b-256 checksum How to use checksums |
49dd137904c383b056cbdaa666867e15ab72d13ce37950afbc88921ed27964aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"AlmaLinux","version":"8.10","id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for gllm-docproc-binary 0.13.25b19
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.13.25b18 8 files Partial provenance
- Added 0.13.25b19 2 files Without provenance
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.