chore: using poetry for dependency management #13
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.
This PR sets up Poetry for dependency management.
In the process of adding this, this PR does the following:
pylint
fromrequirements.txt
and replaces it withflake8
, since all the linting in CI uses flake8.isort
since it's referenced in the.vscode
config, but seemed to be absent from the actual requirementsblack
andisort
formattingMakefile
to use Poetry, and fills in themake format
andmake check-format
commandsblack
andisort
, which resulted in a lot of reformattingREADME
to reference PoetryThis PR leaves the following out:
requirements.txt
in case users are already relying on this to install dependencies. This can be removed if needed (and probably should be at some point)poetry.lock
file to this repo. Since this will be eventually published as a library, it's best not to include the lockfile in the repo IMO.sae_training
andsae_analysis
to a common subfolder. This will need to be done before publishing this as a PyPI module.