Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix unit tests that generate multiple warnings#986

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged

Conversation

murrayrm
Copy link
Member

In preparing for the v0.10.0 release, I found a few more warnings that were not getting trapped properly. The issue was that you get multiple warnings from a single call, you need to test them separately. This wasn't showing up in local testing, but showed up under the GitHub action runs. So figured it was best to clean them up.

I also ran isort on files that I updated to get some consistency in import statements at the top of files (I've been doing that as I make changes).

@coveralls
Copy link

Coverage Status

coverage: 94.482%. remained the same
when pulling0cafd68 on murrayrm:fix_warnings-31Mar2024
intoc8d9c8f on python-control:main.

@murrayrmmurrayrm merged commit1b2abe3 intopython-control:mainMar 31, 2024
@murrayrmmurrayrm deleted the fix_warnings-31Mar2024 branchMarch 31, 2024 16:48
@murrayrmmurrayrm added this to the0.10.0 milestoneMar 31, 2024
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.10.0
Development

Successfully merging this pull request may close these issues.

2 participants
@murrayrm@coveralls

[8]ページ先頭

©2009-2025 Movatter.jp