Add python-can-hub to the plugin interface list - #2087
Open
jamofer wants to merge 1 commit into
Open
Conversation
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
python-can-hubto the list of plugin interfaces and as an optional dependency.python-can-hubis a native backend for can-hub, a hub that lets devices behind NAT export their SocketCAN interfaces over the network. The plugin speaks the binary protocol directly over QUIC, TLS, plain TCP or a unix socket, so no bridge process is needed:Published on PyPI as
python-can-huband registered under thecan.interfaceentry point ascanhub.One thing worth flagging: the package is AGPL-3.0. Declaring it as an optional dependency does not affect python-can's own licensing, but if you would rather not list an AGPL package under
[project.optional-dependencies], I am happy to drop that hunk and keep the documentation entry only.Related Issues / Pull Requests
None
Type of Change
Checklist