Ruff config and module import updates #51
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
Use immediate modules within the package, and import from the package level for integration tests. For now, ignore `pickle` security warning.
ColeDCrawford
force-pushed
the
49_use_ruff
branch
from
9e6aca1 to
77c1b6a
Compare
Split requirements into primary and dev if still installing from requirements.txt
ColeDCrawford
changed the title
Closed
Member
|
This looks great! |
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.
Use immediate modules within the package, and import from the package level for integration tests. I think it makes sense to expose most of the package methods, the parser classes, and the generic
EDTFParseException.For now, ignore
picklesecurity warning (noqa S301).Add a pre-commit hook for ruff and update the docs with a develop section.