-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update dependencies #104
Update dependencies #104
Conversation
The type on the `transformations` dict is incorrect (it is a mapping from strs to type[Transformation], not Transformation objects).
Seems the duplicated errors have gone - likely due to the collected errors issue identified by @mostafa in SigmaHQ/pySigma#145.
Lots of type: ignore due to either upstream issues or where type checks are unnecessary.
Pull Request Test Coverage Report for Build 6732220181
💛 - Coveralls |
PR ready, but excuse me whilst I rant for a little about mypy and type checking in Python in general... I've just spent 4+ hours "fixing" the "issues" mypy 1.6.1 identified. But in reality, basically none of these were issues - they seemed to be caused by limitations of the mypy tool itself. To be fair, some of these issues were not entirely caused by In general, I feel the changes I had to make to please mypy in a number of places here have made the code worse/less pythonic (such as introducing lots of unnecessary type checking). Going forward, I would suggest that updating |
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.
@kelnage
Thanks for looking into this! 🙏
Since I created this PR, I won't be able to approve it, but it LGTM! Also, I agree with your point about mypy and I am against updating such packages that causes (sometimes unnecessary) disruptions, but on the other hand, they help uncover a lot of issues one has never thought of. As you already mentioned, pySigma lacks a lot of type info, which subsequently causes disruptions in our work, which puts us in an unfortunate situation (and was kinda expected). This is exactly why I always add type info to any Python code I write, especially when I submit PRs to pySigma.
This is a maintenance PR and updates all the dependencies to the latest versions. Running mypy produces these issues, which should be resolved: