Skip to content

Fix entry points for 3rd party interfaces #389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 11, 2018

Conversation

christiansandberg
Copy link
Collaborator

Fixes backwards incompatible change introduced in 2.2.0. Updated documentation to new entry point.

@christiansandberg christiansandberg added this to the 2.3 Release milestone Aug 11, 2018
@codecov
Copy link

codecov bot commented Aug 11, 2018

Codecov Report

Merging #389 into develop will increase coverage by <.01%.
The diff coverage is 60%.

@@             Coverage Diff             @@
##           develop     #389      +/-   ##
===========================================
+ Coverage    59.34%   59.34%   +<.01%     
===========================================
  Files           55       55              
  Lines         4243     4248       +5     
===========================================
+ Hits          2518     2521       +3     
- Misses        1725     1727       +2

@christiansandberg christiansandberg changed the title Fix entry points for 3rd party modules Fix entry points for 3rd party interfaces Aug 11, 2018
@@ -25,15 +25,15 @@ The available interfaces are:
interfaces/virtual

Additional interfaces can be added via a plugin interface. An external package
can register a new interface by using the ``python_can.interface`` entry point.
can register a new interface by using the ``can.interface`` entry point in setup.py.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe write: "by using the can.interface entry point in its setup.py"

@@ -28,4 +28,10 @@
for interface in iter_entry_points('can.interface')
})

# Old entry point name. May be removed in 3.0.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe, we should print a warning then, urging people to use the newer one.

@@ -25,15 +25,15 @@ The available interfaces are:
interfaces/virtual

Additional interfaces can be added via a plugin interface. An external package
can register a new interface by using the ``python_can.interface`` entry point.
can register a new interface by using the ``can.interface`` entry point in setup.py.

The format of the entry point is ``interface_name=module:classname`` where
``classname`` is a :class:`can.BusABC` concrete implementation.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe: is a concrete :class:can.BusABC implementation

@felixdivo
Copy link
Collaborator

Looks good to me!

@christiansandberg christiansandberg merged commit 090f380 into hardbyte:develop Aug 11, 2018
@christiansandberg christiansandberg deleted the plugins-fix branch August 11, 2018 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants