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 — Slycot source uses setuptools_scm now by bnavigator · Pull Request #751 · python-control/python-control Conversation
Contributor
python-control/Slycot#180 broke the CI setup for the tests with a Slycot from latest sources (0.5.1.dev6 at the moment). Given that the change blocks proper CI runs in PRs like #750, I intend to merge this as soon as the CI passes.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
bnavigator
force-pushed
the
slycot-5.1.dev
branch
from
027aebd to
0ff9191
Compare
|
There was an error while loading. Please reload this page.
|
Coverage increased (+0.09%) to 94.634% when pulling 0ff9191 on bnavigator:slycot-5.1.dev into 2f29a4c on python-control:main. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@bnavigator This PR looks fine, but I note that it now builds against that latest Slycot in available via pip, versus the previous behavior which checked against the latest version on github. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Are you sure? This is the latest version on github. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ah, I see now. I was confused about how the repository was being check out. I agree the behavior is unchanged. |
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.
There was an error while loading. Please reload this page.