-
-
Notifications
You must be signed in to change notification settings - Fork 242
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
525: Allow extensions to use the format pyvisa_name r=MatthieuDartiailh a=MatthieuDartiailh This change is motivated pyvisa/pyvisa-py#239 but only implement the simplest fix. Moving towards setuptools entry points is left to a future PR. Additional changes include: - a convenience method on BaseVisaLibrary to handle status code in a uniform manner in alternative backends - a transition towards dataclasses for resource name. This change makes the code more readable and more amenable to typing. One can still get a tuple if necessary using astuple but this should not cause any major breakage. - add a PR template to inform people about formatting tools. Co-authored-by: MatthieuDartiailh <marul@laposte.net>
- Loading branch information
Showing
13 changed files
with
453 additions
and
231 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
<!-- | ||
Thanks for wanting to contribute to PyVISA :) | ||
Here's some guidelines to help the review process go smoothly. | ||
1. Please write a description in this text box of the changes that are being | ||
made. | ||
2. Please ensure that the code is properly formatted and typed by running | ||
black, isort, flake8 and mypy. You can also use pre-commit hooks (see the | ||
developer documentation for detailed instructions) | ||
3. Please ensure that you have written units tests for the changes made/features | ||
added. | ||
4. If you are closing an issue please use one of the automatic closing words as | ||
noted here: https://help.github.com/articles/closing-issues-using-keywords/ | ||
5. Once review has taken place please do not add features or make changes out of | ||
the scope of those requested by the reviewer (doing this just add delays as | ||
already reviewed code ends up having to be re-reviewed/it is hard to tell | ||
what is new etc!). | ||
Many thanks in advance for your cooperation! | ||
--> | ||
|
||
- [ ] Closes # (insert issue number if relevant) | ||
- [ ] Executed ``black . && isort -c . && flake8`` with no errors | ||
- [ ] The change is fully covered by automated unit tests | ||
- [ ] Documented in docs/ as appropriate | ||
- [ ] Added an entry to the CHANGES file |
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
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
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
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
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
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
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
Oops, something went wrong.