update usage of flake8 #357
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Please rebase. |
* function names * PEP8 renames in pyparsing (setParseAction() => set_parse_action()) * long lines
Contributor
Author
Done; see also #361 for an overview |
adeas31
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pyproject.toml was introduced in #246; however setup.py is still used for flake8 configuration
This PR
(1) removes the file setup.py (by using Flake8-pyproject)
and
(2) fixes all remaining flake8 warnings (which were deactivated via options)
Additionally, OMTypedParser is updated; this part could be removed / reduced if requested
Milestone: 4.1.0