PyJinx Installer
Temporary project names: this installer package uses the PyJinx name. The global project creator is
pyjinx. Generated projects use the project-local framework executableloom, for both PyJinx and Veyra.
The global installer creates a new application from the private
pyjinx/starter repository. It removes the
starter's development checkout and local framework copy, then leaves the
application configured to install the pyjinx framework distribution from
PyPI.
Installation
Install from a checked-out copy with uv:
uv tool install .
For local development, run the package through the checked-out project:
uv run pyjinx --help
Create an application
pyjinx new hello-world
cd hello-world
uv sync
The command refuses to populate a non-empty destination. Project names must be
one safe directory name made from letters, numbers, -, and _, beginning with
a letter.
For local starter development or tests, pass a directory explicitly:
pyjinx new hello-world --starter-path /path/to/starter
The PYJINX_STARTER_REPOSITORY environment variable can select a starter
repository or local directory. If --starter-path is omitted and the current
directory contains a starter checkout (app/ and bootstrap/), that directory
is used. Otherwise the private pyjinx/starter repository is cloned.
Metadata
Release files for pyjinx-installer 0.1.5
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 |
|---|---|---|---|---|
| pyjinx_installer-0.1.5.tar.gz | 7.8 kB | Without provenance | Details for pyjinx_installer-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyjinx_installer-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for pyjinx_installer-0.1.5-py3-none-any.whl |
Total release size: 15.3 kB
Release files / pyjinx_installer-0.1.5.tar.gz
| Download URL | pyjinx_installer-0.1.5.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a40692689cc94d591f78df07d5f966bd13a47b6a68c3f18a2c1d2448136c97d
|
|
BLAKE2b-256 checksum How to use checksums |
cda32844c901650386cad47d5fa6bff54c9c8a396ca42c6784c14f06abae993a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.24 {"installer":{"name":"uv","version":"0.9.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pyjinx_installer-0.1.5-py3-none-any.whl
| Download URL | pyjinx_installer-0.1.5-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8667c3f8e64b3988feeafe7e660ecc979452d00ae5da51f71d7daaa7fa7a85cb
|
|
BLAKE2b-256 checksum How to use checksums |
308ca93b73d0abcf48ea1351b9f35f38d2da4ce862e0846d7f4301ee2f1b61d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.24 {"installer":{"name":"uv","version":"0.9.24","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pyjinx-installer 0.1.5
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.