scitex-sdk
One project for the SciTeX app contract + UI shell — so the two are named, versioned, and released as a single unit.
scitex_sdk.app -> the app contract (from scitex-app)
scitex_sdk.ui -> the UI shell (from scitex-ui)
Step 1: thin facade
scitex_sdk.app re-exports scitex_app's documented public surface by
identity (the same objects), and scitex_sdk.ui re-exports scitex_ui's.
That makes a consumer's import rewrite mechanical and behavior-neutral:
# before
from scitex_app import get_files
# after
from scitex_sdk.app import get_files # identical object
tests/test_facade_identity.py asserts every re-export is the same object
as the original — a copy or reimplementation fails the suite.
Roadmap
- Facade (this) — re-export, identity tests, release. Consumers can start rewriting imports against it.
- Gradual implementation move — code moves from
scitex_app/scitex_uiintoscitex_sdk.app/scitex_sdk.ui; the original distributions stay as thin compat shims until every consumer has migrated. - Shim removal — only after all consumers (hub, figrecipe, writer,
scholar, cards, agent-container GUI) are on
scitex_sdk.
The static/TS/CSS assets live in scitex_ui today (Django's
AppDirectoriesFinder resolves them by the scitex_ui app label); they move
with the implementation step, not the facade.
App Creator wizard
scitex_sdk.creator is the first implementation that lives in the SDK
rather than behind the facade (new code, not moved code): the appmaker
scaffolding wizard as a web UI, served by the SDK for both standalone
use and host mounting.
scitex-sdk gui serve # wizard at http://127.0.0.1:31301/ (blocking)
scitex-sdk gui open # auto-serve (if needed) + open a browser
scitex-sdk gui status # running / not-running (+ --json)
scitex-sdk gui stop --yes
The wizard covers: new app from starter (label / description /
starter card: data entry, dashboard, log viewer, blank), inline
validation feedback, api/validate-app on an existing app dir, and
publish / dev-install hooks against a SciTeX Cloud server. The engine
(scaffold, validate, publish, dev-install) is still imported from
scitex-app's appmaker and consolidates here gradually.
Hosts mount the same Django app generically:
path("create-app/", include("scitex_sdk.creator.urls"))
(manifest.json slug create-app, port 31301 — the first 3130X
overflow slot; 3129X is full per scitex-dev's reserved-port scheme.)
Metadata
Release files for scitex-sdk 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| scitex_sdk-0.2.1.tar.gz | 19.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scitex_sdk-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.5 kB
Release files / scitex_sdk-0.2.1.tar.gz
| Download URL | scitex_sdk-0.2.1.tar.gz |
|---|---|
| Size | 19.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
800dc4e52aef2e6c70e7e56bb468027c85f586d6f5d3ad40d4eec8b05dd2a563
|
|
BLAKE2b-256 checksum How to use checksums |
9e7fb1387d1f64f6a19ec46b3adcfb830da3f812c3dc3b6b0c6a6c5c6272a990
|
| 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 Sep 28, 2026.
Transparency logRelease files / scitex_sdk-0.2.1-py3-none-any.whl
| Download URL | scitex_sdk-0.2.1-py3-none-any.whl |
|---|---|
| Size | 19.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3293b780ef07a810de0718e26b8c878236aebf97ed89125cace54ade7352c128
|
|
BLAKE2b-256 checksum How to use checksums |
1f518024ee6e185e3e741cd2bc8eeb60d5abb85c7ba9b17105f045cf4586356d
|
| 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 Sep 28, 2026.
Transparency log