stdio_socket
Share the stdio of a process on a unix socket.
This package has 3 entrypoints:
- stdio-expose: launch a process and share its stdio on a unix socket
- console: connect to a socket to get a console into the above process
- pptty: wrap a process in a psuedo tty (used by stdio-expose)
| Source | https://github.com/epics-containers/stdio-socket |
|---|---|
| PyPI | pip install stdio-socket |
| Releases | https://github.com/epics-containers/stdio-socket/releases |
Server CLI
Usage: stdio-expose [OPTIONS] COMMAND
Expose the stdio of a process on a socket at unix:///tmp/stdio.sock.
This allows a local process to connect to stdio of the running process.
Use Ctrl+C to disconnect from the socket.
The following command will connect to the socket and provide interactive
access to the process: socat UNIX-CONNECT:/tmp/stdio.sock -,raw,echo=0
or use the built in client: console
╭─ Arguments ──────────────────────────────────────────────────────────────╮
│ * command TEXT Command to run and expose stdio [default: None] │
│ [required] │
╰──────────────────────────────────────────────────────────────────────────╯
╭─ Options ────────────────────────────────────────────────────────────────╮
│ --socket PATH The filepath to the socket to use │
│ [default: /tmp/stdio.sock] │
│ --version print the version number and exit │
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────╯
Client CLI
Usage: console [OPTIONS]
Connect to a socket and pass stdio to/from that socket
╭─ Options ────────────────────────────────────────────────────────────────╮
│ --socket PATH The filepath to the socket to use │
│ [default: /tmp/stdio.sock] │
│ --version print the version number and exit │
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────╯
Pseudo TTY CLI
Usage: pptty [OPTIONS] COMMAND
Use the pty library to wrap a process in psuedo tty
╭─ Arguments ──────────────────────────────────────────────────────────────╮
│ * command TEXT Command to run and expose stdio [default: None] │
│ [required] │
╰──────────────────────────────────────────────────────────────────────────╯
╭─ Options ────────────────────────────────────────────────────────────────╮
│ --help Show this message and exit. │
╰──────────────────────────────────────────────────────────────────────────╯
Metadata
Release files for stdio-socket 1.4.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 | Provenance | Actions |
|---|---|---|---|---|
| stdio_socket-1.4.1.tar.gz | 75.9 kB | Without provenance | Details for stdio_socket-1.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stdio_socket-1.4.1-py3-none-any.whl | Python 3 | none | any | Details for stdio_socket-1.4.1-py3-none-any.whl |
Total release size: 92.4 kB
Release files / stdio_socket-1.4.1.tar.gz
| Download URL | stdio_socket-1.4.1.tar.gz |
|---|---|
| Size | 75.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
700c0c10e0165052b846ca3972dfcfefb38333411ead71e410c980a893bf5ae5
|
|
BLAKE2b-256 checksum How to use checksums |
3a68edb212723578a4227aa3ca4a3db61e385e590461ec7071ecd32c46e568e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / stdio_socket-1.4.1-py3-none-any.whl
| Download URL | stdio_socket-1.4.1-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8797c5e5884b1bbfddf63c655a1e323549b6c3ffde0f4ccd374b73288e9ffcf
|
|
BLAKE2b-256 checksum How to use checksums |
288a00b24992a38a987912a460e18958d1637369aa8b32b75badedd447aa8431
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for stdio-socket 1.4.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.