bijux-rag
bijux-rag is the continuation of the published bijux-rag distribution on
PyPI. Each release keeps the legacy distribution, import, and command surfaces
available while installing bijux-canon-ingest at the same version.
Its package handbook lives at https://bijux.io/bijux-canon/compat-packages/bijux-rag/.
Migration note
- new installs should use
pip install bijux-canon-ingest - existing automation can stay on
bijux-ragwhile you update imports and commands - canonical migration guide: https://bijux.io/bijux-canon/compat-packages/migration-guidance/
- retired repository target: https://github.com/bijux/bijux-rag
Publication status
- published continuation of the legacy
bijux-ragdistribution - each release depends on
bijux-canon-ingest==<same version> - intended for existing environments that still rely on the legacy name
Canonical package
- distribution:
bijux-canon-ingest - Python import:
bijux_canon_ingest - command:
bijux-canon-ingest
What this compatibility package preserves
- the legacy distribution name
bijux-rag - the legacy Python import surface
bijux_rag - the legacy command name
bijux-rag
Read this next
Use bijux-canon-ingest directly:
- package directory: https://github.com/bijux/bijux-canon/tree/main/packages/bijux-canon-ingest
- legacy package handbook: https://bijux.io/bijux-canon/compat-packages/bijux-rag/
- package docs: https://bijux.io/bijux-canon/bijux-canon-ingest/
- migration guide: https://bijux.io/bijux-canon/compat-packages/migration-guidance/
- changelog: https://github.com/bijux/bijux-canon/blob/main/packages/compat-bijux-rag/CHANGELOG.md
Primary entrypoint
- console script:
bijux-rag
Package contents
- https://github.com/bijux/bijux-canon/blob/main/packages/compat-bijux-rag/pyproject.toml
- https://github.com/bijux/bijux-canon/blob/main/packages/compat-bijux-rag/hatch_build.py
- https://github.com/bijux/bijux-canon/blob/main/packages/compat-bijux-rag/overview.md
- https://github.com/bijux/bijux-canon/blob/main/packages/compat-bijux-rag/CHANGELOG.md
Metadata
Release files for bijux-rag 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 | Actions |
|---|---|---|---|---|
| bijux_rag-0.3.0.tar.gz | 9.6 kB | Without provenance | Details for bijux_rag-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bijux_rag-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for bijux_rag-0.3.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / bijux_rag-0.3.0.tar.gz
| Download URL | bijux_rag-0.3.0.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8dc76f03c515506c04cca7f6f0150dd6e605b2a7e84210ffd14b835f1697bb3
|
|
BLAKE2b-256 checksum How to use checksums |
4b19d8a42802f963093a67ce0ffc7730da975820f673476396297c0c63863e6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / bijux_rag-0.3.0-py3-none-any.whl
| Download URL | bijux_rag-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
676120f3814e8208c6a9c33ac30125b5ac30ae300a66e14c1dee4288a89f746f
|
|
BLAKE2b-256 checksum How to use checksums |
911180ae6246a9441aaeec968017feace13085cdc049e9d661e4ced9936a0a36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for bijux-rag 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.
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.