Skip to content

Slycot source uses setuptools_scm now #751

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 1 commit into from
Jul 18, 2022

Conversation

bnavigator
Copy link
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.

@coveralls
Copy link

coveralls commented Jul 18, 2022

Coverage Status

Coverage increased (+0.09%) to 94.634% when pulling 0ff9191 on bnavigator:slycot-5.1.dev into 2f29a4c on python-control:main.

@bnavigator bnavigator merged commit 6f124ec into python-control:main Jul 18, 2022
@murrayrm
Copy link
Member

@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.

@bnavigator
Copy link
Contributor Author

Are you sure?
Successfully installed slycot-0.5.1.dev6+g5a6858f

This is the latest version on github.

@murrayrm
Copy link
Member

Ah, I see now. I was confused about how the repository was being check out. I agree the behavior is unchanged.

@murrayrm murrayrm added this to the 0.9.3 milestone Dec 24, 2022
@bnavigator bnavigator deleted the slycot-5.1.dev branch February 18, 2024 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants