-
Notifications
You must be signed in to change notification settings - Fork 6
chore: remove pylint #359
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
chore: remove pylint #359
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #359 +/- ##
=======================================
Coverage 99.72% 99.72%
=======================================
Files 43 43
Lines 4340 4343 +3
=======================================
+ Hits 4328 4331 +3
Misses 12 12 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@rpreen ping me when this is ready to go. |
I think this is done now. |
Ok. I’ll try to do it today between meetings.
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Richard Preen ***@***.***>
Sent: Wednesday, July 23, 2025 11:46:40 PM
To: AI-SDC/SACRO-ML ***@***.***>
Cc: Jim Smith ***@***.***>; Comment ***@***.***>
Subject: Re: [AI-SDC/SACRO-ML] chore: remove pylint (PR #359)
[https://avatars.githubusercontent.com/u/2040384?s=20&v=4]rpreen left a comment (AI-SDC/SACRO-ML#359)<#359 (comment)>
I think this is done now.
—
Reply to this email directly, view it on GitHub<#359 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACZSEI2E7UNZGFT3YXYEIZL3KAGFBAVCNFSM6AAAAACCFZKI3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJQHAYTIOJSGU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All very sensible.
At some stage we will schedule someone to remove some of the ignore in specific places - most obviously the files supporting safe classifier() class - it is a series of minor tweaks.
@rpreen approved and ready for you to merge. Have left it to you in case there are any last minute changes |
Fixes #358