Add support for devcontainer development #132
Merged
Conversation
This file contains 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
davet2001
force-pushed
the
devcontainer
branch
from
ab28fa3
to
fc51324
Compare
davet2001
force-pushed
the
devcontainer
branch
from
fc51324
to
8a86428
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Developing in a devcontainer can be useful because specific versions of pyusb can be tested, without altering the system pyusb installation.
Developing in a devcontainer is not always the most straightforward thing to do for usb device development, because temper-usb requires access to the usb port. Specific USB devices can be mapped from the system to the devcontainer environment.