delgado
Listen for commands over a unix socket and execute them in the terminal.
It solves the problem of text editors not wanting to bundle a real terminal emulator.
delgado requires valid JSON objects to be fired over a predetermined UDS (Unix Domain Socket). Delgado has to know about what commands is authorized to execute before running them, preventing arbitrary commands to be run).
A very simple listener allowed to run ls only would look like this:
$ delgado run --allowed ls
On a different terminal, sending the JSON to that socket could be something like:
$ echo '{"ls": ["/tmp/foo"]}' | nc -U /tmp/delgado.sock
The echo pipes over to nc (BSD Netcat) that in turn sends the information to the socket. With the default logging levels, the output would then look like this:
$ delgado run --allowed ls --> Running command: [u'ls']
plugins
delgado was built with some modularity in mind, by default you get the py.test plugin which will run the server and listen for py.test commands only.
The plugins use setuptools entry points. If you want a new plugin to be available, this is what it should have on its setup.py file:
setup(
...
entry_points = dict(
delgado_handlers = [
'my_command = my_package.my_module:MyClass',
],
),
The MyClass should be a class that accepts sys.argv as its argument, delgado will pass that in at instantiation and call a parse_args method.
This is how the py.test plugin looks like for example:
class Pytest(object):
help_menu = 'A handler for running py.test commands'
_help = """
Run a base socket listener that allows py.test commands.
--socket-location The location for the socket (defaults
to /tmp/pytest.sock)
"""
def __init__(self, argv):
self.argv = argv
def parse_args(self):
...
Metadata
Release files for delgado 0.0.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 |
|---|---|---|---|---|
| delgado-0.0.1.tar.gz | 14.1 kB | Without provenance | Details for delgado-0.0.1.tar.gz |
Release files / delgado-0.0.1.tar.gz
| Download URL | delgado-0.0.1.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41076c075cf55e398b7d83c603975b1bd41ef4ad77b5c9e0a13a3c280c3d5ce1
|
|
BLAKE2b-256 checksum How to use checksums |
9b13384976b922791294b1c683b8b47cfe6f1206b9f97668287b16f24a0dce71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for delgado 0.0.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.