GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — Fix loading of defaults during pytest fixture setup by bnavigator · Pull Request #489 · python-control/python-control Conversation
Contributor
Also make matarrayout and matarrayin function scoped fixtures so Fixes #488
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsAlso make matarrayout and matarrayin function scoped fixtures so that they can set the warnings filters individually as needed for each test.
|
There was an error while loading. Please reload this page.
|
Coverage decreased (-0.06%) to 86.98% when pulling abf1565 on bnavigator:fix-defaults into d66f4e4 on python-control:master. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm not enough of a pytest guru (yet -:) to understand this in detail. OK by me to merge unless you feel that someone else should have a closer look first. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I think I tested it thoroughly on my local machine. Given that it affects only the test suite and not the end user I feel confident enough to merge it with "just" your OK. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Meh, the 3 uncovered lines in freqplot need some investigation before merging. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Unit tests do still not use array but matrix by default
There was an error while loading. Please reload this page.