Skip to main content

Build Status Coveralls Status PyPI Status

This is the Python implementation of the Joint Editors Protocol (JEP), see http://joint-editors.org/ for more information. jep-python is providing language authors with a frontend library for IDE/editor integration and a backend library for language support.

This implementation is currently compatible with Python 3.3+.

Look at these associated projects for examples of productive use of the library:

Backend support

Implementing JEP based support for a custom language is easy. Simply derive one or more listener classes to respond to frontend messages and then run the backend with those listeners.

from jep_py.backend import Backend, FrontendListener

class Listener(FrontendListener):
    def on_completion_request(self, completion_request, context):
        # process completion request and send back response:
        completion_response = f(completion_request)
        context.send_message(completion_response)

# instantiate and start backend service with our listeners:
listener = Listener()
backend = Backend([listener])
backend.start()

Callbacks that are not needed by a certain listener do not need to be overridden in the derived class.

While the user is editing a file in a connected IDE the frontend will repeatedly send ContentSync objects to the backend. The backend implementation already processes these messages internally and provides an accumulated file view to client code. Since backend-internal message processing is done before messages are passed to subscribed listeners, you can process the latest view of a file directly inside your listener’s handler of ContentSync by accessing the context’s content_monitor filepath dictionary:

def on_content_sync(self, content_sync, context):
    # get the content monitor's view of the file that was just updated:
    file_content = context.content_monitor[content_sync.file]

    # ...

Frontend support

Similarly in an IDE frontend you again derive listener classes, this time listening to backend messages. Since the frontend initiates the connection you additionally have to create such a connection for a certain language. JEP service lookup is then used to determine the supporting backend and the frontend will start it in its own subprocess.

Here is an example shutting down the backend service upon reception of its first alive message:

import datetime
from jep_py.frontend import Frontend, BackendListener, State
from jep_py.schema import Shutdown

class MyListener(BackendListener):
    def on_backend_alive(self, context):
        context.send_message(Shutdown())


frontend = Frontend([MyListener()])
connection = frontend.get_connection('localfile.mydsl')

while connection.state is not State.Disconnected:
    connection.run(datetime.timedelta(seconds=0.1))

Metadata

Release files for jep-python 0.5.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jep-python 0.5.5
File Size Uploaded Provenance
jep-python-0.5.5.zip 36.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for jep-python 0.5.5
File Interpreter ABI Platform
jep_python-0.5.5-py3-none-any.whl Python 3 none any Details

Total release size: 149.3 kB

Release files / jep-python-0.5.5.zip

Download URL jep-python-0.5.5.zip
Size 36.2 kB
Tags Source
SHA-256 checksum
How to use checksums
a824798d4b9b2ccf1c9491defcca0983af591baaefa7b2dc49bb8ed827ac1b05
BLAKE2b-256 checksum
How to use checksums
1c30ea4790524c0c2427cfca0bc8cd40a05fe8e9bd31863d40a9de9ea58db669
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / jep_python-0.5.5-py3-none-any.whl

Download URL jep_python-0.5.5-py3-none-any.whl
Size 113.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
780303d7ce6ea5a5422280976280b24bda8fe4c7e094cefa270fc976cfa82c2e
BLAKE2b-256 checksum
How to use checksums
1bf0084e617ece4d4f4800f302b5ab2b185ba4e8a86e428f0ab8a0276f749822
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for jep-python 0.5.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.

Release history Release notifications | RSS feed

This release

0.5.5 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page